PL-300 · 2.1.5 · Model the data
Calculated columns and tables
Identify use cases for calculated columns and calculated tables
and tables store results in the model and recalculate during refresh.
Stored DAX becomes model structure
A evaluates once per row during model refresh and stores the result. A evaluates a DAX table expression during refresh and stores the returned rows.
Choose column, table, or measure
| Need | Use |
|---|---|
| Value for every row | |
| New reusable table structure | |
| Result that changes with report filters |
Columns can be used in , , grouping, and because they become model fields. Calculated tables can participate in relationships like other model tables.
Understand the cost
Stored columns and tables increase model size and refresh work. are calculated at query time and do not store one result per row.
Use stored calculations when the result must become part of the model structure, not merely because DAX can express it.
Exam clue: filterable or relational stored output = column/table; filter-responsive result = measure.
Key points
- : one stored value per row
- : expression returns a table
- Stored results: increase model size
- Use cases: filtering, , or reusable model structure
Click an underlined term for a one-line explanation, or see them all in the glossary .
Exam trap
at query time; and tables store their results in the model.
Sources · 2 Microsoft Learn pages Show ▾
Checked on October 4, 2026. Report a problem
Go deeper on Microsoft Learn
Checked against Microsoft Learn on October 4, 2026. Report a problem with this card