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
AlB
Community Champion
Community Champion

Synching slicers from different columns

Hi all,

Imagine we have a table Table1 with a Table1[Location] column. We place Location as a slicer in page 1 of a report. We then place Table1[Location] as a slicer in page 2 of the report. We can sync both slicers easily.

Now imagine we have a second table also with a Location column Table2[Location] and the same values as Table1[Location]. We place Table2[Location] as a slicer in page 3 of the report.

 

Is there a way to sync the slicer (based on Table2[Location]) in page 3 with the slicer (based on Table1[Location]) in page 1??

 

Many thanks           

7 REPLIES 7
lbendlin
Super User
Super User

Not really but you can force it, sort of, by creating a forced 1:M relationship from Table1 to Table2.  Power BI will initially tell you it wants a bidirectional 1:1 relationship between the tables but that will not work as table2 would then impact table1.

 

The real issue here is that you are not actually synching slicer 1 and slicer 2.  All you do is narrow down the slicer 2 options based on slicer 1 selections. But you could argue that the result is the same. 

 

See attached.

 

AlB
Community Champion
Community Champion

Ok, but then the sync would go only from Slicer 1 to Slicer 2, not from slicer 2 to slicer 1, correct?

Thanks

yes, that's how I interpreted your request.

AlB
Community Champion
Community Champion

@lbendlin 

I would like the sync to work both ways, like it does with the "native" sync between two slicers based on the same column

Thanks

 

Hi, @AlB 

You can consider creating a calculated table based on values from all locations in both tables, and then create sync slicers based on this new table.

 

Best Regards,
Community Support Team _ Eason

@v-easonf-msft 

But for that I can use just Table 1, right?

What I need is two different tables; reason being each location table will be filtering different fact tables downstream to avoid an ambiguity issue

 

I don't think that is possible with Power BI/Vertipaq. You may need to look at Qlik's associative model.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

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

August 2025 community update carousel

Fabric Community Update - August 2025

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