Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Omesh
Helper I
Helper I

Hi Experts, Need help in slicer

I have a values in the slicer as displayed in a table, and there are two slicers, Slicer 1 and Slicer 2. Slicer 1 has an interaction with Slicer 2, but not the other way around. Initially, Slicer 1 is set to "A" and Slicer 2 is set to "1," as shown in the figure. When I change Slicer 1 value from "A" to "B," everything works fine. However, when I change Slicer 1 to "C," since Slicer 2 doesn't have any corresponding value as "1" it displays all blank visualization. Is there any setting that can automatically change Slicer 2 to "1+" in this situation?

Table

Slicer 1Slicer 2
A1
 2
B1
 2
 3
 4
C1+
 2+
 3+

 

Initially 

Slicer 1Slicer 2
A1


Current output 

Slicer 1Slicer 2
C1

 

Expected output

Slicer 1Slicer 2
C1+


Thanks in advance 

1 ACCEPTED SOLUTION
OwenAuger
Super User
Super User

Hi @Omesh 

Slicers can't natively "reset" when their selection becomes invalid.

However, there is a workaround involving field parameters. I have attached a small example.

I have assumed Slicer 1 & Slicer 2 only allow single selection. This can be relaxed for Slicer 2 without changing anything, but if relaxed for Slicer 1 it complicates things.

 

The basic idea is:

  1. SlicerTable contains the original columns Slicer 1 & Slicer 2.
  2. Create a new 'Slicer 2' table that contains one column per distinct value of Slicer 1 (3 in this example). These columns are identical and each contains the distinct values of Slicer 2.
  3. Create a 'Slicer 2 Field Parameter' that allows selection of the 3 columns of 'Slicer 2', with a column corresponding to the values of Slicer 1.
  4. Create a bi-directional 1:many relationship from 'Slicer 2' to SlicerTable.
  5. On the report page:
    1. Slicer 1 slicer uses SlicerTable[Slicer 1]
    2. Slicer 2 slicer uses 'Slicer 2 Field Parameter'[Slicer 2 Parameter]
    3. There is a hidden slicer using 'Slicer 2 Field Parameter'[Slicer 1] that is synced with the main Slicer 1 slicer.
  6. Now, whenever the selection on Slicer 1 is changed, the Slicer 2 slicer will reset. If single-select is enabled, it will reset to the first available value.

OwenAuger_1-1697451007304.png

 

 

OwenAuger_0-1697450996593.png

Please take a look at attached PBIX and see if that helps 🙂

 

Regards


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
LinkedIn

View solution in original post

1 REPLY 1
OwenAuger
Super User
Super User

Hi @Omesh 

Slicers can't natively "reset" when their selection becomes invalid.

However, there is a workaround involving field parameters. I have attached a small example.

I have assumed Slicer 1 & Slicer 2 only allow single selection. This can be relaxed for Slicer 2 without changing anything, but if relaxed for Slicer 1 it complicates things.

 

The basic idea is:

  1. SlicerTable contains the original columns Slicer 1 & Slicer 2.
  2. Create a new 'Slicer 2' table that contains one column per distinct value of Slicer 1 (3 in this example). These columns are identical and each contains the distinct values of Slicer 2.
  3. Create a 'Slicer 2 Field Parameter' that allows selection of the 3 columns of 'Slicer 2', with a column corresponding to the values of Slicer 1.
  4. Create a bi-directional 1:many relationship from 'Slicer 2' to SlicerTable.
  5. On the report page:
    1. Slicer 1 slicer uses SlicerTable[Slicer 1]
    2. Slicer 2 slicer uses 'Slicer 2 Field Parameter'[Slicer 2 Parameter]
    3. There is a hidden slicer using 'Slicer 2 Field Parameter'[Slicer 1] that is synced with the main Slicer 1 slicer.
  6. Now, whenever the selection on Slicer 1 is changed, the Slicer 2 slicer will reset. If single-select is enabled, it will reset to the first available value.

OwenAuger_1-1697451007304.png

 

 

OwenAuger_0-1697450996593.png

Please take a look at attached PBIX and see if that helps 🙂

 

Regards


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
LinkedIn

Helpful resources

Announcements
July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.