Hardcoded years / static dates in DAX
"Hardcoded years / static dates in DAX" is one of the reliability checks Auditabi runs on a Power BI semantic model. A year, a date or a period is written as a literal inside a measure (Calendar[Year] = 2024, DATE(2025, 1, 1)). It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Use the date table and time-intelligence functions, or a parameter table selected by the user; never a literal year in a reusable measure.
What is detected
A year, a date or a period is written as a literal inside a measure (Calendar[Year] = 2024, DATE(2025, 1, 1)). The number silently stops meaning what it says after the year turns.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Use the date table and time-intelligence functions, or a parameter table selected by the user; never a literal year in a reusable measure.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.