Lesson 04 of 7 · Relationships
One side filters. Many side listens.
The model has 53 relationships, and every one of them is one-to-many. That single choice decides where a slicer's filter goes.
1
The 1 and the *
The model has 53 relationships, and every one is one-to-many: one row in a dimension matches many rows in a fact. In Model view that's the 1 at the dimension end of the line and the * at the fact end.
The direction matters. A filter travels from the one side to the many side. Pick a commodity in the dimension and every fact table joined to it narrows down. It doesn't travel back the other way.
A slicer uses DimCommodity[Commodity]. Which tables does it filter?
Answer the question above to unlock this.
Where does the slicer come from?
Slicer
DCommodity
–Release checks no relationship
FTrade
FPrices
Trade tonnes 0Price rows showing 3
A toy model with illustrative values. Try the second slicer source with a commodity selected.
2
Check yourself
0 / 3
Two fact tables both record a country. Where should the country slicer come from?
A line has 1 at the DimDate end and * at the fact end. Which way does filtering flow?
Why is single direction the safer default?
The ruleSlice from dimensions. Keep relationships one-to-many and single-direction, unless you can name the reason for an exception.