Visual level filtering in slicers
I have a large set of options from which I would like to pick some specific ones and use them in a slicer to filter my data.
Currently, this is not possible while it is an implemented feature for other chart types.
I'm currently using a 100% stacked column chart as a workaround.
Andre Cavaca
shared this idea
I’m happy to say this is now complete! In the June 2019 release of Power BI Desktop you’ll see you can set visual level filters on slicers. There’s one known issue where applying a measure filter to a slicer in range mode causes the visual to show an error. We’ll release a fix in an interim update before the July release.
Thanks for your patience and your votes, everyone!
148 comments
-
SJR
commented
This is a must have!
-
Karl Geiger
commented
This would be very helpful, especially in the case where one could specify for example a "from" and "to" field towards the visual filter. There are certain use cases where for example where I would like to apply page slicer selection to all visuals, but on a certain visual I would like to allow the user to select a range until (within the range of the main slicer selection). Important for dates for the most part.
-
Ben Sanders
commented
This is number 8 of the top 10 most voted ideas, with the last note back in January that it was under consideration... When are we going to get an update?
-
Anonymous
commented
A must have...
-
Andrew Lindner
commented
Waiting for this. Have had to do very clunky search-feature workarounds that involves typing out each value in the search bar for each value from a filtered list, rather than having a simple button that has a bookmarked visual level filter for the slicer.
-
Jeo Varghese
commented
This functionality will be really helpful. especially when we have a Drillthrough to a report + additional filtering in that report
-
Alankar Padman
commented
Is there an ETA for when this will be included? The idea has been out there for over 2.5 years.
-
Daniel Nilsson
commented
This really has to be prioritized soon! This is a must have!
-
Line
commented
In our customer slicer we have 300.000 customer. If I could set a filer on a country (another dimension) the sales reps would only see their customers in their country. I could do the same if I enable both-way-filtering, but i dont want to do this do to performance issue. This is a feature that exist in Qlik Sense, which our end-user is asking for.
-
Anonymous
commented
We need this visual filter for slicer where i can add date as value and other column like flag as filter to show only those dates.
Thanks -
Kamal Mukhi
commented
Please add this feature. We need this.
Thank You
Kamal Mukhi -
victor
commented
Please add this feature! Today We can add a slicer to filter another slicer, but this is totally inefficient since colateral work of editing interactions become huge and really annoying.
So, please:
1) Allow the filter a slicer
2) Improve the "edit interactions" funcionality. It would be great if we can "affect all visual", or "affect none". -
Alexis Olson
commented
It needs to be possible to do this based on a measure. I'd like to exclude certain options that don't meet a specific threshold.
-
Anthony
commented
Will be very useful
-
Chris Mlynarczyk
commented
I found a reliable workaround for this, you can basically just use a slicer on a slicer - after all, what is a slicer if not just a dynamic Visual Level Filter?
1. Create Slicer #1 for your users to interact with
2. Create Slicer #2 with the field you want to filter Slicer #1 by, i.e. the field that you would have put into your Visual Level Filter.
(Example: If Slicer #1 has names of all sales reps in the company, and you only want it to show reps in a certain region, then create Slicer #2 with the Region field. Or, if you want to manually choose specific reps to show, then you can even just use the same Sales Rep field in Slicer #2)
3. Edit the interactions on Slicer #2 so that it ONLY INTERACTS WITH SLICER #1. If necessary, edit the interactions of your other visuals to not interact with Slicer #2.
4. Choose the values on Slicer #2 that you want to allow in Slicer #1, i.e. the values that you would have allowed in the Visual Level Filter.
5. Open the View tab, check the "Selection Pane" box, find Slicer #2 on the Selection Pane, and hide it (click the eye next to it) so users can't interact with it inadvertently.Hope this helps!
Chris -
Anonymous
commented
Very needed function that is missing in Power BI. We are working on the project which some functions are very complicated to implement because of a lack of filtering in slicers.
-
Chris Mlynarczyk
commented
I just ran into this issue, but after giving it more thought, I think there's a fundamental problem with visual level filters on a slicer. How do you handle interactions between that slicer and visuals that don't have the same filter applied? E.g. say the visual contains values 1, 2, and 3, but the slicer is filtered down to values 1 and 3. What do you do with value 2 in the visual? When would Power BI display that data and when would it be filtered out?
I think the best solution is to give an option to make slicers subservient to the visuals they interact with, maybe a toggle that trims slicers down to data that's actually in the resulting visuals. I don't think allowing visual level filters on slicers properly solves the problem because it would, in the end, create a data mismatch between visuals and slicers that would be difficult to reconcile. Just my 2 cents.
-
sunil.tak@bizmetric.com
commented
Seriously needed. If , we can get some expected dates, that will be great.
-
Pär Adeen commented
Please note that this request is valid for all filter visuals, not only slicers. As I'm told, visual level filters are turned of already in the development API as soon as you choose to develop a filter visual.
Please also note that using the other two filters, Page level filters and Report Level filters are already available for all filter visuals already, so why not the visual level filter as well -
Robert Wolf
commented
very needed creates a lot of seemingly unnecessary labor to get around this seemingly simple solution. Though I have a feeling for Microsoft it is harder than it would seem.