go to post Peter Steiwer · Oct 7, 2022 Hi Ahmad, These functions do not exist in MDX, please see the MDX function documentation here: https://docs.intersystems.com/iris20221/csp/docbook/Doc.View.cls?KEY=D2R... You likely want to use the %OR function: https://docs.intersystems.com/iris20221/csp/docbook/DocBook.UI.Page.cls?... Using %OR would allow you to reference multiple members, for example:Expression="%OR({[Demographics].[H10].[Citizenship].&[USA],[Demographics].[H10].[Citizenship].&[U.S.A],[Demographics].[H10].[Citizenship].&[US]})"
go to post Peter Steiwer · Sep 28, 2022 Hi Phillip, Specifically, Studio connects using the superserver port: https://docs.intersystems.com/iris20221/csp/docbook/Doc.View.cls?KEY=PAG... As Tom mentioned, you will need to determine which port this has been configured as
go to post Peter Steiwer · May 24, 2022 Hi Virat, Here is a good resource for getting started with InterSystems IRIS BI (DeepSee):https://learning.intersystems.com/course/view.php?id=1793 If you are interested in creating dashboards and exploring your data, IRIS BI is a good choice. If you are interested in traditional reporting, you may want to consider InterSystems Reports:https://learning.intersystems.com/course/view.php?id=1444
go to post Peter Steiwer · Jun 15, 2021 When executing a query, DeepSee will store intermediate and final results in the cache globals. As the engine was trying to create a new session, it looks like it could not access the database in e:\hs-db\tfoms\. Either this database is mounted read only (in this case you will need to create some DeepSee mappings) or the user executing the query does not have r/w permissions on this database.
go to post Peter Steiwer · Jun 11, 2021 What database is in /hs/nehi/ ? These protect errors suggest the user may not have permissions on this database
go to post Peter Steiwer · May 27, 2021 I just tested and it worked OK for me. I used the following: Class: Class DC.TestImport Extends %Persistent { Property TS As %TimeStamp; Property Bool As %Boolean; } CSV: 2021-05-27 17:43:15,0 2021-05-27 17:51:13,0 2021-05-27 17:53:11,1 Import Settings: File Name: C:\Users\psteiwer\Documents\DC\testimport.csv Charset: <Device Default> Schema: DC Table: TestImport Columns are delimited by: Special Character: , First row contains column headers? No String quote: double Date format: YYYY-MM-DD Time format: hh:mm:ss TimeStamp format: ODBC Format Disable validation? No Defer Index Building with %SortBegin/%SortEnd: No
go to post Peter Steiwer · May 26, 2021 This now works after modifying my objectscript.export "folder" setting. It was previously "src" and is now "".
go to post Peter Steiwer · Apr 30, 2021 We also have a sample that uses %InjectFact() inside of the %OnBuildCube() Method. Documentation here. This injects the cities "Cambridge", "Chelsea", and "Somerville" into the HoleFoods cube. These city members will exist in the dimension table, but there is no associated data (there could be, but in this example there isn't). When using the City level on rows and the default NONEMPTY, we see the following: When we turn "Show Empty" on: We now see these members with no data:
go to post Peter Steiwer · Apr 20, 2021 Hi Evgenii, I noticed this question has not been answered yet, is there a specific reason why you are looking into using a Data Connector? Typically before recommending a Data Connector, we would recommend that a new class is created and populated from a similar query that your Data Connector would have used. This allows for a lot more standard cube usage. Standard options like synchronization and detail listings would be available without needing to implement custom code to modify the SQL and they wouldn't require you to worry about using $$$RESTRICT
go to post Peter Steiwer · Apr 16, 2021 By default, changing the display of the Week members is not available. However, you can create a custom time level by extending %DeepSee.Time.WeekYear and overriding a couple methods. Then you can change your timeFunction value in your cube definition. Here is a sample I put together that was MINIMALLY tested on a newer version than the version you noted here: Class CustomTime.WeekRange Extends %DeepSee.Time.WeekYear { /// Return the user-visible name of this level. ClassMethod %GetName() As %String { Quit "WeekRange" } /// Convert a level key value to a display value. ClassMethod %KeyToValue(pKey As %Integer, pFormat As %String = "", pOffset As %String = "") As %String { Set tValue = "" Set tSC=..%KeyToBaseRange(pKey,.tStart,.tEnd,pOffset) Set tValue=$zd(tStart)_"-"_$zd(tEnd-1) Quit tValue } /// Convert a $H value to the logical value used for this level. /// This is used within the computed field logic for properties /// within a fact table based on this level.<br/>. /// In this case, we convert $H to an ISO Week: YYYYWnn ClassMethod %Convert(pTime As %DeepSee.Datatype.dateTime, pTimeOffset As %String = "") As %Integer [ CodeMode = expression ] { $S(pTime="":"",pTime=$$$DeepSeeNullTimeMarker:$$$DeepSeeNullTimeMarker,1:##class(%DeepSee.Time.WeekYear).ISOWEEK(pTime)) } }