You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using DHL's services, but we have encountered a problem with the pickup (proxy) request.
The problem seems to be related to the XML request that is being generated by the Karrio system. When we attempt to send a pickup request to DHL using the generated XML, we receive an error response from DHL stating that the XML is incorrect or contains invalid properties.
I have taken the time to investigate the issue further, and I have identified that the problem lies within the XML request being generated. After some debugging, I tried manually creating an XML request with fixed properties, and to my surprise, it worked perfectly fine. This leads me to believe that there might be an issue with the way Karrio service is generating the XML for the pickup request. (we're using same DTO from karrio api docs)
Here is an example of the XML request generated by the Karrio server: (copied from dashboard logs)
note: x characters is not the real values, it just masked
And here is the error response we receive from DHL:
<?xml version="1.0" encoding="UTF-8"?>
<res:ErrorResponsexmlns:res='http://www.dhl.com/'xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'xsi:schemaLocation= 'http://www.dhl.com/ err-res.xsd'>
<Response>
<ServiceHeader>
<MessageTime>2023-08-01T11:38:37.830+00:00</MessageTime>
<MessageReference>xxxxxxxxxxxxxxxx</MessageReference>
<SiteID>xxxxxxxxxxx</SiteID>
</ServiceHeader>
<Status>
<ActionStatus>Error</ActionStatus>
<Condition>
<ConditionCode>111</ConditionCode>
<ConditionData>Error in parsing request XML:Error: The content of element type "Requestor" is
incomplete, it must match
"(AccountType,AccountNumber,RequestorContact,CompanyName?,Address1,Address2?,Address3?,City,CountryCode,DivisionName?,PostalCode?)".
at line 23, column 18</ConditionData>
</Condition>
</Status>
</Response>
</res:ErrorResponse>
And here is manual XML request generation based on DHL document(fix version)
I have compared the above XML with the manually created one that works, and I noticed some discrepancies, particularly in the properties and formatting.
Could you kindly review the provided XML request and let us know if you see any issues with it? It's possible that we may be missing certain elements, or there might be some data formatting problems. Any guidance or insight you can provide will be highly appreciated.
If you require any further information or additional code snippets, please don't hesitate to ask. We are eager to resolve this matter promptly to ensure our DHL integration functions flawlessly once again.
Thank you for your attention to this matter. We look forward to your assistance in resolving this issue.
OS: Debian
Karrio Version: 2023.5 & 2023.5.1 same result
The text was updated successfully, but these errors were encountered:
MrWorld
changed the title
[]
[DHL-Conflict] Pickup xml request issue
Aug 8, 2023
We have been using DHL's services, but we have encountered a problem with the pickup (proxy) request.
The problem seems to be related to the XML request that is being generated by the Karrio system. When we attempt to send a pickup request to DHL using the generated XML, we receive an error response from DHL stating that the XML is incorrect or contains invalid properties.
I have taken the time to investigate the issue further, and I have identified that the problem lies within the XML request being generated. After some debugging, I tried manually creating an XML request with fixed properties, and to my surprise, it worked perfectly fine. This leads me to believe that there might be an issue with the way Karrio service is generating the XML for the pickup request. (we're using same DTO from karrio api docs)
Here is an example of the XML request generated by the Karrio server: (copied from dashboard logs)
note: x characters is not the real values, it just masked
And here is the error response we receive from DHL:
And here is manual XML request generation based on DHL document(fix version)
And here is the DHL XML official example (dhl xml portal documents):
I have compared the above XML with the manually created one that works, and I noticed some discrepancies, particularly in the properties and formatting.
Could you kindly review the provided XML request and let us know if you see any issues with it? It's possible that we may be missing certain elements, or there might be some data formatting problems. Any guidance or insight you can provide will be highly appreciated.
If you require any further information or additional code snippets, please don't hesitate to ask. We are eager to resolve this matter promptly to ensure our DHL integration functions flawlessly once again.
Thank you for your attention to this matter. We look forward to your assistance in resolving this issue.
The text was updated successfully, but these errors were encountered: