Microsoft Office Tutorials and References
In Depth Information
Filter Context with Multiple Tables
Now that you have seen how to use row context with related tables, you might find it
interesting to note that table relationships directly affect the filter context of involved
tables, regardless of DAX expressions used. For example, you can add a Cities table to
the model like the one in Figure 6-20, which has a relationship as a lookup table with the
Orders table through the City column (see Figure 6-21).
FIguRE 6-20 The Cities table contains Country and Continent columns.
FIguRE 6-21 The relationship between the Orders and Cities tables.
When you browse the data by using a PivotTable, you can choose Continent and Channel
as the slicers, DiscountedAmount as a measure, and Color and Size in Rows and Columns,
respectively.
In Figure 6-22, you can see the data of all the rows in the Orders table partitioned by Color
and Size attributes. Despite the presence of Continent and Channel as slicers, there is no filter
active on these slicers because all the members are selected. Keep in mind that the Continent
Slicer also contains an empty member that corresponds to all the sales made in the Internet
Channel that do not have a corresponding City. (See Figure 6-18 to look at raw data.)
Search JabSto ::




Custom Search