Forum Discussion
DATESYTD problem in PB Onpremises (Remote Server)
Good Afternoon,
I am making a duplicate copy version of a certain dashboard in PB Onpremises (Remote Server). It was originally made in the previous PB Desktop version.
My use of DATESYTD in a measure in the previous PB Desktop version gave no problems, but in the new version the measure(s) using DATESYTD does not give the required Running Total result:
Hi F_Reh
Your DAX is almost correct - the issue is not the function itself, it’s how the year-end parameter is being interpreted in newer versions of Microsoft Power BI.
Change it to:
Attendances FYTD = CALCULATE( Daily_Attendances[Total_Attendances], DATESYTD(DatesTable[Date], "03/31") )If it still misbehaves, then your issue is one of these (common in Report Server setups):
Your DatesTable is not marked as a Date Table
Relationship between DatesTable[Date] and fact table is broken/inactive
Daily_Attendances[Total_Attendances] is not a proper measure (should be SUM-based)
7 Replies
Hi F_Reh , Could you share which version exactly ? also can you try whether the small change in the format is helping you to fix the error:
instead of this
Attendances FYTD = CALCULATE(Daily_Attendances[Total_Attendances],DATESYTD(DatesTable[Date],"31/3"))
use
Attendances FYTD = CALCULATE(Daily_Attendances[Total_Attendances],DATESYTD(DatesTable[Date],"3/31"))
I recreated the scenario with some sample data both the measures are working for me .
Data model :
Sample data :
Op:
File :
Rag status.pbix
Thanks
If you found this helpful, please consider giving it a kudo and marking it as the accepted solution — it goes a long way in helping others facing the same issue.
For more Power BI tips and discussions, let’s connect on LinkedIn:
https://www.linkedin.com/in/natarajan-manivasagan
Cheers!Unfortunately the Running Total is still not being calculated in spite of making the suggested change....The Onsite (Remote Server) version is 2.150.1926.0 64-bit (January 2026)
1) Desktop Version top rows looks like this (Descending) where the running totals look fine:
2) The Onsite (Remote Server) Version top rows looks like this (Descending). I have modified the measure to use "3/31":
Kind Regards
Hi F_Reh , In the solution I shared, I created the measure, but the screenshot appears to show values derived from a calculated column.
Thanks
It is indeed a calculated column with Running Totals....It worked fine in the old Power BI Desktop version...The exact application of DATEYTD is inexplicably failing in the onpremises remote server version !
Hi F_Reh
Thank you for reaching out to the Microsoft Fabric Forum Community.
Natarajan_M Thanks for the inputs.
I hope the information provided by user was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hi F_Reh
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.
Hi F_Reh
Your DAX is almost correct - the issue is not the function itself, it’s how the year-end parameter is being interpreted in newer versions of Microsoft Power BI.
Change it to:
Attendances FYTD = CALCULATE( Daily_Attendances[Total_Attendances], DATESYTD(DatesTable[Date], "03/31") )If it still misbehaves, then your issue is one of these (common in Report Server setups):
Your DatesTable is not marked as a Date Table
Relationship between DatesTable[Date] and fact table is broken/inactive
Daily_Attendances[Total_Attendances] is not a proper measure (should be SUM-based)
