Context sharing on navigation not working for some list types

Describe the bug
If the list type for a filter dimension is defined as any of the following

Element Drill
Element + Element Children
Element + Element Ancestors
Element Children

Then on navigation to the screen the context from the setting service is ignorred and the first element in the list is selected for the filter value when the Default Element entry is empty.

If the same MDX as the auto-generated MDX is copied and the list type changed to MDX then the context replacement works as expected.

To Reproduce
Steps to reproduce the behavior:

In the UX samples app in the screen Rows and Columns Format

‌

2. For the Region dimension on filter change the list type from MDX to Element Drill with World selected as the element. The results in generated MDX for the list of

{HIERARCHIZE( {TM1DRILLDOWNMEMBER( {[Region].[Region].[1]},ALL, RECURSIVE )} )}

Save the changes.

3. Navigate to Simple Planning Template and set the Region context to USA

4. Navigate back to Rows and Columns Format screen

5. World is selected as the region context when it should be USA

6. Copy the generated MDX and change the list type to MDX. Paste in the MDX and save changes.

7. Repeat the test and the filter value is taken from the setting service.

‌

Expected behavior
Other than MDX all other list types are simply shortcuts for the end user to avoid needing to hand write MDX. The way UX treats the list and setting service substitution at runtime should be identical.

‌

Related bug
The advanced options GUI for the other list types then MDX doesn’t expose the Default Element property which should always be available for filter dimensions regardless of selected list type (except maybe for type=Element).

Comments (3)