|
Component |
edoc NAV archivelink |
|---|---|
|
Version |
4.0.0 - 4.5.0 |
|
Created on |
|
|
Last modified on |
An error occurredFailed to render Workflows Metadata macro on page 2166063199 during export. If this problem continues, please contact our Customer Support Team for assistance. |
|
Review status |
An error occurredFailed to render Workflows Metadata macro on page 2166063199 during export. If this problem continues, please contact our Customer Support Team for assistance. |
|
KB article number |
1705705686 |
Summary
When archiving or importing data from Microsoft Dynamics Navision (NAV), errors may occur if fields contain special characters such as the less-than sign (<) or greater-than (>) contain special characters. These characters compromise the XML structure and mean that the response from Microsoft Dynamics NAV cannot be processed as expected.
The error message "The response does not correspond to the expected XML structure." is displayed.
This article deals with the causes of the error and what you can do to prevent it from occurring and reduce the consequences of the error.
Background information about the error
-
Microsoft Dynamics NAV versions without automatic XML encoding/decoding do not support special characters in XML-relevant fields.
-
In fields (e.g. table or page captions, vendor names) that are queried by edoc archive service from Microsoft Dynamics NAV, special characters such as less-than (angle bracket open) and greater-than (angle bracket close) are entered.
-
In some cases, captions are missing, which means that standard texts with special characters are adopted.
Important requirements
-
You have software development permissions in Microsoft Dynamics NAV (only for the import/export routine).
-
You are using edoc NAV archivelink in conjunction with edoc archive service minimum version 25.5.1 (only for the function to ignore the process).
-
You have activated versioning for the relevant processes in edoc archive service (only for the function to ignore the process).
Solution
Depending on the situation you find yourself in, the following solutions are possible:
-
Prevention: You can take preventive measures by checking your texts for special characters when entering data and avoiding them. You can also maintain captions in all relevant languages to prevent standard texts containing special characters.
-
After the error occurs: The transactional data has already been written to archiving operations in the process table of edoc NAV archivelink. You then have the following options:
-
You can develop an export/import routine to clean up the data.
-
You can create a new version of the process after the error has been corrected and then ignore the incorrect version.
-