Jitterbit · Transformation mapping import
The node cannot be created
Short answer
This 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.
VerifiedLast verified
01Error text
The node: <node name> cannot be created.02Likely causes
- A mapping file that added duplicate nodes to the target schema did not apply that change to the schema definition used at runtime, so the two went out of sync.
03How to fix it
- In the affected transformation, use Remove all mappings beneath this node on the root node.
- Import the mapping file again to resync the runtime schema definition.
- If the error persists, reconfigure the activity that provides the schema, then refresh the schema in the transformation.
04Official documentation
→Related errors
- Failed to convert XML file to JSONThis 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.
- 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.
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