Forum Discussion
Slicers Issue in Power BI
Hi everyone,
I'm facing a strange problem with the slicers in power bi service but it works well in desktop.
The issue is the follwoing:
When I select one value in a slicer (Desk_n -> select “Desk A”) and then I select a value in another slicer (account -> select "315"), at that moment the value displayed in the slicer card Desk_n changes to “All” instead of “Desk A” that I previously selected… When I click on the arrow to open the selection of Desk_n, I can see that "Desk A" is selected... This means that the desk selected is not displayed on the card and can lead to a misleading interpretation.
I attacehd a graph to summarize the issue.
Can you please help?
Thank you very much
Hi noah_pbix ,
Thanks so much for sharing the details and screenshot that makes things a lot clearer. What you’re seeing isn’t due to your data model or slicer setup. It’s actually a known quirk in Power BI Service: sometimes the slicer header shows “All” even when a specific value is still selected. Don’t worry, your selection isn’t lost and the filters are still working behind the scenes. If you open the slicer dropdown, you’ll see “Desk A” is still checked.
This usually pops up when multiple slicers interact or if you switch slicers and it affects another. It can also happen when you leave and come back to the report page, as the visuals reload. An easy fix is to add a card visual with a DAX measure like SELECTEDVALUE('Desk'[Desk_n], "All") that way, users always see the right selection, even if the header says “All.”
Your setup’s totally fine; it’s just a display thing in the Service. The engineering team knows about it and is working on a fix. In the meantime, the card workaround should help users keep track of what’s actually selected.
Thank you,
Tejaswi
Community Support Team
9 Replies
- Shahid12523
Community Champion
Power BI Service sometimes shows “All” in a slicer card even when one item is selected because the visual doesn’t properly reflect the filter context. To fix this, create a measure using SELECTEDVALUE() to show the selected item explicitly, and use that measure in the card instead of the default field. This makes the displayed value match the actual slicer selection.
hi Shahid12523 ,
Thank you very much for your reply and help. Not sure to fully understand. Are you indicating that the issue in the Slicer cannot be solved but one option to display with evidence the selection from the slicer is to create a separeted card that includes a measure built with SELECTEDVALUE() ? (Because a measure cannot be used in a slicer?)
Thank you very much for your help
v-tejramaCommunity Support
Hi noah_pbix ,
Thank you Shahid12523 and tayloramy for the response provided!
Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Thank you for your understanding!
Hey, we're having the same issue in our tenant. Multiple users have reported that slicers are showing "all" when a value is actually selected. They can only see the value is selected by clicking on the slicer dropdown. This is happening when users select a value, navigate away, then return to the page. It can also happen as described by changing another slicer
- v-tejrama
Hi noah_pbix ,
Thanks so much for sharing the details and screenshot that makes things a lot clearer. What you’re seeing isn’t due to your data model or slicer setup. It’s actually a known quirk in Power BI Service: sometimes the slicer header shows “All” even when a specific value is still selected. Don’t worry, your selection isn’t lost and the filters are still working behind the scenes. If you open the slicer dropdown, you’ll see “Desk A” is still checked.
This usually pops up when multiple slicers interact or if you switch slicers and it affects another. It can also happen when you leave and come back to the report page, as the visuals reload. An easy fix is to add a card visual with a DAX measure like SELECTEDVALUE('Desk'[Desk_n], "All") that way, users always see the right selection, even if the header says “All.”
Your setup’s totally fine; it’s just a display thing in the Service. The engineering team knows about it and is working on a fix. In the meantime, the card workaround should help users keep track of what’s actually selected.
Thank you,
Tejaswi
Community Support Team
