DATESBETWEEN with literal boundaries
"DATESBETWEEN with literal boundaries" is one of the reliability checks Auditabi runs on a Power BI semantic model. n expression(s) bound DATESBETWEEN with literal dates. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Derive the boundaries from the filter context (MIN and MAX of the date column) or from a parameter table.
What is detected
n expression(s) bound DATESBETWEEN with literal dates. The window stops moving with the calendar, so the measure quietly becomes wrong after the boundary date passes.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Derive the boundaries from the filter context (MIN and MAX of the date column) or from a parameter table.
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