Calculated column aggregating its own table
"Calculated column aggregating its own table" is one of the performance checks Auditabi runs on a Power BI semantic model. n calculated column(s) aggregate the table they belong to without CALCULATE. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Use a measure, or wrap the aggregation in CALCULATE when a per-row total really is intended.
What is detected
n calculated column(s) aggregate the table they belong to without CALCULATE. The aggregation ignores the row context and returns the same grand total on every row — and it is computed at refresh for every row.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Use a measure, or wrap the aggregation in CALCULATE when a per-row total really is intended.
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