Time intelligence anchored on a fact date column
"Time intelligence anchored on a fact date column" is one of the reliability checks Auditabi runs on a Power BI semantic model. n expression(s) pass a fact-table date column to a time-intelligence function. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Pass the date column of the marked date table, and let the relationship filter the fact.
What is detected
n expression(s) pass a fact-table date column to a time-intelligence function. Those functions need a contiguous date table; on a fact column they silently skip the days with no transaction, so a period with a gap returns the wrong comparison.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Pass the date column of the marked date table, and let the relationship filter the fact.
Reference
SQLBI: Time intelligence in DAX
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