Forum Discussion
One slicer for two tables
All,
I have page 1 on my report using a slicer that filters map and data based on status. I added a new table to the report. This table has some of the same values. I created a relationship from first table to the second table. Unfortunately the one slice I have does not update the second. The relationship I am using is not the one in the slicer. I attempted to link the two fields one in each data set that my current slicer is using, but it would not allow me to establish the relationship. So I used the next field that linked.
Any help would be appreciated.
Figured it out, the two tables had to be on the same page. It now functions. Suprised that using a relationship will work on same page but not a different page in the same report.
3 Replies
A single slicer should be able to filter related tables, even if the slicer is not made using the field for the relationship. Two things that could affect your slicer's ability to filter your data are how the relationship is set up, and what measure you're using for your calculations.
Here's an article on creating relationships that might help get more familiar with them. If that doesn't do it, can you include more information about your data structure and what calculation isn't getting filtered by the slicer?
Thank you for the feedback. So the unique table(TableA) with common values I created in the desktop will work with one(Table1) or the other(Table2) when using it as a slicer. But it will work together for both Table1 and Table2 at the same time. Is this because I am using two different pages in the report
Figured it out, the two tables had to be on the same page. It now functions. Suprised that using a relationship will work on same page but not a different page in the same report.
