Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
The customer is experiencing an error indicating an unexpected difference between request and session data, which violates the Devices XML protocol, labeled as REQUEST_XML_TAMPERING, when Warehouse app task validation is used.
The customer is experiencing an error indicating an unexpected difference between request and session data, which violates the Devices XML protocol, labeled as REQUEST_XML_TAMPERING, when Warehouse app task validation is used.
Reason:
This arises when the task is being rerun without resetting the related data/orders, as the task is not guaranteed to be idempotent. This behavior is by design, leading to failures on consecutive runs if the work/action was already performed.
This arises when the task is being rerun without resetting the related data/orders, as the task is not guaranteed to be idempotent. This behavior is by design, leading to failures on consecutive runs if the work/action was already performed.
Resolution:
To resolve this, follow these steps:
1. Review the output XML of the last successful test step to determine where your test run left off.
2. Inspect your test to ensure that all required sales orders, transfer orders, work headers, and other records are still present and in the expected state.
3. Re-create or edit any missing or modified records. Alternatively, create a new test setup and design the test to use valid existing records.
4. For further details, refer to the Microsoft documentation on the Unexpected difference between request and session data during testing - Dynamics 365 Supply Chain Management | Microsoft Learn.
To resolve this, follow these steps:
1. Review the output XML of the last successful test step to determine where your test run left off.
2. Inspect your test to ensure that all required sales orders, transfer orders, work headers, and other records are still present and in the expected state.
3. Re-create or edit any missing or modified records. Alternatively, create a new test setup and design the test to use valid existing records.
4. For further details, refer to the Microsoft documentation on the Unexpected difference between request and session data during testing - Dynamics 365 Supply Chain Management | Microsoft Learn.