Jitterbit · Transformations
Failed to convert XML file to JSON
Short answer
This Jitterbit transformation error means XML embedded in JSON contains a CDATA section, which is not supported. In a Jitterbit script, use Replace to swap the special characters inside the CDATA section, including the CDATA delimiters, for their escaped equivalents.
VerifiedLast verified
01Error text
Failed to convert XML file to JSON02Likely causes
- CDATA sections are not supported in XML embedded within JSON passed through a transformation.
03How to fix it
- In a Jitterbit script, use Replace to swap the special characters inside the CDATA section, including the CDATA delimiters, for their escaped equivalents.
- If targeting only the CDATA section is not feasible, replace the entire XML string that contains it.
04Official documentation
→Related errors
- String value length exceeds the maximum allowedThis Jitterbit transformation error means a single JSON string value exceeded the agent JSON parser limit of 20 MB. On a private agent running version 12.5 or later, set MaxStringLength in the [JsonParser] section of jitterbit.conf, for example 50000000 for 50 MB.
- expected String to be a ArrayThis Jitterbit error appears when special characters in connector-provided JSON schema names are replaced by underscores, so the endpoint receives names it does not expect. Confirm the affected activity uses a JSON schema with a root node named json.
- The node cannot be createdThis Jitterbit error means an imported transformation mapping with duplicate nodes is out of sync with the schema definition used at runtime. In the affected transformation, use Remove all mappings beneath this node on the root node.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries