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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
RandyPgh
Resolver III
Resolver III

Dimension Driving Dimension Selection through Fact

A single fact table attaches to two conformed dimensions. Dimension_1 is actively attached. Dimension_2 is inactively attached. For this fact table only, the goal is for Dimension_2 to filter the list of Dimension_1 as associated to the Fact table, but then to disappear from the calculation, allowing only related Dimension_1 records to affect the results. Another way to look at the goal is that Dimension_2 chooses the Dimension_1 values, but then all Fact records associated with Dimension_1 are calculated, ignoring the Dimension_2 choice. Note that other dimensions might be affecting the results, but these describe the interactions of these two dimensions.

 

For example, I have tried the following DAX that does not accomplish the goal. What does get returned is filtered by both Dim1 and Dim2.

 

VAR __dim1_list =
CALCULATETABLE(
        VALUES('Fact'[Dim1Key]),
        USERELATIONSHIP('Fact'[Dim2Key],'Dim2'[Dim2Key])
)
VAR __result =
    CALCULATE(
        COUNTROWS('Fact'),
        __dim1_list
    )
 
I am obviously not understanding something about the processing of the contexts, but not sure what.
1 ACCEPTED SOLUTION
RandyPgh
Resolver III
Resolver III

It was solved with a bridge table between Dim2 and the Fact table. The bridge contains the appropriate Dim1 and Dim2 pairings, with a relationship {Dim2.Dim2Key, Bridge.Dim2Key} one-to-many join and a {Bridge.Dim1Key, Fact.Dim1Key} many-to-many join. Both joins are uni-directional toward the fact table.

 

Thanks for your suggestions @amitchandak .

 

View solution in original post

2 REPLIES 2
RandyPgh
Resolver III
Resolver III

It was solved with a bridge table between Dim2 and the Fact table. The bridge contains the appropriate Dim1 and Dim2 pairings, with a relationship {Dim2.Dim2Key, Bridge.Dim2Key} one-to-many join and a {Bridge.Dim1Key, Fact.Dim1Key} many-to-many join. Both joins are uni-directional toward the fact table.

 

Thanks for your suggestions @amitchandak .

 

amitchandak
Super User
Super User

@RandyPgh , Try one of the two ways

 

CALCULATE(
COUNTROWS('Fact'),
USERELATIONSHIP('Fact'[Dim2Key],'Dim2'[Dim2Key])
)

or


CALCULATE(
COUNTROWS(summarize('Fact', 'Fact'[Dim1Key])),
USERELATIONSHIP('Fact'[Dim2Key],'Dim2'[Dim2Key])
)

Share with Power BI Enthusiasts: Full Power BI Video (20 Hours) YouTube
Microsoft Fabric Series 60+ Videos YouTube
Microsoft Fabric Hindi End to End YouTube

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

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.