How to Automatically Reset Slicer Selections When Changing value in Slicer in Power BI?

[Amyries]

Hi everyone,

I have a question regarding Power BI slicer behavior:

1. Initially, I select SprintKey = "199_S1" and choose Week 1 (2025/02/10) and Week 31 (2025/09/01) in (2.1), (3.1) slicers.

- Then, I change the SprintKey to a different value (e.g., "199_S2"), but Power BI still remembers the previous week selections. This is not ideal for my workflow.

Note: I ask chatGPT for reference, it's suggested me create the reset button. But I’m looking for a more user-friendly or automatic solution.
My question: Is there a way to automatically reset or clear the week selection slicer whenever I change the value in the SprintKey slicer, without requiring users to manually click a reset button?

Here is file

Thank you in advance for your help!

[v-achippa]

Hi @Amyries,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @AnalyticPulse, @LED_General and @OwenAuger for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[Amyries · Accepted solution]

@v-achippaThe issue is not resolved yet, and I might have to tell my client that it’s a limitation of the tool.

[v-achippa]

Hi @Amyries,

Thank you for the response, I hope you have updated to your client that it’s a limitation of the tool.

If you have any further issue, please raise a new thread in the community forum, we are ready to assist you on it.

Thank you for being part of Microsoft Fabric Community.

Thanks and regards,

Anjan Kumar Chippa

[OwenAuger]

One possible workaround is similar to the method described here:

https://exceleratorbi.com.au/slicer-values-dont-clear-after-changing-a-second-slicer/

Caveats:

• This method only makes sense when single selections are made on the first slicer.
• It also requires copies of the columns used on the slicers that have to reset (the 2nd & 3rd slicers in this example), which are then linked to field parameter columns added to the table containing the column used on the first slicer.

I have set up an example using your PBIX (attached).

Setup steps:

1. Add these columns to From_EVM_Dates, all equal to From_EVM_Dates[週].

One column must be added for each distinct SprintKey value (three in this case):

週 1 = 
From_EVM_Dates[週]
------------------
週 2 = 
From_EVM_Dates[週]
------------------
週 3 = 
From_EVM_Dates[週]

(This can be automated by constructed tables in Power Query but the sample uses DAX calculated columns).

2. Add these columns to To_EVM_Dates, all equal to To_EVM_Dates[週].

One column must be added for each distinct SprintKey value (three in this case):

週 1 = 
To_EVM_Dates[週]
------------------
週 2 = 
To_EVM_Dates[週]
------------------
週 3 = 
To_EVM_Dates[週]

(This can be automated by constructed tables in Power Query but the sample uses DAX calculated columns).

3. Add these two columns to Project_EVM (just one possible way of defining these columns):

From 週 Column = 
VAR SprintKeyRank =
    RANK ( DENSE, DISTINCT(Project_EVM[SprintKey]) , ORDERBY ( Project_EVM[SprintKey] ) )
RETURN
    "From_EVM_Dates[週 " & SprintKeyRank & "]"
-----------------------------------------------------------------------------------------
To 週 Column = 
VAR SprintKeyRank =
    RANK ( DENSE, DISTINCT(Project_EVM[SprintKey]) , ORDERBY ( Project_EVM[SprintKey] ) )
RETURN
    "To_EVM_Dates[週 " & SprintKeyRank & "]"

4. Using Tabular Editor (or TMDL view), add a JSON Extended Property to each of the columns from step 3, equal to {"version":3, "kind"2}. These two columns will then be recognised as field parameter columns.

5. Change the 2nd & 3rd slicer fields to Project_EVM[From 週 Column] and Project_EVM[To 週 Column].

In the field context menu, select "Show values of selected field":

6. Now changing the SprintKey slicer selection will reset the 2nd & 3rd slicers.

Note that making no selection or multiple selections on the SprintKey slicer would produce an unwanted hierarchy on the other two slicers.

Would something like this work for you?

[Amyries]

Thank you for your detailed responses!
However, I am wondering: if SprintKey is increases, does that mean I need to manually create the corresponding 週 (number) in From_EVM_Dates and To_EVM_Dates?

[OwenAuger]

@Amyries Good point! The need for a potentially growing set of copies of these columns is the main drawback with this method.

I consider this method a workaround and certainly not good modelling practice. Model table schemas should generally not change over time.

I would only recommending using this method if you can automate the additional columns in Power Query or further upstream. I wouldn't recommend adding these columns via DAX in practice.

Also, it may not be desirable to use this method  if the number of SprintKey values becomes particular large.

[AnalyticPulse]

hi @Amyries,

cant you just use the clear selection buttonthata is built in on the slicer? because if user selected some options from slicer he is aware that there is certain selection on report and he is viewing the desired data, and if he doesn't want the selections anymore he can just clear the selection. 

My Work:
Analytic Pulse Blog 
Docynx Productivity Tools 

[LED_General]

This is probably the best solution in the current version.

There is no automatic slicer reset now.