Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register 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 April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 43 | |
| 37 | |
| 34 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 65 | |
| 64 | |
| 31 | |
| 26 | |
| 25 |