DAXDAX QualityLow
Comparison with BLANK() instead of ISBLANK
"Comparison with BLANK() instead of ISBLANK" is one of the dax quality checks Auditabi runs on a Power BI semantic model. n expression(s) compare a value to BLANK() with = or <>. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Use ISBLANK(value) or NOT ISBLANK(value).
What is detected
n expression(s) compare a value to BLANK() with = or <>. In DAX BLANK() = 0 and BLANK() = "" are TRUE, so the test does not do what it reads.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Use ISBLANK(value) or NOT ISBLANK(value).
Reference
Tabular Editor BPA: Use ISBLANK instead of = BLANK()
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