The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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.