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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
billuran09
Frequent Visitor

Common Dependent dimensions in data model

Hello,

I have multiple fact tables.

Region, Department, Quantity

Region, Department, Sales

Have shared dimension tables for region and department

My issue i have a new mapping table that assigns further attributes to the regiona and department

Region, Department, Leader (of region department combo)

How can build Leader or other attricbutes to the fact tables for slicing and dicing and if I filter leader is shows me the measure.

 

1 obvious solution but i dont think it is right is to merge region department into 1 column for all tables and make a key off that, but i dont think thats best practice correct?

How can build Leader to the fact tables for slicing and dicing and if I filter leader is shows me the meausre.

 

 

 

 

1 ACCEPTED SOLUTION
VasTg
Memorable Member
Memorable Member

@billuran09 

 

You should use the RDL(Region;Department;Leader) as a bridge table between facts and dimension. For all the Region and Department combination, you should have a single row in this table(Leader column value should be unknown/undefined if there isn't any leader entry - but the row must exist)

 

Short forms:

RDL(Region;Department;Leader); Create a key column combining Region and Department, Lets call it as Bridge_key

R(Region)

D(Department)

Facts - Create a key column combining Region and Department in Sales and Quantity fact, Lets call it as Sales_key in sales fact and Quantity_key in Quantity fact.

 

Now define the relationships as below..

 

R->RDL(using Region ; 1 to Many)

D->RDL(Using Department; 1 to Many)

RDL to facts(Bridge_key to Sales_key and Quantity_key)

 

You should be able to filter by Leader(from RDL) or Region(from R) or department(from D).

 

If this helps, mark it as a solution. Reply if you have any questions.

Kudos are nice too.

 

 

 

 

 

Connect on LinkedIn

View solution in original post

3 REPLIES 3
VasTg
Memorable Member
Memorable Member

@billuran09 

 

You should use the RDL(Region;Department;Leader) as a bridge table between facts and dimension. For all the Region and Department combination, you should have a single row in this table(Leader column value should be unknown/undefined if there isn't any leader entry - but the row must exist)

 

Short forms:

RDL(Region;Department;Leader); Create a key column combining Region and Department, Lets call it as Bridge_key

R(Region)

D(Department)

Facts - Create a key column combining Region and Department in Sales and Quantity fact, Lets call it as Sales_key in sales fact and Quantity_key in Quantity fact.

 

Now define the relationships as below..

 

R->RDL(using Region ; 1 to Many)

D->RDL(Using Department; 1 to Many)

RDL to facts(Bridge_key to Sales_key and Quantity_key)

 

You should be able to filter by Leader(from RDL) or Region(from R) or department(from D).

 

If this helps, mark it as a solution. Reply if you have any questions.

Kudos are nice too.

 

 

 

 

 

Connect on LinkedIn

Cheers, this is kind of what I was thinking just wasnt sure if creating a key column inside the facts table was best practice. IE merging the columns together.

@billuran09 

 

Unfornately, you cannot define a relationship with composite key. You have to have a single column.

 

If this helps, mark it as a solution

Kudos are nice too.

Connect on LinkedIn

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

September Power BI Update Carousel

Power BI Monthly Update - September 2025

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

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 Kudoed Authors