This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowJuly 28 - August 9 | Final Round of the Power BI Dataviz World Championships. This is your chance. Learn more
Hi everyone, so I have this measure that calculates overdue jobs. I wanted to optimize it as when I have filter dates (year & months), it throws an error. Thanks in advance 🙂
Overdue Jobs =
VAR MaxDateInCurrentContext =
CALCULATE ( MAX ( 'Date'[Date] ), ALL ( 'Date'[Date] ) )
VAR MinDateInDateTable =
CALCULATE ( MIN ( 'Date'[Date] ), ALL ( 'Date' ) )
RETURN
CALCULATE (
COUNTROWS ( 'Jobs' ),
FILTER (
ALLEXCEPT (
'Jobs',
'Jobs'[Jobs Job ID],
Jobs[Jobs Job Client Name],
Jobs[Jobs Job Name],
Jobs[Jobs Job State]
),
[Jobs Job Start Date] >= MinDateInDateTable
&& [Jobs Job Start Date] <= MaxDateInCurrentContext
&& (
[Jobs Job Completed Date] > MaxDateInCurrentContext
|| [Jobs Job Completed Date] = BLANK ()
)
&& ( [Jobs Job Due Date] < MaxDateInCurrentContext )
),
USERELATIONSHIP ( 'Date'[Date], Jobs[Jobs Job Start Date] ),
USERELATIONSHIP ( 'Unique Staff'[StaffID], Jobs[Job Manager ID] )
)
Change USERELATIONSHIP to TREATAS
Rewrite the FILTER part - it doesn't have to be that complicated inside a CALCULATE
Rearrange the filters in order of cardinality impact
In general you will want to install DAX Studio and then check the query plan that is generated by the measure. That will help you to identify which part needs tuning.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
If you love stickers, then you will definitely want to check out our community sticker challenge, Barcelona edition!
Check out the July 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 25 | |
| 23 | |
| 19 | |
| 17 | |
| 14 |
| User | Count |
|---|---|
| 24 | |
| 23 | |
| 20 | |
| 20 | |
| 19 |