Create a calculated table
Applies to: SQL Server Analysis Services Azure Analysis Services Fabric/Power BI Premium
A calculated table is a computed object, based on either a DAX query or expression, derived from all or part of other tables in the same model.
A common design problem that calculated tables can solve is surfacing a role-playing dimension in a specific context so that you can expose it as a query structure in client applications. You might recall that a role-playing dimension is simply a table surfaced in multiple contexts -- a classic example is the Date table, manifested as OrderDate, ShipDate, or DueDate, depending on the foreign key relationship. By creating a calculated table for ShipDate explicitly, you get a standalone table that is available for queries, as fully operable as any other table. Another use includes configuring a filtered rowset, a subset, or superset of columns from other existing tables. This allows you to keep the original table intact while creating variations of that table to support specific scenarios.
Using calculated tables to best advantage will require that you know at least some DAX. As you work with expressions for your table, it might help to know that a calculated table contains a single partition with a DAXSource, where the expression is a DAX expression.
There is one CalculatedTableColumn for each column returned by the expression, where the SourceColumn is the name of the column returned (similar to DataColumns on non-calculated tables).
At least one table must already exist before you can create a calculated table. If you are creating a calculated table as a standalone computed table object, you can first create a table by importing from a file data source (csv, xls, xml). The file you import from can have a single column and single value. You can then hide that table.
How to create a calculated table
First, verify the tabular model has a compatibility level of 1200 or higher. You can check the Compatibility Level property on the model in SSDT.
Switch to the Data View. You can't create a calculated table in Diagram View.
Select Table > New calculated table.
Type or paste a DAX expression (see below for some ideas).
Name the table.
Create relationships to other tables in the model. See Create a Relationship Between Two Tables if you need help with this step.
Reference the table in calculations or expressions in your model or use Analyze in Excel for ad hoc data exploration.
Replicate a role-playing dimension
In the Formula bar, enter a DAX formula that gets a copy of another table. After the calculated table is populated, give it a descriptive name and then set up a relationship that uses the foreign key specific to the role. For example, in the Adventure Works database, you might create a calculated table for Due Date and use the DueDateKey as the basis of a relationship to the fact table.
=DimDate
Summarized or filtered
In the Formula bar, enter a DAX expression that filters, summarizes, or otherwise manipulates a model to contain the rows you want. This example groups by sales by color and currency.
=SUMMARIZECOLUMNS(DimProduct[Color]
, DimCurrency[CurrencyName]
, "Sales" , SUM(FactInternetSales[SalesAmount])
)
Superset using columns from multiple tables
In the Formula bar, enter a DAX expression that combines columns from multiple tables. In this case, query output lists product category for each currency.
=CROSSJOIN(DimProductCategory, DimCurrency)
See also
Compatibility level
Data Analysis Expressions (DAX) in Analysis Services
Understanding DAX in tabular models
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for