FILTER over a table comparing a measure
"FILTER over a table comparing a measure" is one of the performance checks Auditabi runs on a Power BI semantic model. n expression(s) filter a whole table with a condition that calls a measure. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Filter on the dimension instead, pre-aggregate with SUMMARIZE or a variable, or move the comparison outside the row context.
What is detected
n expression(s) filter a whole table with a condition that calls a measure. The measure is evaluated once per row of the table with a context transition each time, which is the classic cause of a visual that takes seconds to refresh.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Filter on the dimension instead, pre-aggregate with SUMMARIZE or a variable, or move the comparison outside the row context.
Reference
SQLBI: Filter arguments in CALCULATE
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