Time intelligence without a marked date table
"Time intelligence without a marked date table" is one of the reliability checks Auditabi runs on a Power BI semantic model. Time-intelligence functions are used in n expression(s), but no table is marked as a date table (dataCategory: Time). It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Mark the calendar table as a date table (Table tools → Mark as date table) and use its date column in every time-intelligence call.
What is detected
Time-intelligence functions are used in n expression(s), but no table is marked as a date table (dataCategory: Time). Results are only correct when the date column is contiguous and unique, and Power BI cannot guarantee it.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Mark the calendar table as a date table (Table tools → Mark as date table) and use its date column in every time-intelligence call.
Reference
Microsoft: Set and use date tables in Power BI Desktop
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