Hello Folks !
Just wanted to share something I fixed recently with Incoming Customer Order in IFS Cloud 25R1. We have been using the SalesMessageService API to create Incoming Customer orders for some time now. We recently updated to 25R1 and noticed that the incoming customer order API broke.
Overview
If you’ve recently upgraded or considering upgrading to IFS Cloud 25R1 and use the SalesMessageService API for creating Incoming Customer Orders, this update may affect you. A field change in the order‐lines payload is causing deserialization errors.
The Error You’ll See
{
"error": {
"code": "ODP_DESERIALIZATION_ERROR",
"message": "Error while de-serializing contents.",
"details": [
{
"message": "Tree should be empty but still has content left: WantedDeliveryDate"
},
{
"code": "UNKNOWN_CONTENT",
"message": "'WantedDeliveryDate' can not be mapped as a property or an annotation."
}
]
}
}
What Changed
| Element | Before (Pre-25R1) | After (25R1) |
| At ExtCustOrdLines level | "WantedDeliveryDate": "YYYY-MM-DD" | "WantedDeliveryDateTime": "YYYY-MM-DDThh:mm:ssZ" |
| At OrdersStruct header level | remains "WantedDeliveryDate" | remains unchanged |
The change is only for the order lines, not the header.
Impact
- Payloads using the old field (WantedDeliveryDate) in line items will fail with deserialization errors.
- Integrations built prior to 25R1 need adjustments.
- If not caught, this can disrupt automated order creation, cause delays.
What You Should Do
- Update your payloads: replace WantedDeliveryDate (line level) with WantedDeliveryDateTime using ISO-8601 datetime format.
- Review any sample templates or auto-generated code you maintain; make sure they reflect the new structure.
- Test thoroughly end-to-end, including all order lines, before deploying in production.
- Monitor logs for errors like “Tree should be empty … WantedDeliveryDate” or “UNKNOWN_CONTENT”.
Takeaways
- Even small schema changes (field name/type) can break integrated services.
- Always check the API contract / schema when upgrading major versions.
- Document changes in your internal integration spec so everyone (development, QA, ops) knows what to expect.
Additional Context
- IFS Cloud 25R1 was released end of May 2025.
I hope this helps other consultants and developers avoid headaches when moving to 25R1. Reach out to me if you need further information.
— Ram