go to post Evgeny Shvarov · Aug 6, 2018 Hi, guys!There is a community project of DSW reports - which provides a way to prepare and send DeepSee Web reports in PDF by schedule.So, we introduced this feature to DC online analytics to have a weekly report in PDF - like this one.If you want to receive this report on Mondays too please put your comment here, we'll put you on the list.And you are very welcome to introduce your issues how we can improve it, or provide your pull requests.
go to post Evgeny Shvarov · Jul 31, 2018 Hi, Karthik!Check DeepSee Web solution - it is Angular visualisation module for DeepSee Dashboards and you are able to introduce your own visualisation for any DeepSee widgets. Check this posts too: one, two.
go to post Evgeny Shvarov · Jul 31, 2018 Hi, Scott!It's obvious, but what about this?^OSUWMCInstance = "TestClin"^OSUMCLDAP("LDAPKey") = "/ensemble/"_^OSUWMCInstance_"/mgr/LDAPKeyStore/"
go to post Evgeny Shvarov · Jul 31, 2018 Actually I'm impressed how quickly you guys introduce in QEWD new trendy approaches for development. Though there is a difference here: what @Gevorg Arutunyan published supports Caché Objects and I doubt if QEWD does. Is there any Caché Objects support/mapping in QEWD?
go to post Evgeny Shvarov · Jul 31, 2018 And, any stats, Rob? Is it the most popular API in EWD and EWD3? And why it is not supported in QEWD?
go to post Evgeny Shvarov · Jul 30, 2018 If you like Visual Studio Code you can consider to try VSCode-ObjectScript extension. Github repo.
go to post Evgeny Shvarov · Jul 29, 2018 If you don’t use Studio, you can consider to try isc-dev tool, which is intended to simplify routine processes of import/export code, releases and patches.Import it to e.g. USER and map to %All.After that you’ll be able to import, export, release and patch in any namespace.To work in a given namespace point the tool to a directory on the disk which contains repository in UDL or XML classes (preferablly UDL) with the following command: d ##class(dev.code).workdir(“/work/github/myproject/src”) Use following to import the code: d ##class(dev.code).import() To setup the mask introduce isc.json file into .../src folder with following content: {“compileList”:”A*.INC,B*.CLS,C*.CLS,D*.DFI,E*.GBL” ”projectName”:”myproject” ”git”:0} Example Call Init class to let dev.code use settings in the given namespace: d ##class(dev.code).init() After that you’ll be able to export all the project in one file with the release command: d ##class(dev.code).release() it will export all into one /mgr/database/myproject_release_ddmmyyy.xml file. Once you commit your changes to git repo you’ll be able to have a patch release. Call d ##class(dev.code).patch() to get all the changed code into one patch release in /mgr/database/myproject_patch_ddmmyyyy.xml file. To export all source code (including DeepSee staff) in UDL and organized in folders call: d ##class(dev.code).export() And call compile method to compile everything in your project, but not the whole namespace: d ##class(dev.code).compile() One of the projects which is maintained with this util is dsw-map: classes, globals, DFIs, releases.
go to post Evgeny Shvarov · Jul 23, 2018 Cool staff, Athanassios!Caché queries demo doesn't work though:
go to post Evgeny Shvarov · Jul 23, 2018 Jaqueline!I do not get the aim: do you want to filter facts BEFORE building the cube? Or you want to filter cube data on the fly via dimensions and members somehow?If you are looking for "any this values" in filter expression you could consider to try with %OR
go to post Evgeny Shvarov · Jul 19, 2018 Hi, M Y!Check this video and these articles (one, two) from @Mark BolinskyHTH
go to post Evgeny Shvarov · Jul 18, 2018 Hi, Fabian!Could you share please the call to export the compiled classes without source code?
go to post Evgeny Shvarov · Jul 18, 2018 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.
go to post Evgeny Shvarov · Jul 18, 2018 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
go to post Evgeny Shvarov · Jul 17, 2018 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.
go to post Evgeny Shvarov · Jul 17, 2018 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.
go to post Evgeny Shvarov · Jul 13, 2018 Oleg, congrats with 1,500+ installations of VSCode-cos!And I like the new features of "Save on Compile" and easy server connection settings.
go to post Evgeny Shvarov · Jul 13, 2018 Actually the voting has already resulted into the coming webinar. See the announcement )
go to post Evgeny Shvarov · Jul 2, 2018 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?