Here’s my $0.02. It’s good as syntax sugar for specific cases, but it’s basically a FILTER construct in Groucho glasses. And writing it out the long way let’s you add more than one matching condition. I use it, but if it disappeared tomorrow, I wouldn’t miss it.
Here’s an example from a recent forum response where I did a lookup with 3 matching conditions. If the solution required only one, I could have used LOOKUPVALUE as a substitute.
Rate Lookup =
VAR SelStaff = SELECTEDVALUE( Hours_Worked[Staff ID] )
VAR SelCat = SELECTEDVALUE( Hours_Worked[Category] )
VAR SelDate = SELECTEDVALUE( Hours_Worked[WeekEndingFriday] )
VAR FindRow =
ALL( Rate_Data ),
Rate_Data[Staff_ID] = SelStaff &&
Rate_Data[Category] = SelCat &&
Rate_Data[rate_activefrom] <= SelDate &&
Rate_Data[rate_expired_on] >= SelDate
VAR Result =
MAXX( FindRow, Rate_Data[Hourly Rate] )
I think of it a lot like 90% of the time intelligence functions - helpful shorthand conveniences, but basically unnecessary.