LOOKUPVALUE where a relationship exists
"LOOKUPVALUE where a relationship exists" is one of the performance checks Auditabi runs on a Power BI semantic model. n calculated column(s) or measure(s) use LOOKUPVALUE between two tables that are already related. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Use RELATED when the relationship exists and points the right way.
What is detected
n calculated column(s) or measure(s) use LOOKUPVALUE between two tables that are already related. RELATED follows the relationship and is evaluated by the storage engine; LOOKUPVALUE re-scans the target table for every row.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Use RELATED when the relationship exists and points the right way.
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