TODAY() / NOW() / USERNAME() in a calculated column
"TODAY() / NOW() / USERNAME() in a calculated column" is one of the reliability checks Auditabi runs on a Power BI semantic model. n calculated column(s) use a volatile function. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Anchor the logic to the latest date in the fact table, or move it to a measure evaluated at query time.
What is detected
n calculated column(s) use a volatile function. The value is frozen at refresh time, so "today" is really "last refresh" and the column drifts silently.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Anchor the logic to the latest date in the fact table, or move it to a measure evaluated at query time.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.
More DAX checks
- Arithmetic or comparison on a measure that returns text
- Measure returning text in one branch and a number in another
- Share denominator clears a fact-table column instead of the dimension
- "Previous period" window overlaps the current one
- Percentage label built without ×100
- Percentages and amounts summed together