Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
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.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!