I have 2 dimensions. When I choose an element in Dim1, I need it to limit what is available in Dim2. In the following example, when P1C1 is selected from Dim1, I want Dim2 to display E1 and E2. If P1C2 is selected, then no elements can be chosen from Dim2:
When this is part of a view, I can write some MDX that uses the current member from Dim1:
TM1Member(FILTER([Dim2].[Total Dim2].CHILDREN , [Dim2].CURRENTMEMBER.NAME = [Dim1].CURRENTMEMBER.NAME).ITEM(0) , 0).CHILDREN
This works but requires Dim2 to be exposed in the overview of an exploration widget, which is not something that I want to exposed to our users. Ideally, I would want both to be driven by a selector widget – but then I can’t synchronise the second dimension from a selection in dimension 1. Are there any plans to pass in the synchronisation parameter (like can be fed into processes) into MDX before it gets sent to the TM1 server? I think it would need a default value for when the synchronisation is not on.
I know there are workaround options but wanted to know if this was something being considered as part of PAW’s future?
@Planning Analytics