Calculated column with an iterator or CALCULATE
"Calculated column with an iterator or CALCULATE" is one of the performance checks Auditabi runs on a Power BI semantic model. n calculated column(s) run SUMX / FILTER / CALCULATE per row. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Move the logic to Power Query (merge / group) or to a measure evaluated at query time.
What is detected
n calculated column(s) run SUMX / FILTER / CALCULATE per row. On a fact table this multiplies refresh time and the column is not compressed as well as a source column.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Move the logic to Power Query (merge / group) or to a measure evaluated at query time.
Reference
Tabular Editor BPA: Avoid calculated columns with iterators
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