Hardcoded date in a row filter
"Hardcoded date in a row filter" is one of the reliability checks Auditabi runs on a Power BI semantic model. n query(ies) filter rows with a literal date (#date(2024, …) or a date string). 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 boundary from Date.From(DateTime.LocalNow()) or a parameter (RangeStart/RangeEnd for incremental refresh).
What is detected
n query(ies) filter rows with a literal date (#date(2024, …) or a date string). The window never moves; the report silently stops receiving new data or keeps old data forever.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Derive the boundary from Date.From(DateTime.LocalNow()) or a parameter (RangeStart/RangeEnd for incremental refresh).
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.