Selection on one slicer preserved when another slicer is selected

[karimm]

Hi All

I have 2 slicers where one is interacting with the other.

1. Project/Release slicer has 3 dimensions: Project, Active/Inactive, Release

2. Active Only single option slicer that displays a single checkbox

I'm having a UX problem described in the image below (the squared shared are for hiding values).

When both Active and Inactive values are selected on first slicer and then "ACtive only" checkbox is selected, reopening the first slicer, will still show Inactive as selected.

This is not causing problems in the calculations but rather might confuse the inexperienced user.

Is there a way to make powerbi "refresh" the selections displayed once a value in another slicer is selected?

[SamWiseOwl · Accepted solution]

Hi @karimm 

I have had a similar issue before and the only way I could solve it was using Bookmarks.
So instead of have a slicer that ticks Active, I had a button named Active that reset the slicer to tick all the Active items.

The issue then is not know what the originally had ticked 😕

Daft question but could you not Have your Active column before your Project in the slicer?

That way they tick Active, Inactive or Select All at the start of each slicer.

[karimm]

Thank you for your answer and sorry about the delay.

Yes, I though 1 of 2 compromises... either have it like now or use bookmarks but then suffer from resetting the selections...

Regarding having the Active/Inactive as the top of the hierarchy, I don't think that's improving things, as users will need to scroll a lot between the 2 nodes to find their relevant releases.

[v-aatheeque]

Hi @karimm ,

Just a quick reminder that the @SamWiseOwl has already addressed your query regarding slicer interactions and UI behavior in Power BI.

• The issue you’re seeing is more of a UX limitation, not a calculation issue.

• As a workaround, suggested using Bookmarks tied to a button (e.g., "Active Only") to reset the slicer to display only Active items.

• Additionally, rearranging the slicer by placing the Active column before Project could improve clarity when making selections.

Let us know if you need further help implementing the suggested approach or if you’re exploring an alternative method.

Happy to assist further!

[v-aatheeque]

Hello @karimm 
Just a friendly reminder that @SamWiseOwl  has already responded to your question about slicer interaction and UI behavior in Power BI.

The behavior you're encountering is a user experience limitation, rather than a data or calculation issue.

As a workaround, it was suggested to use a Bookmark tied to a button (like “Active Only”) to help reset the slicer view effectively.

Also, reordering the slicer fields placing the Active field before Project could make the interface more intuitive when selecting items.

If you’d like support implementing any of these suggestions or are considering a different approach, feel free to reach out we’re happy to assist!

[v-aatheeque]

Hi @karimm ,

Just a friendly reminder that @SamWiseOwl  has already responded to your question regarding slicer interaction and UI behavior in Power BI.

The behavior you're seeing is a user experience limitation, not a data or calculation issue.

As a workaround, it was suggested to use a Bookmark tied to a button (like “Active Only”) to effectively reset the slicer view.

Additionally, reordering the slicer fields placing the Active field before Project  may help make the interface more intuitive for users.

If you'd like any help implementing these suggestions or if you're exploring an alternative approach, feel free to reach out  we're happy to assist!

If we don’t hear back, we may close this thread in line with our community guidelines, but you’re always welcome to post a new query anytime.
Thank you for being part of the Microsoft Fabric Community!