Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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.
Why Is it not possible to add a Visual level filter for a slicer when this is an option for other chart types?
I'm currently using a 100% stacked column chart as a workaround.
Thanks,
Andre
Solved! Go to Solution.
There is a hack for this ...
1. turn the visual into a bar chart
2. apply the visual level filter
3. turn the visual back into a slicer
You can check out my solution here
Have 1 slicer where a min and max date range is selected and use that to filter such that ALL rows with DATE1 OR DATE2 are returned. Using two slicers returns only rows with DATE1 AND DATE2 which is why this is not the ideal scenario.
Table: CE (All relevant fields are in this table)
DATE1: CreatedTime
DATE2: caseclosedtime
DATE1 fully qualified reference: 'CE'[CreatedTime]
DATE2: fully qualified reference: 'CE'[caseclosedtime]
Steps
in the function bar replace
Column =
With
CreatedTimeOrCaseClosedTime = SELECTEDVALUE('CE'[CreatedTime],'CE'[caseclosedtime])
Now we have a column that contains a date and will return created date if it is selected in a slicer and if not will return closed date.
Any news on this topic ?
We need that feature a lot of times. 😞
It's really frustrating to see that something so basic is not implemented. I need the filter always to be updated to the current date i.e. all filter options.
Create two of the same slicers, making sure one of them (referred to as 'first slicer') only has 'interactions' with the other slicer ('second slicer') and nothing else on the page. Select the chosen items from the first slicer and it will filter the second slicer to only show those options available. Go to View->Selection Pane and hide the first slicer so it is no longer visible and you're sorted.
You can add a page level filter and remove what you don't want to appear in the slicer. This is really useful when your requirment is to remove (Blank) or empty option from the slicer.
If a direct page filter wont' help, then you are probably filtering the wrong table and a relationship is missing.
Anoterh way to help limit your slicer options is to ensure you have cross filtering enabled.
often you have filters on the page, but the slicers seem unaffected by the filters. that's possibly because you're filtering for all won opportunities but are not applying that filter back to the accounts list. (just as a concrete excample I was struggling with)
if you configure your relationship between the two tables to not just filter in a single direction but both you will see that slicers automatically filter too.
PS. this cross filter option often only works once. PowerBI does not like multiple cross filters in your model as it can only handle a singe filtering path.
This was 100% what I was running into with trying to filter down my results in a table. Thanks a lot for the info! Works perfectly
I found a hack
My data has hospital Id in one table and hospital names in another table. To see only hospital for Ids present in table1, I added the hospital id slicer from first table and manually chose all the IDs (remember not to use select all also add a blank id in the first table ),
add another slicer from the master table.The first slicer will filter the second slicer .hide the first slicer behind second slicer
I just went to the Ideas forum and upvoted as many posts as I could find that request this fix. This is so important! And it's so frustrating to see a Visual-level slicer on this visual, but not be able to use it!
In the meantime, I have a really hack-y workaround:
This will give you a Filter Slicer with all of the values you want to see, then a group of values at the very bottom that contains all the values you don't want to see. If you don't have too many values you do want to see, you can even format this filter slicer as a List and resize it so that all of the values except for the Z group at the bottom show up.
Hi,
There is a workaround to it:
1. Create a copy of the slicer so you have two slicers on the page (let's call them "SL1" and "SL2")
2. On SL2, select the values you want to see appear in the actual slicer (this is NOT using the visual filter of the slicer, just select the values from the actual slicer)
3. SL1 will now be showing ONLY the values you have selected in SL2.
4. With SL1 switch "ON" background and set transparency to 0%
5. reduce the size of SL2 to something smaller than SL1 and Drop it "behind" SL1 to hide it.
This will get the work done.
Thanks @GregM for the edit
Thanks @sumit4732 That worked...
To be clearer for other users...
1. Create a copy of the slicer so you have two slicers on the page (lets call them "SL1" and "SL2")
2. On SL2, select the values you want to see appear in the actual slicer (this is NOT using the visual filter of the slicer, just select the values from the actual slicer)
3. SL1 will now be showing ONLY the values you have selected in SL2.
4. With SL1 switch "ON" background and set transparency to 0%
5. reduce the size of SL2 to something smaller than SL1 and Drop it "behind" SL1 to hide it.
Thanks again @sumit4732
Best Regards
Gerard
Thanks @sumit4732 It's a great workaround! Just wanted to add that you can hide SL2 in the Selection Pane, it will eliminate the need for step 4 and 5.
I just saw another option for this that @Mike_Carlo came up with. Since we can show and hide things on a page, he just copied a slicer, filtered it, then hid the slicer. The other slicer retains the same context without the filtered out value and no one is the wiser. A bit harder for someone else to discover 🙂 but its super quick without the need to layer things. As a seperate note I just thought of, it would be easy to just create a bookmark page that contained the filtered slicers, would be easier to discover.
This 'solution' is great if you have only a few visualizations that need interactions to be turned off. It is much more cumbersome of a 'solution' when you have a page of over 30 stacked visualizations.
Hi Mike,
Isn't your solution the same as using a Page/Report level filter? If not, what's the difference?
Thanks
Robin
@Anonymous The effect is the same, the difference is that the filters panel is available to the end user, and they can modify and remove those filters. This method effectively removes the capability of an end user to see or modify anything.
Both visual level filters and page level filters don't seem to apply to any slicer - even those that are downloaded from the marketplace.
Any news on how to solve this one? Also need to use a filter version.
Me too
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
103 | |
98 | |
98 | |
38 | |
37 |
User | Count |
---|---|
152 | |
120 | |
73 | |
72 | |
63 |