Hi Guys,
I’m wondering about referencing the Global Filter (PA hierarchy)in a dimension MDX expression.
Is there a recommended way to use the selected element from the Global Filter directly in the MDX for a dimension subset?
For example, how should I write the MDX if I want the subset to change dynamically based on the global filter selection? Seems not working for PA hierarchy
Nothing should have changed here in terms of functionality and setting service reference style from the AngularJS version. The reference for a member from a filter should be $<<instance.dimension.hierarchy>> which is what it looks like you have. If this reference style is used in any text display field like title or info then this should resolve to the caption display value. If the same reference is used in a technical field like MDX then it should resolve to the principal name.
If it is returning a null value then this looks like a bug and you should create a ticket
One additional piece of information would be helpful which is is the filter hierarchy also used in the table rows or columns? If it is then the same $<<instance.dimension.hierarchy>> reference in the context of a table popup should return the row or column context ID and not the filter value. In that case if you wanted to force the filter value you would need a special syntax (which we had in the Angular version but I’m not sure if it exists in the new version.) However, as the value in your screenshot looks to be null then I assume this isn’t the case.
Thanks for the explanation! I just wanted to clarify that the same reference syntax in the process parameter can successfully read the element from the global filter, so the hierarchy reference itself is valid.
However, when I copy the same expression and use it inside the dimension editor’s MDX, it doesn’t return anything(undefined). That’s why it really looks like a bug.
I’m also a bit curious because the previous version of the dimension editor used to support selecting or referencing a specific value more directly. Now it seems the only way is to write MDX manually to reference a particular element.
Just sharing this in case it helps with identifying the issue.
