Relationship built on a calculated column
"Relationship built on a calculated column" is one of the performance checks Auditabi runs on a Power BI semantic model. n relationship(s) join on a calculated column. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Create the key in Power Query or in the source so the relationship is built on a stored column.
What is detected
n relationship(s) join on a calculated column. The column is computed at refresh after the data loads, the relationship is rebuilt each time, and any dependency in the expression slows the refresh further.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Create the key in Power Query or in the source so the relationship is built on a stored column.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.