ISFILTERED used where HASONEVALUE is meant
"ISFILTERED used where HASONEVALUE is meant" is one of the dax quality checks Auditabi runs on a Power BI semantic model. n measure(s) branch on ISFILTERED before reading a single value. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Use HASONEVALUE (or SELECTEDVALUE with an alternate result) when the branch needs exactly one value.
What is detected
n measure(s) branch on ISFILTERED before reading a single value. ISFILTERED is true even when several values are selected, so the branch that assumes one value can still be reached.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Use HASONEVALUE (or SELECTEDVALUE with an alternate result) when the branch needs exactly one value.
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