Matt White on 26 Sep 2024 10:26:29
Understand from support that there is a known limitation within field parameters when grouped with a hierarchy.
The expectation is that selecting fields from a field parameter in a slicer will display them in a visual in that order (e.g. selecting bar then foo will display bar then foo). When a hierarchy comes into play, the behaviour can go wrong, so that instead of selecting barfoo, foobar, foofoo, barbar displaying in that order, it reorganises after the final selection to barfoo, barbar, foofoo, foobar.
This is a real shame, as it cripples the functionality of the parameters where hierarchies are used in an organisation.
Idea is to sort out background DAX created so that it respects select order, no matter if there is a hierarchical grouping.