Relationship key built from a hardcoded year
"Relationship key built from a hardcoded year" is one of the reliability checks Auditabi runs on a Power BI semantic model. n calculated column(s) used as relationship keys are built with a literal year (DATE(2026, …)). It is a critical finding: it breaks refresh, returns wrong numbers or exposes data, so it should be fixed before publishing. Derive the year from the source data (a Year column, the file, or a parameter) instead of a literal.
What is detected
n calculated column(s) used as relationship keys are built with a literal year (DATE(2026, …)). Every row maps to that year; when the data moves on, the whole table stops joining and its measures go blank.
Why it matters
Breaks refresh, returns wrong numbers, or exposes data. Fix before publishing.
How to fix it
Derive the year from the source data (a Year column, the file, or a parameter) instead of a literal.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.