DHL Shipping Quotes fail for Domestic Shipments when Content Mode is "Non Documents"

[gwharton]

Preconditions (*)

1. Magento 2.2-develop or 2.3-develop

Steps to reproduce (*)

1. Setup DHL module to obtain quotes via XML
2. Setup store as ship from address SW1 1AA, GB
3. Set DHL Content Type to Non Documents
4. Attempt to obtain shipping quote for destination SW1 1AA, GB

Expected result (*)

1. A quote is obtained

Actual result (*)

1. No quote is obtained.

Investigation shows that the request to DHL is stating that the shipment is dutiable, even though the shipment is domestic. This causes DHL to reply with an error. This seems to be due to this change. 410027d#diff-de9bd572b851dd842e021c8421062177

[magento-engcom-team]

Hi @gwharton. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@gwharton do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[gwharton]

PR #19487 @ PR #19488 fixes ready.

[magento-engcom-team]

Hi @engcom-backlog-tomash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-backlog-tomash Thank you for verifying the issue.

Unfortunately, not enough information was provided to created internal ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@engcom-backlog-tomash Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97515, MAGETWO-97516 were created

[magento-engcom-team]

Hi @gwharton. Thank you for your report.
The issue has been fixed in #19487 by @gwharton in 2.3-develop branch
Related commit(s):

• 77a5cd1a51e376d4f02bc23dcfdee0c61f08c6a7
• ff9282dca5b76a1df543c4ab8a001def4b9e9e0c
• d9ac0d6d188f0e6fe2d7fac9845db51a34630d2f

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @gwharton. Thank you for your report.
The issue has been fixed in #19488 by @gwharton in 2.2-develop branch
Related commit(s):

• e6b279b815b80065fdb7a70ed0fea16d26960425
• ce7b5602466b47777cfa9de1cec31fa9f02ac644
• 49e26db2a7ab099258cdd9307ad572f5b8075333
• a497c95712e1682904d62b80525efd3bce380fef
• 5557b9d06c169fbd8b38f7c598e51c8c49e94739

The fix will be available with the upcoming 2.2.9 release.