Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Daniel_B
Helper II
Helper II

Table of locations for Slicer Drill Down

Hi There

 

I have to source data tables which use the same list buildings and I want to be able to filter at different levels using slicers to drill down to the lowest levels available based on the previous selection for example 


Site 1 has 7 Departments and 8 Sub Departments

Site 2 has 10 Departments and 40 Sub Departments

 

If I select Site 1, then I should not be able to see any of Site 2's Departments and Sub Departments

 

I created individual tables and realised that meant the relationship was only at that level (Site -> Site but wasn't linked to Department)

 

I created a table in Excel which contains all of the Sites and Departments but it is at a row level so there are multiple versions of site 1 which doesnt' work either

 

What is the best way to create multi-level slicers (I don't want filters) to show the relationship between the Sites as per the above

 

Thanks

 

1 ACCEPTED SOLUTION
edhans
Super User
Super User

You should create the table at the same level of granularity as in your FACT table, or your data. Presumably that is at the department level. It wouldn't make sense if Site data was in the FACT table as you couldn't tell the difference between Site 1/Dept 1 and Site 1/Dept 2.

 

But if your FACT table is at the department level, then your DIMENSION table for location would be at the Department level as well and look something like this:

 

DepartmentSite
Dept 1Site 1
Dept 2Site 1
Dept 3Site 1
Dept 4Site 2
Dept 5Site 2
Dept 6Site 2

 

Then you relate Location[Department] to the department in your FACT table as a One-To-Many, and will be able to slice by department or site.



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

View solution in original post

2 REPLIES 2
v-lionel-msft
Community Support
Community Support

Hi @Daniel_B ,

Are your fact table like this?

nn4.PNG

Maybe you can use hierarchical filter:

nn5.PNG

nn6.PNG

 

Best regards,
Lionel Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

edhans
Super User
Super User

You should create the table at the same level of granularity as in your FACT table, or your data. Presumably that is at the department level. It wouldn't make sense if Site data was in the FACT table as you couldn't tell the difference between Site 1/Dept 1 and Site 1/Dept 2.

 

But if your FACT table is at the department level, then your DIMENSION table for location would be at the Department level as well and look something like this:

 

DepartmentSite
Dept 1Site 1
Dept 2Site 1
Dept 3Site 1
Dept 4Site 2
Dept 5Site 2
Dept 6Site 2

 

Then you relate Location[Department] to the department in your FACT table as a One-To-Many, and will be able to slice by department or site.



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.