go to post Evgeny Shvarov · Apr 14, 2018 Thank you, Robert! So, if I want to put $H to a %Date property I do: set s.Date=$H do s.%Save() for %TimeStamp property to set current date/time, I do what?
go to post Evgeny Shvarov · Apr 13, 2018 Eduard, do you think it makes sense to DELETE everything in a namespace and then import code from checkout?Consider DeveloperA deleted ClassB from repo and from his local NamespaceADeveloperB checkout repo and with only classA but still has ClassB in his local NamespaceB. What will delete ClassB in DeveloperB's working system?The only "automatic" solution I see here is to check out and import classes into clear or new Namespace.Or never delete classes, only "deprecate" it
go to post Evgeny Shvarov · Apr 11, 2018 Hi, Alessandro!Thanks again for such valuable content on BI Architecture with DeepSee. Analytics server configuration gets more and more sophisticated with a lot of manual operations. Do you plan to introduce a script which will convert a "usual" server to a "ready for DeepSee Analytics" server in a one-run? That would be fantastic!
go to post Evgeny Shvarov · Apr 11, 2018 Hi, Alessandro!Thank you for the useful article!Having Primary and Analytics servers is very important, the main reason being to avoid performance problems on either server. Please check the documentation about Recommended Architecture.What is the type of mirroring is recommended? Should it be synchronous mirror or async, or disaster recovery?
go to post Evgeny Shvarov · Apr 7, 2018 Wow. That's interesting. I'm curious what will happen if a class was created in Caché and then modified in IRIS (e.g. with new property) - would it be another global for a new property? Could you check that?I think if you created class first in Caché 2017.2 and preserve the storage definition within a class in version control you should be good with IRIS - I mean IRIS shouldn't change the storage of your 2017.2 class.
go to post Evgeny Shvarov · Apr 7, 2018 Hi, Peter!I would warn you of NOT including storage information in Git (or any other CVS). It is the must to keep class storage definition within source control.Consider you have a system in production where you have class A with properties P1 and P2 with data.And you developed a new version of a product with the optimization when you don't need P1 anymore and delete it. And you added a new feature which needs to add property P3 You deploy new class A with P2 and P3 properties on a production system. Storage would be generated upon class definition and you will get the following:All reads from P2 would deal with former P1 data.All reads from P3 would read former P2 data (yes, you will get P3 initialized by former unexpected P2 data).So you'll get some unexpected behavior and bugs with this.Solution:keep the storage definition within a class and in Git.Maybe delete a property is a bad practice but sometimes we are doing that.HTH
go to post Evgeny Shvarov · Apr 6, 2018 I'll answer the comment related to import/export utility isc-dev . It exports everything in a namespace to a specified folder. You can setup the folder with: d ##class(sc.code).workdir("D:\yourfilder") Then export with d ##class(sc.code).export() You can specify a mask of classes too or set it up in isc.json file.
go to post Evgeny Shvarov · Apr 3, 2018 Hi, Jaqueline! You also can consider using isc-dev import/export tool. Install it in USER and map into %ALL (to make it runnable from any namespace), set up the tool like this: d ##class(sc.code).workdir("/your/project/src") Enter your project namespace and call: d ##class(sc.code).export() And the tool will export (along with classes) all the DeepSee components you have in Namespace including pivots, dashboards, term lists, pivot variables and calculation members in folders like: cls\package\class dfi\folder\pivot gbl\DeepSee\TermList.GBL.xml gbl\deepsee\Variables.GBL.xml. So you can use it with your CVS tool and see commit history, diffs, etc. To import everything from the source folder into new namespace use: d ##class(sc.code).import() or standard $SYSTEM.OBJ.ImportDir() method. HTH
go to post Evgeny Shvarov · Apr 3, 2018 Hi Sergey! Kanban is great! Love it)But now I do not start any project without issue tracker. If you got a bug report or a feature request, where you will place it?
go to post Evgeny Shvarov · Apr 2, 2018 Hi, Peter, thanks! The question was that everything which is listed in pivot-settings-dropdown is available to call with %LISTING in MDX, except with "custom listing". Which can be called with DRILLTHROUGH .... RETURN fields MDX instruction, as you wrote. Thanks!
go to post Evgeny Shvarov · Mar 31, 2018 Thank you, Alessandro! That's clear now. I guess Custom Listing is being executed with DRILLTHROUGH + field names by comma: there is an option in Drillthrough documentation.
go to post Evgeny Shvarov · Mar 31, 2018 Have no idea, Alessandro.Just figured out, that there are some extra listings (in addition to those we have in the cube) available for pivots in Analyzer. %Listing only works (for me) with those which are declared in the cube.You can see (and alter custom listing) if you open Detail Listings section in Analyzer (version 2017.2).
go to post Evgeny Shvarov · Mar 31, 2018 Hi, Robert!Thanks for the answer!Yes, %LISTING this works perfectly with listings declared in the cube definition.But if you open Analyzer you can see extra "Custom" listings, which are available in the pivot, but not available via %LISTING.
go to post Evgeny Shvarov · Mar 31, 2018 This is changed. So ReactJS is React and AngularJS is Angular now.
go to post Evgeny Shvarov · Mar 29, 2018 Thank you, Artem!It's a great feature which helps you call any binaries diectly from Objectscript without coding a proxy dll. It was also used for Caché Localization manager.
go to post Evgeny Shvarov · Mar 28, 2018 2) It's OK approach for relatively small external source tables because in this case, you need to build the cube for all the records and have no option to update/sync.If you OK with timings on cube building you are very welcome to use the approach.If the building time is sensible for the application consider use the approach what @Eduard Lebedyuk already has advised you: import only new records from the external database (hash method, sophisticated query or some other bright idea) and do the cube syncing which will perform faster than cube rebuilding.
go to post Evgeny Shvarov · Mar 27, 2018 Hi, Chintan!Have you seen this article? Maybe it's relevant.
go to post Evgeny Shvarov · Mar 22, 2018 Thanks, Eduard!Also this is a relevant article too by @Vicky Li
