TREATAS used where a relationship exists
"TREATAS used where a relationship exists" is one of the performance checks Auditabi runs on a Power BI semantic model. n measure(s) transfer a filter with TREATAS between two tables that are already related. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Rely on the relationship, and keep TREATAS for virtual relationships that cannot exist in the model.
What is detected
n measure(s) transfer a filter with TREATAS between two tables that are already related. The relationship does the same work in the storage engine.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Rely on the relationship, and keep TREATAS for virtual relationships that cannot exist in the model.
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