Calculated column with a context transition
"Calculated column with a context transition" is one of the performance checks Auditabi runs on a Power BI semantic model. n calculated column(s) wrap an aggregation in CALCULATE. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Compute the value upstream in Power Query, or expose it as a measure if it does not need to be a column.
What is detected
n calculated column(s) wrap an aggregation in CALCULATE. Each row triggers a context transition at refresh time, which is the slowest way to compute a column.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Compute the value upstream in Power Query, or expose it as a measure if it does not need to be a column.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.
More DAX checks
- Arithmetic or comparison on a measure that returns text
- Measure returning text in one branch and a number in another
- Share denominator clears a fact-table column instead of the dimension
- "Previous period" window overlaps the current one
- Percentage label built without ×100
- Percentages and amounts summed together