Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
The new slicer filtering is great but it appears to be broken when using the 'select all' functionality. Is this just me?
I read it works as expected form product team but from the user perspective this is definetly not what we expect to happen! Still unsolved even if a lot of people want that feature. thanks microsoft
This issue still seems to be present in the June 2023 version. Has anyone come up with a solution yet? It's creating an awful lot of extra effort to produce a workaround.
I am having the same issue in 2022. Still seems like the issue is not solved? Unless there is a solution that someone has found that I am not seeing.
Back in 2020 I got the response to this that it works as designed:
https://community.powerbi.com/t5/Issues/quot-Select-all-quot-behavior-on-a-slicer-while-visual-level...
Not very user friendly
I have the same problem. Are there any solutions by now?
Any news on this topic?
Is it a bug?
Hi @Kashinoda ,
This looks weird as I don't experience any such functionality error at my end.
Just to sanity check on your data column that you are using as fileter: Can you confirm that you are using same "EMPLOYEE" column in your slicer and your Visual Level Filter?
Thanks,
Pragati
@Pragati11- I'm not the person you're addressing but I have the same issue.
I can confirm that the field used in the Filter visual and Table visual is the same field. I have just removed that same field from both visuals and then put it back in those visuals to see if removing it/adding it will trigger/refresh it to work. I'm afraid it still doesn't work.
@Kashinodahas provided a very good demonstration of this issue faced.
Hi @D_PBI ,
Apologies for tagging you by mistake.
@Kashinoda Can you confirm that you are using the same column in Visual level filter, your slicer and your chart?
As i am not able to replicate the same issue as you are facing. For me it works.
Thanks,
Pragati
Its still the case, latest version of Power BI Desktop with Excel as source. (Happens in SQL or Analysis Services too)
Using 'Select All':
Manually selecting 'Bob' and 'Aaron'
Relationship:
Hi @Kashinoda ,
Can you make your relationship bi-directional and see if this works?
If this helps and resolves the issue, appreciate a Kudos and mark it as a Solution! 🙂
Thanks,
Pragati
A bi-directional relationship doesn't solve the issue, I wouldn't expect it to either. I uploaded the PBIX, Try yourself:
https://drive.google.com/open?id=10QwYrgDYd4pGz8ZIGTUL92KRoh02Tyul
Hi @Kashinoda ,
I think you are not trying things the way they work:
1. Visual level filter of EMPLOYEE on your bar chart:
When you select anything on EMPLOYEE, the bar chart will get filtered as it is a visual level filter on your chart. This will not filter the slicer present on the report.
2. Trying to filter the chart using the Slicer present on the report:
This will affect the chart and filters it based on the selection in the slicer.
Now the above screenshots are from the pbix file that you shared.
It looks perfectly fine to me.
If this helps and resolves the issue, appreciate a Kudos and mark it as a Solution! 🙂
Thanks,
Pragati
I know how filters work, I've tried to make this example as basic as possible because people are misconstruing the problem. Let me clarify this issue again.
In June 2019 Microsoft added the ability to apply visual-level filters to a slicer, this meant you could restrict the available options within a slicer. This was not possible prior to this date.
In the example I showed, I've limited the slicer to only 'Aaron' and 'Bob. Here it is again for reference.
So here there are only 2 employees available on the slicer, but when I use the 'Select All' button it's selecting all employees - even the ones not included in the visual level filter for the slicer. I would expect to see the SalesAmount for Bob and Aaron only, I don't.
This is probably an oversight on how the slicer handles 'Select All', it's a bug.
Hi @Kashinoda ,
Looks like now I understand the problem. Thanks for detailed explanation 🙂
In order to fulfil your requiremnt, is it right to turn-off "Show Select-All Option" under Selection Controls for your slicer?
Because I think Select-All option still wors on the principal of selecting everything from the column on which slicer is based.
If this helps and resolves the issue, appreciate a Kudos and mark it as a Solution! 🙂
Thanks,
Pragati
How do we get confirmation this is a bug or not?
@Admin - I assume this user is actually a Power BI community admin representative. If so, please can you confirm if what has been described in this thread is a bug or not? If it is a bug, can you raise it as so, or instruct me on how to raise it?
@Kashinoda - don't wish to steal your thunder but how you're interpreting the functionality is how, I'd imagine, 99% of users would too.
Same issue here. I created a new topic about this in the 'Issues' section:
Hi @Kashinoda
Based on my test.the option works well.I would suggest you update to latest version of Power BI Desktop then try again.Below is the article about the new filter pane.
https://docs.microsoft.com/en-us/power-bi/power-bi-report-filter-preview
Regards,
I'm already on the latest version, I updated again anyway to be sure and the error is still there.
Visually it looks to work on the slicer, but the data does not filter. Try adding a visual to your demo and see if that works.
Hi @Kashinoda
Visual level Filters- These filters work only on visualizations.
Page level Filters- These filters work at the page of a report.
Report level Filters- These filters work on entire report including all pages and visualizations.
If you want the filter work for the two visuals,i would suggest you use page level filter.
Regards,
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
90 | |
86 | |
84 | |
68 | |
49 |
User | Count |
---|---|
138 | |
111 | |
103 | |
64 | |
60 |