Forum Discussion
Power BI service error - Date time format
Hi,
I get below error relating to date format issue in power BI service. However it works fine in desktop.
I have tried all the recommended solutions such as - using locale to transform to date, checking language peference in browser, microsoft 365, clearing cache etc. But nothing worked. Can any of you please help?
Error
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"We couldn't parse the input provided as a DateTimeZone value."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10032"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"6/30/2025"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} Table: Labour Requirements.
Hi KM06 ,
Thanks for reaching out to the Microsoft fabric community forum.
GilbertQ ,
Thank you for your prompt response.
In addition to GilbertQ , input, I have added more troubleshooting steps that may help resolve the issue, along with links to previously solved threads with similar issues.
To fix the DateTimeZone parsing error in Power BI Service, start by updating your Power Query transformations to explicitly convert date strings using ISO format like 2025-06-30T00:00:00Z via DateTimeZone.FromText, which eliminates locale ambiguity. Ensure the machine running your on-premises gateway has its regional settings aligned to your expected date format for example, set it to English (United Kingdom) or English (India) via Control Panel → Region → Formats, and restart the gateway after changing. Also, update your gateway to the latest version from Microsoft's official site to avoid known parsing bugs, and consider disabling HTTPS mode in the gateway config tool if issues persist. As a diagnostic aid, wrap your transformation in a try...otherwise clause to catch problematic rows and pinpoint inconsistencies. To confirm the fix, test a dummy table with hardcoded ISO-format dates and verify that it refreshes correctly in the service. This will isolate whether your source data or environment setup is causing the issue.
We truly appreciate your continued engagement and thank you for being an active and valued member of the community.
If you're still experiencing any challenges, please don’t hesitate to reach out we’d be more than happy to assist you further.
We look forward to hearing from you.
Best regards,
Lakshmi
5 Replies
v-lgarikapatCommunity Support
Hi KM06 ,
Thanks for reaching out to the Microsoft fabric community forum.
GilbertQ ,
Thank you for your prompt response.
In addition to GilbertQ , input, I have added more troubleshooting steps that may help resolve the issue, along with links to previously solved threads with similar issues.
To fix the DateTimeZone parsing error in Power BI Service, start by updating your Power Query transformations to explicitly convert date strings using ISO format like 2025-06-30T00:00:00Z via DateTimeZone.FromText, which eliminates locale ambiguity. Ensure the machine running your on-premises gateway has its regional settings aligned to your expected date format for example, set it to English (United Kingdom) or English (India) via Control Panel → Region → Formats, and restart the gateway after changing. Also, update your gateway to the latest version from Microsoft's official site to avoid known parsing bugs, and consider disabling HTTPS mode in the gateway config tool if issues persist. As a diagnostic aid, wrap your transformation in a try...otherwise clause to catch problematic rows and pinpoint inconsistencies. To confirm the fix, test a dummy table with hardcoded ISO-format dates and verify that it refreshes correctly in the service. This will isolate whether your source data or environment setup is causing the issue.
We truly appreciate your continued engagement and thank you for being an active and valued member of the community.
If you're still experiencing any challenges, please don’t hesitate to reach out we’d be more than happy to assist you further.
We look forward to hearing from you.
Best regards,
Lakshmi- v-lgarikapat
Hi KM06 ,
I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.
Thank you for being an active part of the community. Looking forward to hearing from you!
Best regards,
Lakshmi- v-lgarikapat
Hi KM06 ,
We haven’t heard back from you regarding our last response, so I just wanted to check in to see if you were able to resolve the issue. If you have any further questions or need assistance, please feel free to let us know.
Best Regards,
Lakshmi
