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

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

nonunique dimension tables

Hi, 

I have a "Ticket" Fact table which is unique on Ticket Number.
Each ticket can have MANY labels, products, and components.

I'm trying to get the Label, Product, and Component tables to be dimensions tables so I can filter on them.

If I join the label table to the fact table with a cross-filter direction of "both", it works fine. Then I join the component table to the fact table with a cross filter direction of "both". After that, the visualizations break.

I have tried a few iterations with bridge tables, but it hasn't worked.
Any ideas on how to handle a model that has nonunique dimension tables?

 

Fact with non unique Dims.png

 

1 ACCEPTED SOLUTION
DataInsights
Super User
Super User

@Anonymous,

 

Try this solution.

 

Create a relationship between each dimension table and the fact table (crossfilter direction = single):

 

DataInsights_1-1671470063470.png

 

Measure:

 

Total Hours = 
CALCULATE (
    SUM ( FactTable[Hours] ),
    CROSSFILTER ( LabelTable[Ticket #], FactTable[Ticket #], BOTH ),
    CROSSFILTER ( ProductTable[Ticket #], FactTable[Ticket #], BOTH )
)

 

Create slicers using dimension tables, and add FactTable[Ticket #] to a visual:

 

DataInsights_2-1671470204688.png

You can use this pattern for additional dimension tables. In the measure, add a CROSSFILTER argument for each dimension table, enabling bidirectional crossfiltering in the measure.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!




View solution in original post

1 REPLY 1
DataInsights
Super User
Super User

@Anonymous,

 

Try this solution.

 

Create a relationship between each dimension table and the fact table (crossfilter direction = single):

 

DataInsights_1-1671470063470.png

 

Measure:

 

Total Hours = 
CALCULATE (
    SUM ( FactTable[Hours] ),
    CROSSFILTER ( LabelTable[Ticket #], FactTable[Ticket #], BOTH ),
    CROSSFILTER ( ProductTable[Ticket #], FactTable[Ticket #], BOTH )
)

 

Create slicers using dimension tables, and add FactTable[Ticket #] to a visual:

 

DataInsights_2-1671470204688.png

You can use this pattern for additional dimension tables. In the measure, add a CROSSFILTER argument for each dimension table, enabling bidirectional crossfiltering in the measure.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!




Helpful resources

Announcements
PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

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