FILTER(table, …) used as a CALCULATE filter argument
"FILTER(table, …) used as a CALCULATE filter argument" is one of the performance checks Auditabi runs on a Power BI semantic model. n expression(s) pass FILTER over a whole table to CALCULATE. 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 a column: CALCULATE([m], Table[Col] = value) or KEEPFILTERS(Table[Col] = value).
What is detected
n expression(s) pass FILTER over a whole table to CALCULATE. The engine materialises the table instead of applying a fast column predicate.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Filter on a column: CALCULATE([m], Table[Col] = value) or KEEPFILTERS(Table[Col] = value). Use FILTER only when the predicate needs a measure.
Reference
Tabular Editor BPA: Filter column values with proper syntax
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