Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I have 3 tables that are linked together using bridge tables (as seen below).
What I am trying to do is to have columns in the DIM_Contact table being filtered by both the DIM_PractitionerClass (2 columns) and DIM_Licence columns (1 column). This works to an extent though it does not filter all the data in the way that I need to.
What is the best practise for this? Do I need to have another bridge table to link DIM_PractitionerClass and DIM_Licence?
Solved! Go to Solution.
Hi @Austen229022 - Common bridge table that connects these dimensions in a many-to-many relationship context.
If filtering isn't working as expected, you might need a common bridge table to link DIM_PractitionerClass and DIM_Licence to DIM_Contact. you ensure that your data model is optimized for filtering the Dim Contact table based on multiple dimensions. This approach leverages a common bridge table and ensures that relationships are correctly established and cross-filtering works as expected.
Ensure that cross-filtering is set to "Both" for these relationships to ensure proper filtering across the tables.
Try the above suggested changes and let's see.
Did I answer your question? Mark my post as a solution! This will help others on the forum!
Appreciate your Kudos!!
Proud to be a Super User! | |
Hi @Austen229022 - Common bridge table that connects these dimensions in a many-to-many relationship context.
If filtering isn't working as expected, you might need a common bridge table to link DIM_PractitionerClass and DIM_Licence to DIM_Contact. you ensure that your data model is optimized for filtering the Dim Contact table based on multiple dimensions. This approach leverages a common bridge table and ensures that relationships are correctly established and cross-filtering works as expected.
Ensure that cross-filtering is set to "Both" for these relationships to ensure proper filtering across the tables.
Try the above suggested changes and let's see.
Did I answer your question? Mark my post as a solution! This will help others on the forum!
Appreciate your Kudos!!
Proud to be a Super User! | |
Hi Rajendraongole1,
If I were to have the two standard bdige tables like I have now, and another joint bridge table wouldnt that cause cardinality issues?
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 47 | |
| 43 | |
| 40 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 70 | |
| 67 | |
| 32 | |
| 27 | |
| 25 |