I’m integrating with CargoWise (WiseCloud) using the Universal XML (UniversalShipment) structure, and I’m running into issues when trying to update fields on an existing Forwarding Shipment (S-JOB) through an HTTP+XML eAdaptor endpoint.

I have read the Universal XML documentation thoroughly, and I understand that to update fields inside an existing shipment, I should use:

However, CargoWise rejects or ignores my XML, and I cannot determine whether the issue is related to:

• wrong XML structure

• incorrect namespaces

• missing DataContext fields

• EnterpriseID / ServerID / Company mismatch

• AdditionalFieldsToUpdate Type paths

• EDI Sender/Recipient configuration

• or something else entirely

  My goal its to update an existing S-JOB, e.g. "TETSE 4000", and set one or more custom fields.

  Things I've already tried

  • Changing the root to without

  • Testing different versions (1.0, 1.1)

  • Explicit XML namespaces (both default and prefixed)

  • Using ForwardingShipment.FieldName vs ForwardingShipment.CustomFields.FieldName

  • Adding elements in different positions

  • Sending minimal XML vs extended XML

  • Verifying SenderID / RecipientID in CargoWise EDI Settings

  • Verifying Company / Enterprise / Server values

  • Testing via SOAP envelope as well as direct XML POST

  • Using both AdditionalFieldsToUpdate and standard Shipment fields

  • Testing inside CargoWise "Universal XML Viewer" import tool (same behavior)