Transformation mapping consists of target fields or nodes and their corresponding scripts. These scripts may contain references to source fields or nodes or to project components, use functions, or contain other valid script logic. A mapping does not include target fields that are not mapped.
These pages are included in this topic:
Automapping is used to automatically map source and target fields whose names are an exact match within identical data structures. You can perform automapping using the entire data structure or within selected source and target nodes.
- Conditional Mapping
Creating a condition on a target node, referred to as conditional mapping, lets you specify if a source record being processed should be output to the target based on a defined condition. The condition determines (yes or no) if the record is mapped.
- Mapping Source Objects
In addition to automapping, source fields can be manually mapped to a target field. When you map a source field to a target field, the reference path of the source object is inserted into a script on the target field.
- Mapping Variables
When you map a variable, the variable reference is inserted into a script on the target field. Variable references are constructed with a dollar sign (
$) preceding the variable name.
- Mapping Custom Values
Custom values are simply hard-coded values that can be mapped to a target field.
- Mapping with Scripts
All transformation mappings are made up of scripts on individual nodes and fields within a target schema. This page covers how to open transformation scripts and reference project components and functions within them, although any valid script logic can be used.
- Transformation Mapping Exports and Imports
After you have completed a transformation mapping, you can export the mapping for reference, to share outside the project, or to reuse later. The mapping consists of all target fields or nodes and their corresponding scripts. Mappings that have been exported can be imported into a transformation, with the ability to select whether existing mappings will be overridden.
- Transformation Mapping Validity
Transformation mappings must be valid for a transformation to be valid. This page covers how to identify invalid mappings and view the validation errors associated with them, as well as how to resolve validation errors.
- XML Schema Advanced Types
When using a schema that contains derived types or substitution groups, some input from the user is required before you can proceed with the transformation mapping.
Last updated: Jun 25, 2019
- No labels