go to post Alessandro Marin · Aug 21, 2018 Yes, that would work. You can test that in RelatedCubes/Patients and RelatedCubes/Patients. The downside of this approach is having to use cube relationships, which are more complex to maintain and in general have slower queries.
go to post Alessandro Marin · Jun 5, 2018 There is no direct equivalent in ObjectScript to the ternary operator. You can use $SELECT or $CASE
go to post Alessandro Marin · Apr 11, 2018 Hi Evgeny,I think I'd better leave the answer to somebody with more experience in this field.
go to post Alessandro Marin · Apr 11, 2018 I did not plan to introduce such a script though I actually do have scripts doing operations on databases, mappings, security, etc. It would not be too difficult to implement such a script. There is already something similar for Ensemble namespaces.One problem however is that, as I hope it will be clear from my series, there is no universal solution for all user cases. In spite of this my opinion is that the solution of intermediate complexity outlined here would be the most likely to be adopted by most users.
go to post Alessandro Marin · Mar 31, 2018 Those listings in italics are defined in Listing Groups. You can find them in SMP > DeepSee > Tools > Listing Group Manager > Open > Additional Listing for HoleFoods SampleThey work in MDX:Do $SYSTEM.DeepSee.Shell()>>DRILLTHROUGH SELECT FROM [holefoods] %LISTING [Another Sample Listing by Date] "Custom Listing" is the listing that you construct in pivots using Listing Fields, see here: Display a Detail Listing. I have not checked the code but to me it makes sense that, if defined on the pivot, "Custom Listing" will not be available for general MDX queries.
go to post Alessandro Marin · Mar 31, 2018 What is exactly that custom listing? Is it defined in Listing Group (those ones should work using %LISTING)?
go to post Alessandro Marin · Mar 19, 2018 In spite of the fact that your queries do not show dates nor the PARTEPOLICIAL cube, I do not think related cubes change anything from what suggested in answer 2 here: https://community.intersystems.com/post/filters-deepsee-dashboards . Below I rephrase what was suggested:A) Create a "myDate" pivot variable used as "Literal" and of type "Day" in your main cube, which I will assume is EVENTOSPOLICIALES.B) Define two calculated dimensions. First get the spec of the two dates from your main cube. You can drag and drop dates and inspect the MDX query. For example, the specs will be something like:[Some dimension].[H1].[Fecha Creacion][Relation to PARTEPOLICIAL].[Some other dimension].[H1].[Fecha Parte]C) Create two calculated dimensions with Local Storage. The expressions should use the specs in B and the pivot variable in A, for example:[Some dimension].[H1].[Fecha Creacion].$variable.myDate[Relation to PARTEPOLICIAL].[Some other dimension].[H1].[Fecha Parte].$variable.myDateD) Use the calculated dimensions as filter or in rows/columns for your pivots. The dashboard will have to have a widget with a Apply Pivot Variable control.
go to post Alessandro Marin · Mar 19, 2018 The queries shown above do not use dates. I do not see the PARTEPOLICIAL cube
go to post Alessandro Marin · Mar 19, 2018 That happened because calculated members and pivot variables are stored in globals. One way to export folder items together with related supporting items is to follow the procedure described here:http://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=D2IMP_ch_moving#D2IMP_folder_manager_export_container
go to post Alessandro Marin · Mar 15, 2018 I am glad point 1 helped, though I see that you flagged as accepted answer another one which is about the problem you have not yet solved.
