Fact table declared on the "one" side of a relationship
"Fact table declared on the "one" side of a relationship" is one of the modeling checks Auditabi runs on a Power BI semantic model. n relationship(s) put the fact table on the one side and the dimension on the many side. It is a critical finding: it breaks refresh, returns wrong numbers or exposes data, so it should be fixed before publishing. Recreate the relationship with the dimension on the one side (its key must be unique) and the fact on the many side.
What is detected
n relationship(s) put the fact table on the one side and the dimension on the many side. Filters flow from the fact to the dimension only: a slicer on the dimension does not filter the fact, and totals silently ignore it.
Why it matters
Breaks refresh, returns wrong numbers, or exposes data. Fix before publishing.
How to fix it
Recreate the relationship with the dimension on the one side (its key must be unique) and the fact on the many side.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.