Year written into a file path or a table name
"Year written into a file path or a table name" is one of the reliability checks Auditabi runs on a Power BI semantic model. n query(ies) embed a year in the source path or object name. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Parameterise the year, or point at a source that covers every period.
What is detected
n query(ies) embed a year in the source path or object name. The dataset stops picking up new data on 1 January and nobody notices until the numbers stop moving.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Parameterise the year, or point at a source that covers every period.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.