Forum Discussion
Interaction between two Slicers doesn't work well
Please refer to my last post for the explanation from PBI team. In this scenario, unselecting on higher level filter should make the previous selection on lower level filter unselected generally. But PBI now stores previous selections and show them regardless of whether another filter may hide them. The team do not want to clear selections based on filter from other slicers, and they are obligated to show any selected items.
Best Regards,
Herbert
Any use cases they use to support this design?
Erin If you remember I was with you on this!
First the bad news! :smileysad:
I think this is more about the principle - you have selected something in the slicers yourself!
Basically you have set the search criteria yourself!
They are not about to undo/clear YOUR selections!
As you can see in the picture you selected Dallas P1 and Houston P1
They don't want to clear your selections - you are the only one that can clear them!
In your example I guess the products are exclusive to those cities and its easier to see why you may not like the outcome.
Hope this makes sense!
If you have not selected something yourself and it does not apply it will disappear
however if you have selected something yourself it will show no matter what because YOU selected it yourself!
And now the good news! :smileyhappy:
I think I may have found a solution for you =>the Hierarchy Slicer
Hope this helps! :smileyhappy:
Hi Sean & v-haibl-msft
I think the hierarchy slicer is a good workaround but doesn't really deal with the problem. Also it looks a bit different from the standard slicer so mix and match aren't great - I'll raise it with the developer.
There's a confusing usability effect in the standard slicer. If an item is selected but not valid, then it still appears (as noted) - but at the bottom of the list. If the list is being used and the height of the list is small so that there is a vertical scroll bar, then if the invalid item is selected and operational, you can't see it. I am finding that users report a bug (or get confused), because they can't see it. One partial solution would be to move it to the top of the list.
In terms of logic, I don't think I agree with your approach although the simplicity of the idea is good. I would agree with your approach if cross-filtering is turned off between the two slicers. However, if cross-filtering is active, I expect one slicer to act upon the other slicer. When a slicer item is selected then, on all visuals where the cross-filter is active, filtering takes place. But not seemingly on the slicer. To me, that is not a logical application of cross-filtering.