Hello everyone,
We recently migrated to IFS Cloud 25R2 (SU6) and noticed a change in the format of the "ActualShipDate" field in the Dispatch Advice messages (DESADV) we send.
Before migration:
"ActualShipDate": "2026-07-17T16:04:55" (local timestamp, no timezone indicator)
Since the migration to 25R2:
"ActualShipDate": "2026-07-20T10:29:20Z" (UTC timestamp, with "Z" suffix)
This is causing issues on the receiving side, which expects the previous format without the UTC indicator.
Has anyone else run into this on Dispatch Advice (DESADV), or on other outbound messages? Is this an intentional/documented change, and if so, is there a way to keep the previous format?
For reference, we have also opened an official support case on this topic: CS0542209.
Thanks in advance for any insight!
Soumia