Forum Discussion
Understanding the differences between two time-intelligence expressions relative to Visual
It needs a date context. You can see the total is blank too.
You should be able to supply a context by wrapping your calculate in another one, simulating the outer filter context that you get in a visual
Calculate(
Your calculate
, treatas( {max(dates[date])}, date[date])
)
So my intution was correct, its the lack of date context supplied by the Card that causes the issue.
My understanding was that it is generally bad form to nest Calculates within Calculates?
My intution is that the biggest drawback to sticking with my original measure as compared to the DAX pattern based measure is likely performance, more than anything?
- Deku1 year agoSuper User
Nothing wrong with nesting calculate, won't affect performance.
The built in date intelligence functions are syntax sugar, you can achieve more versatililty and same performance with a custom one