Forum Discussion
How to Automatically Update a Single-Select Slicer When Parent Slicer Changes?
Hi everyone,
I have a Power BI report with two single-select slicers that are hierarchical:
Regional Manager (RM) – Parent slicer
Team Manager (TM) – Child slicer, dependent on the selected RM
Issue:
When I select a Regional Manager, the Team Manager slicer updates its available options to show only the relevant managers. However, the previously selected Team Manager does not reset or update.
For example:
Initially, I select RM1 → The Team Manager slicer shows TM1.1, TM1.2 → let the selected be TM1.1
Then, I change the Regional Manager to RM2.
The Team Manager slicer updates to show only TM2.1, TM2.2, but it still shows TM1.1 as selected (even though TM1.1 does not belong to RM2).
What I Need:
I want the Team Manager slicer to automatically update and select a new valid value when the Regional Manager is changed, preferably:
The first available Team Manager (alphabetically) OR
A random Team Manager under the selected RM
What I've Tried:
Edit Interactions: Ensured that the RM slicer filters the TM slicer correctly. The list updates, but the selection stays on the previous value.
DAX Measures: Created a measure using MIN(Employees[Team Manager]) to get the first available TM, but measures cannot be used for default slicer selection.
Hierarchy Slicer: Considered merging both slicers into a hierarchy slicer, but I need them as separate slicers because of seperate graphs for both managers.
Bookmarks: Tried using bookmarks to reset selections, but they aren’t dynamic.
Question:
How can I make the Team Manager slicer automatically select the first available value whenever the Regional Manager is changed? Is there any workaround using DAX, Power Query, or another Power BI feature to achieve this behavior?
Any help would be greatly appreciated!
Thanks in advance!
Hi nks98
This is a general issue with the core slicer visuals unfortunately, sometimes called "sticky slicers".
Solutions I can suggest:
- Use a technique with field parameters to "reset" the Team Manager slicer when the Regional Manager slicer is changed. The TM slicer should not filter the RM slicer (via edit interactions), and the RM slicer has to force a change in a field parameter containing copies of the TM column.
- Blog post by Matt Allington
(you may need to use a plugin such as Just Read for reader view as the site is displaying oddly at the moment). - Video on same method
- Blog post by Matt Allington
- Use a Chiclet Slicer for Team Manager (if you are happy with the appearance).
- Again, the TM slicer should not filter the RM slicer.
- The TM slicer (Chiclet) should have Forced selection enabled.
Here's a small recording of the Chiclet Slicer version using Continent/Country. I used Chiclet slicers for both in this example but only the 2nd slicer needs to be Chiclet Slicer.
Hopefully similar functionality comes to the core visuals soon!
(The Force selection option on the newer core slicer visuals unfortunately doesn't work like the Chiclet slicer.)
- Use a technique with field parameters to "reset" the Team Manager slicer when the Regional Manager slicer is changed. The TM slicer should not filter the RM slicer (via edit interactions), and the RM slicer has to force a change in a field parameter containing copies of the TM column.
3 Replies
Hi nks98
This is a general issue with the core slicer visuals unfortunately, sometimes called "sticky slicers".
Solutions I can suggest:
- Use a technique with field parameters to "reset" the Team Manager slicer when the Regional Manager slicer is changed. The TM slicer should not filter the RM slicer (via edit interactions), and the RM slicer has to force a change in a field parameter containing copies of the TM column.
- Blog post by Matt Allington
(you may need to use a plugin such as Just Read for reader view as the site is displaying oddly at the moment). - Video on same method
- Blog post by Matt Allington
- Use a Chiclet Slicer for Team Manager (if you are happy with the appearance).
- Again, the TM slicer should not filter the RM slicer.
- The TM slicer (Chiclet) should have Forced selection enabled.
Here's a small recording of the Chiclet Slicer version using Continent/Country. I used Chiclet slicers for both in this example but only the 2nd slicer needs to be Chiclet Slicer.
Hopefully similar functionality comes to the core visuals soon!
(The Force selection option on the newer core slicer visuals unfortunately doesn't work like the Chiclet slicer.)
- Use a technique with field parameters to "reset" the Team Manager slicer when the Regional Manager slicer is changed. The TM slicer should not filter the RM slicer (via edit interactions), and the RM slicer has to force a change in a field parameter containing copies of the TM column.
Hi nks98,
Thank you for reaching out to Microsoft Fabric Community Forum.
As suggested by super user you can use chiclet slicer for teammanager slicer or use BUTTON SLICER for Teammanager slicer.
It looks like as Below
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay PabbuHi nks98,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.Regards,
B Manikanteswara Reddy
