Forum Discussion
Major Problem with DAX Time Intelligence Functions such as TOTALYTD etc.
Dear All,
One major problem I see in the TOTALYTD function is that, this function does not allow variable for <year-end-date> parameter. It should be no paramater to default to "12/31" or any harcoded string like "31/10", "06/30" etc. And I believe it defaults to 365 days in a year which could not be changed.
So this function does not work when the fiscal year end dates are different for different fiscal years and the number of days are also slightly different in different fiscal years, for example some fiscal years may have 366 days, some 370 days, some 365 days etc. Also a fiscal year could have 12 or 13 periods etc. & fiscal periods are not Jan, Feb, Mar.. Dec etc. Ideally TOTALYTD function must not have any <year-end-date> parameter or default to anything. All it needs is the measure for which YTD to be computed and the company's Fiscal Calendar to find out all the time related information, that's it. My current BI tool which is a relatively new and little-known tool, works fantastic! In DAX I need to write my own YTD script. Painful.
Will there be a fix from Microsoft in near future?
Thank you.
2 Replies
maitydd64 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/434008I also have this video that demonstrates the superiority of No CALCULATE over DAX TI functions and CALCULATE approaches. And, the approach is easy to modify for fiscal years, especially if you use offsets.
Could you please fix - or, rather, remove - your "signature" so it doesn't take 70% of the message's space?
The forum engine and formatting is already bad enough and does not use screen space efficiently; bloated spammish signatures only make it worse.
