Long hardcoded exclusion list in a row filter
"Long hardcoded exclusion list in a row filter" is one of the maintainability checks Auditabi runs on a Power BI semantic model. n query(ies) filter rows with five or more literal `<>` conditions in one step. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Maintain the exclusions in a reference table (an "Out of scope" list) and anti-join on it, so the business owns the list.
What is detected
n query(ies) filter rows with five or more literal `<>` conditions in one step. The business rule (entities out of scope) lives in code nobody reviews and drifts from the reference table.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Maintain the exclusions in a reference table (an "Out of scope" list) and anti-join on it, so the business owns the list.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.