Forum Discussion
Hierarchical Slicer that Does Not Include Parent Nodes
Super UserHey joeatamida ,
I think you are using the default slicer correctly, the below image shows a hierarchy using the default slicer:
From my understanding, you want to get rid of the "children are selected" visualization, as in Europe / Germany, because a German city is selected.
From my knowledge, there is no custom visual that allows using a hierarchy without indicating a selection on the parent level, here: the semi-filled checkbox.
Out of curiosity, what is the requirement behind your ask?
The visualization will not affect your measures. If one of my measures requires the list of selected cities I use VALUES( 'DimRegion"[CityName]), e.g., inside a table iterator functions like SUMX.
From my personal point of view, I like the visualization, the below image helps me to identify that "something" inside France is selected.
Nevertheless, I'm looking forward for more details about your requirement.
Regards,
Tom
Thank you for the reply.
This could be a modeling problem, but here is the issue. Instead of something with appropriate logical and labeled separations like continent, country, county/state/other, city, etc, we have instead a series of what are effectively folders. In the example given, we want the ability to navigate these folders, which the front-end UI is capable of doing, in order to select a single directory within which to view results.
The original model has all of these "Groups" (effectively folders or similar enough concepts) in a single table called Identity. Identity uses the IdentityRelationship table to refer back to itself with a ParentChild column. In order to get this slicer to work at all, we did have to develop a table with Columns "Group Level 1", "Group Level 2" etc out to 10 so that we could pull those values into the slicer in that order and create the appropriate hierarchy. We couldn't use measures with the OOTB slicers due to what I'm assuming are infinite loop-related self-referential reasons.
The end result is the structures noted in the original post, but, in the example given, when we select G, which also selects A and F as parent nodes, then our applied filters become A and F and G for groups. Due to all of these being in a single table with no distinction (no concept like country versus state/county/other), simply parent or child nodes of otherwise unknown depth until selection takes place, this makes it difficult to implement the solution.
Apologies if this is both rambling and tough to follow, but as a result, I'm thinking we may need a custom PBI visual that works just like the hierarchical slicer, but does not select the parent nodes (allowing navigation without parent selection upward). Or we may need to rebuild our model to facilitate the action we want to see which can probably be done with PATH functions or the like if I take some time to think about it and sit down with the developers.
Hopefully this makes sense and/or helps to clarify in a way that might lead to new thoughts on the topic.
Thank you,
Joe