VALUES used as a scalar without a single-value guard
"VALUES used as a scalar without a single-value guard" is one of the reliability checks Auditabi runs on a Power BI semantic model. n measure(s) use VALUES where a scalar is expected without checking HASONEVALUE or using SELECTEDVALUE. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Use SELECTEDVALUE(column) — optionally with an alternate result — or guard with IF(HASONEVALUE(column), …).
What is detected
n measure(s) use VALUES where a scalar is expected without checking HASONEVALUE or using SELECTEDVALUE. The measure works while one value is selected and raises an error as soon as the visual groups by something coarser, including the total row.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Use SELECTEDVALUE(column) — optionally with an alternate result — or guard with IF(HASONEVALUE(column), …).
Reference
SQLBI: SELECTEDVALUE vs VALUES
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