Review the rules and guidelines for configuring a mapping.
I made a lot of changes to source field metadata that I want to revert. I tried the Synchronize icon, but nothing's happening. What's going on?
Synchronization does not restore field metadata that was updated in a Source transformation. You can manually update the field metadata. Or, you can start over: Clear and select source object or create a new Source transformation.
A field name conflict error message displays in a transformation. In the transformation, I created a field rule that renamed the incoming fields, but the error continues.
A field name conflict can continue throughout a mapping after the initial problem. Locate the transformation with the first field name conflict error message and rename the fields before they enter the transformation.
A mapping failed because the number of fields in the compiled mapping exceeded the threshold. What should I do?
Mappings can have up to 7,000,000 input and output fields. When a mapping includes the Hierarchy Processor transformation, the mapping is more likely to reach this limit because of the complex data involved. The more joins, child fields, nested fields, and flattened arrays that the Hierarchy Processor transformation contains, the more likely the mapping will exceed the field limit.
If the mapping exceeds the limit, the following message appears in the mapping compilation log:
[LDTM_0502] The mapping [<mapping name>] failed because the number of fields in the compiled mapping exceeds the threshold: [7,000,000]. Number of fields: [<actual number>]. Create multiple mappings to process the data incrementally.
To resolve the error, create multiple mappings to process the complex data incrementally, and reduce the size of the mapping.
The Source transformation returns a JSON parsing error, even though my JSON file is good. What should I do?
When you select a JSON file in the source object, you receive the following error:
error [The file or partition directory [<path>/<JSON file>] is not valid. The parser encountere the following error while parsing the content: [Unexpected character 1 at 1]. Select a valid [Json] file or partition director.]
The error occurs when there is an array of primitives without a field name in the JSON file. For example, the following array causes a parsing error: [10,20,30,40,50,0]
The Source transformation parses the following array successfully: {"numbers":[10,20,30,40,50,0]}
As a workaround, wrap the top-level array in a struct element before reading the file in the Source transformation.