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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
jdusek92
Advocate III
Advocate III

Data Modeling - Multiple Fact Columns in one dimension Table / one Hierarchy

Hello!

I need to create a report where I can display multiple granularity details in a single fields/column of a Matrix.

This basically means that some rows from the source table will be counted multiple times

Here is the example of the data:

 

jdusek92_2-1712778123609.png

 

 

 

 So Far I have come up with these sutions:

 

  1. Create a Composite Key and a Dim Table with all the possible Composite Keys. This works well, but it uses many to many relationship and does not follow the Star Schema. Can you see any possible future problems with this solution?
  2. Create a disconnected Dim Table and create a measure with a condition on Dim Table SELECTEDVALUE. The problem is I will have a lot of measures and I dont want to have basically tripled the amount of DAX count in each measure due to SWITCH cases 
  3. Create a connected Dim Table, connected on Grade. Then for SELECTEDVALUE(Dimension) = Managers/Senior use a custom calculation. But again this would triple the amount of DAX code.

 

I do not want to expand the rows of the source table to multiple rows, I want 1 row = 1 employee

I would prefer the first solution using Many to many relationship, because it seems the most efficient when it comes to writing the measures. But I am not sure of any future complications/implications this solution might bring.

 

I would like to know your opinion or maybe you have a different solution!

 

Thank you 

Jakub

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

Your dimension table 2 needs to stay disconnected for this to work. Your composite key (table 1) is not required, and table 3 is not required either.

 

Repeating data in the same visual is a design red flag.

 

lbendlin_0-1712793097775.png

see attached.

 

View solution in original post

1 REPLY 1
lbendlin
Super User
Super User

Your dimension table 2 needs to stay disconnected for this to work. Your composite key (table 1) is not required, and table 3 is not required either.

 

Repeating data in the same visual is a design red flag.

 

lbendlin_0-1712793097775.png

see attached.

 

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors