Forum Discussion
Interactions between viz's - filtering based on two other visualizations does not work
To answer your question. The term "master" is kind of fitting. When you select a slicer, the selection will not be cleared until you force it to clear. When you select another visual, that selection is clear the moment you make another selection on any other visual.
Currently because of this limitation, if I know that a user will want to filter by a specific field, I normally provide a slicer on in addition to the visuals. If there are a long list of items you can turn on the search function in the slicer.
Hopefully, we'll get the cross highlighting feature soon. Let me know if this helps.
Kind regards,
Mike
Thanks Mike for the tip and the link.
Indeed, it is a very popular idea, however it looks like this hasn't been introduced in the December's release.
A slicer would be a nice workaround, especially if a map could filter such slicer.
For example - if I select a city on a map, this city is also selected in the slicer's drop down list.
However, despite the fact that the map "filters" the slicer in my report, when I select the city in the map, slicer's selection remain unchanged. So, does it mean that slicer is always a "master" for other visuals?
Helper I
To answer your question. The term "master" is kind of fitting. When you select a slicer, the selection will not be cleared until you force it to clear. When you select another visual, that selection is clear the moment you make another selection on any other visual.
Currently because of this limitation, if I know that a user will want to filter by a specific field, I normally provide a slicer on in addition to the visuals. If there are a long list of items you can turn on the search function in the slicer.
Hopefully, we'll get the cross highlighting feature soon. Let me know if this helps.
Kind regards,
Mike