Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
After reading this, https://community.fabric.microsoft.com/t5/Desktop/Creating-a-Hierarchy-from-Multiple-Tables-using-a-... I learned that you can make a heirarchy in your visual from different columns from multiple tables if they have relationships made between them. This does work for visuals as far as I can tell, however, it doesn't work for a slicer?
Is there a way to get it to work for a slicer as well?
We're changing up our model to be able to handle duplicate entries, so we're using bridging tables to go from a 1:MANY (to bridge) and then MANY:1 to the component values, and all this works as excpected, but I also need this to work for a slicer or else it's going to break everything.
Here you will notice the bottom visual is working, and that 3'rd level of the heirarchy comes from a completley different table and it works, if I try to do the same to the slicer at the top, it says relationships are not supported.
If your fields have a hierarchical relationship then they should reside in the same (or a dependent) table.
If they don't form a natural hierarchy, use separate slicers.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
124 | |
79 | |
50 | |
38 | |
38 |
User | Count |
---|---|
195 | |
80 | |
70 | |
51 | |
42 |