Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 116 of 212

104 C H A P T E R 6 | More analytics Figure 6-7: Viewing a calculated table in the model designer. Note Some interesting uses for calculated tables are described at and numbers/. Although these articles describe uses for calculated tables in Power BI, you can now use the same approach in tabular models. Bidirectional cross-filtering Another feature new to tabular models is bidirectional cross-filtering. This rather complex-sounding name allows cross-filtering across a table relationship in two directions rather than one direction, which has always been a feature in tabular models. This means that you no longer need to create complex DAX expressions to produce specific results, as long as you set your model to compatibility level 1200. To better understand the implications of this new feature, we'll start by reviewing one-directional cross-filtering. A one-directional cross-filter applies in a one-to-many relationship such as that between a dimension table and a fact table. Typically, the fact table contains a column with a relationship to a corresponding column in the dimension table. In a tabular model based on AdventureWorksDW, FactInternetSales (which you can rename as Internet Sales) has the ProductKey column, and you can use this column to define a relationship in a single direction from the DimProduct dimension table (renamed as Product) to the fact table. If you import these tables into the model at the same time, the foreign-key relationship defined in the tables is automatically detected and configured for you. Otherwise, you can manually create the relationship.

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016