MC1532274 Low
Dynamics 365 Commerce -Failures for Store Commerce operations following recent WebView2 updates
Summary AI-generated
Store Commerce operations in Dynamics 365 may fail due to date formatting issues triggered by recent browser/runtime updates and historical time-zone-offset changes.
Suggested actions AI-generated
- Change affected device's time zone to UTC
- Validate workflow, timestamps, integrations
- Evaluate rollback with Microsoft Support if needed
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1526749 Finance and operations apps - Information about the 2026 time zone changes in Canada
- MC1526697 Dynamics 365 apps and Dataverse – Information about the 2026 time zone changes in Canada
- MC1526712 Power Platform – Information about the 2026 time zone changes in Canada
- MC1530376 Finance and operations apps - Information about a recent update to the Store Commerce app on iOS
- MC1473356 Dynamics 365 Commerce - Improve order capture workflows in Store Commerce
- MC1526468 Update to MC1510951: Canada 2026 time zone changes — Microsoft 365 impact and required admin actions
Original post from Microsoft
We are investigating reports of failures in Dynamics 365 Commerce Store Commerce operations following recent browser or runtime updates. Affected operations may fail with an error indicating that a date value cannot be converted to Edm.DateTimeOffset.
How does this affect me?
Reports include failures when updating cart lines and creating customers. Other operations that process affected date values may also result in failures. Our initial investigation indicates that changes in historical time-zone-offset handling can interact with Store Commerce’s date formatting, causing certain requests to contain date values that Commerce Scale Unit cannot accept.
What action do I need to take?
If you are impacted by this issue, please review the available mitigation options listed below:
How does this affect me?
Reports include failures when updating cart lines and creating customers. Other operations that process affected date values may also result in failures. Our initial investigation indicates that changes in historical time-zone-offset handling can interact with Store Commerce’s date formatting, causing certain requests to contain date values that Commerce Scale Unit cannot accept.
What action do I need to take?
If you are impacted by this issue, please review the available mitigation options listed below:
- UTC time zone: Please change impacted device’s time zone to UTC to avoid the failures. Validate the affected workflow and the impact on local-time displays, timestamps, scheduled activities, and integrations before broader deployment. Please ensure that you are changing the time zone and not the system clock.
- Temporary version rollback: A rollback to an exact, previously working version may be evaluated with Microsoft Support. For the Windows app, this concerns the WebView2 Runtime; for web-based POS, it concerns the Edge or Chrome browser. These require different procedures. Rolling back Edge alone does not roll back WebView2.