Forum Discussion
Resolver IBug Report: DATESINPERIOD Function – Leap Year Handling
Thanks, Greg,
your links are always relevant.
"Unfortunately," I share your opinion about the TI functions, but at the same time, I hope they will be improved and cleaned of their bugs over time.A workaround was to propose a month-year selector instead of the date field. This way, you don’t have any issues. I’m reporting the measure for completeness.
var _ultimodelmese =
CALCULATE(
MAX('Data'[data]),
ALLEXCEPT('Data', 'Data'[anno], 'Data'[mese_anno])
)
RETURN
CALCULATE(
[Amount],
DATESINPERIOD(
'Data'[data],
_ultimodelmese,
-1,
YEAR
)
)
Community ChampionMattiar Yeah, in general, stay away from the DAX TI functions IMHO. You may find this helpful - https://community.powerbi.com/t5/Community-Blog/To-bleep-With-Time-Intelligence/ba-p/1260000
Also, see if my Time Intelligence the Hard Way provides a different way of accomplishing what you are going for.
https://community.powerbi.com/t5/Quick-Measures-Gallery/Time-Intelligence-quot-The-Hard-Way-quot-TITHW/m-p/434008
Resolver IThanks, Greg,
your links are always relevant.
"Unfortunately," I share your opinion about the TI functions, but at the same time, I hope they will be improved and cleaned of their bugs over time.
- Mattiar
A workaround was to propose a month-year selector instead of the date field. This way, you don’t have any issues. I’m reporting the measure for completeness.
var _ultimodelmese =
CALCULATE(
MAX('Data'[data]),
ALLEXCEPT('Data', 'Data'[anno], 'Data'[mese_anno])
)
RETURN
CALCULATE(
[Amount],
DATESINPERIOD(
'Data'[data],
_ultimodelmese,
-1,
YEAR
)
)