All
Accepted answers
Evgeny Shvarov · Jul 18, 2018 go to post

And I think you can use IN operator in this Build Restriction expression - use everything which suitable to put in WHERE clause of a SELECT query.

Evgeny Shvarov · Jul 18, 2018 go to post

Hi, Jaqueline!

Have you tried Build Restriction field of the cube?

Build Restriction is in the properties of the cube.

Put there SQL Expression which goes after WHERE clause. It will filter the facts which will be included to your cube. E.g. if you base your cube on Samples.Person you can set the Cube Build Restriction as:

NAME='John' 

to limit the facts of the cubes to only records with 'John' in Name property.

HTH

Evgeny Shvarov · Jul 17, 2018 go to post

You could also check this small library isc-dev which could automate you on working with git on:

import/export code in UDL, exporting releases and patches upon commits.

Evgeny Shvarov · Jul 17, 2018 go to post

Hi, Murillo! You also can export all the classes, DFIs, globals or whatever of your project in one file with D $System.OBJ.Export(). E.g.: s

list="RMH*.CLS"

  D $System.OBJ.Export(list,"release16072018.xml")

Then just import it on a target system.

Evgeny Shvarov · Jul 13, 2018 go to post

Oleg, congrats with 1,500+ installations of VSCode-cos!

And I like the new features of "Save on Compile" and easy server connection settings.

Evgeny Shvarov · Jul 2, 2018 go to post

Thanks, Oleg!

But it's not about to map DeepSee  globals, though this is helpful. Do you want to provide more details on this repository? Why map and what are the globals?

Evgeny Shvarov · Jun 27, 2018 go to post

Que bueno! :)

But I would be happy even if you suggest the way how to contribute to your solution to introduce an another language support.

Evgeny Shvarov · Jun 27, 2018 go to post

Hi, Francisco!

Great stuff!

Could it be possible to add other languages support to your solution? E.g. Russian?

Evgeny Shvarov · Jun 21, 2018 go to post

Hi, Shameer!

As @Nicole Aaron mentioned, there is no officially proposed folder structure for your  InterSystems project, but I can share one typical approach.

The upper folder is basically named "src" assuming source code inside.

Files inside "src" could be splitted by source type. E.g.:

"cls" -  for ObjectScript classes,

"inc" -  for include files,

"mac" - for mac routines,

"dfi" - for DeepSee dashboards and pivots.

Every class name consists of package(s) and class itself. So class package could be projected to a folder. E.g. source code for the class Sample.Person will be stored in the file with following path:

/src/cls/Sample/Person.cls

There are numerous projects on Github which use similar approach. You can find examples of such projects via these cacheobjectscript-udl tag, e.g. this project.

HTH

Evgeny Shvarov · Jun 19, 2018 go to post

Thank you, Lucas. But the thanks should go to @Oleg Dmitrovich

As for CSP - it is a file, and can be edited via VS-Code just as a file in a versioned folder.

If you are looking for exporting tools, I can recommend isc-dev module, which can export code as single files in a dedicated folder structure (including DeepSee stuff), can export a single kits - large xml kits, say releases, and also patches which a commit, or a set of commits in git.

Evgeny Shvarov · Jun 15, 2018 go to post

Could you please share a sample code with ordering of the main grouping to understand the problem better?

Evgeny Shvarov · Jun 15, 2018 go to post

Hi, Community members!

It's just a reminder on a meetup we are having on 25th in UK, Birmingham!

And! We have a time slot available! So if you want to tell about your solution or share your best practices with InterSytems Data Platform please contact me or comment to this post!

Evgeny Shvarov · Jun 14, 2018 go to post

Hi, John!

Yes, we had the issue here - it is fixed now.

Thanks for pointing this out!