Forum Discussion
Filtering across multiple columns, best practices? Many-to-Many or 1-to-Many (dim)
- 1 year ago
One to many is the better idea, here's another recommendation: if you have a User ID, ensure to have it on the Assignments/Claims table and then relate the Users ID single table containing all the hierarchy with it. That way you'll be able to filter the Claims table by the L3 Manager from your Users Catalog/Hierarchy.
- 1 year ago
Thank you for the reply. The one-to-many approach seems like the better approach for some cases, as long as the many table does not become too large.
If I am following correctly, I believe that your alternative would require having filters for each level of manager. Is that correct?
I did find a 3rd alternative, which I decided to use: using the HierarchySlicer custom visual along with a key on a ragged hierarchy chart. Here are some links on it. I was able to keep a proper star schema with this option:
Removing Blanks from Organizational Ragged Hierarchy in Power BI Matrix Visual - RADACAD
Thank you for the reply. The one-to-many approach seems like the better approach for some cases, as long as the many table does not become too large.
If I am following correctly, I believe that your alternative would require having filters for each level of manager. Is that correct?
I did find a 3rd alternative, which I decided to use: using the HierarchySlicer custom visual along with a key on a ragged hierarchy chart. Here are some links on it. I was able to keep a proper star schema with this option:
Removing Blanks from Organizational Ragged Hierarchy in Power BI Matrix Visual - RADACAD
Nice alternative! And to answer your question, yes, you'll need multiple filters but good thing is that you can create the hierarchy in the slicer itself 🙂
- BryMan_171 year agoRegular Visitor
Is there a way to remove the blanks in the default slicer when creating the hierachry? Using the filter pane options to remove (Blank)s would remove parents.
I believe the custom visual HierarchSlicer was created to solve this problem, but I'm curious if Power BI now has a away to do this in it's own Slicer now that I cannot find.
Thanks for your help on this!