SUMMARIZE used to add computed columns
"SUMMARIZE used to add computed columns" is one of the performance checks Auditabi runs on a Power BI semantic model. n expression(s) add expressions inside SUMMARIZE. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Group with SUMMARIZE and add the expressions with ADDCOLUMNS, or use SUMMARIZECOLUMNS.
What is detected
n expression(s) add expressions inside SUMMARIZE. That form evaluates in a context the engine cannot optimise and is a known source of wrong results with filters.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Group with SUMMARIZE and add the expressions with ADDCOLUMNS, or use SUMMARIZECOLUMNS.
Reference
SQLBI: All the secrets of SUMMARIZE
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