Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register 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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
9 | |
9 | |
8 | |
8 |
User | Count |
---|---|
14 | |
12 | |
11 | |
11 | |
8 |