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
Hello,
@Applicable88 , You are returning a table from filter. just like measure column can only have one value per row.
So calculation should be done assuming each row operation happens. here you are returning a table for each row
example
if( 'Calendar' [Date]>minx(relatedtable('Maintable') , 'Maintable'[BookingDate]) && 'Calendar[Day]= "Monday",1,0)
assuming Maintable is joined with calendar
@amitchandak I understand what you mean. But I'm referring to the Filter function, which you can see in the measure and also in the calculated column. In the measure 'Calendar'[Date] only works with MAX('Calendar'[Date]) whereas in the calculated column in works with a naked column like 'Calendar'[Date]>= 'Booking'[Date]
I assume you have row by row also in the measure through Filter(), so why cannot write 'Calendar'[Date]<= 'Calendar'[Date] instead? Don't we have row context here ? Why we need to aggregate? It's a virtual table within the measure in my understanding, same as filter() in a calculated column.
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!
| User | Count |
|---|---|
| 9 | |
| 9 | |
| 8 | |
| 6 | |
| 6 |
| User | Count |
|---|---|
| 20 | |
| 18 | |
| 16 | |
| 14 | |
| 14 |