Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Is there a way to get a slicer to effect another slicer that came from a different data source? E.G if had three slicers from table A say Date, Name and Category, would it possible to have the option picked in each of these apply the same filters to the three slicers from Table B if they had the same fields (Date, Name and Category)?
I am trying to avoid joining these tables as they contain many of the same columns so was trying to find workarounds and having slicers trasfer between the two tables would be useful.
Hi! Your model should be in a star schema format with fact(s) and dimensions. The fields that are the same between your two tables are dimensions (i.e. date, product name, etc.). Your fact tables should only have keys and values that you want to aggegate. The fact tables would connect to the dimension tables - then, if you filter to product name A from the product dim table, this would filter any fact table that is joined to that dim table. http://powerbiwithme.com/2023/07/30/the-star-schema-edition/
Proud to be a Super User! | |
hi, unfortunately in this case the only two tables I have are the two that share similar fields and they are both fact tables so I am not sure this will work in this case.
Hi @audreygerred ,thanks for the quick reply, I'll add further.
Hi @Cheezeduckies ,
Regarding your question, if there is no relationship established between tables. Then the filtering effect of the slicer is not passed.Suppose you want to filter two tables using the 'Date' column, you can create a linked table.
The Table data is shown below:
Please follow these steps:
1. Use the following DAX expression to create a table
Table = DISTINCT(UNION(VALUES('Table1'[Date]),VALUES('Table2'[Date])))
2.Create a new linked table in excel and connect it using Power BI Desktop.
3.Creating table-to-table relationships.
4.Final output
User | Count |
---|---|
84 | |
71 | |
71 | |
68 | |
55 |
User | Count |
---|---|
94 | |
92 | |
91 | |
77 | |
70 |