The parse assets that you create are available to the users who create mappings in
Data Integration
. You or other users add a Parse transformation to a mapping and add a parse asset to the transformation. The Parse transformation applies the logic in the parse asset to an input data field that you specify.
A Parse transformation works in a similar way to a Mapplet transformation. A
Data Integration
user connects the transformation inputs and outputs to other objects in the mapping in the same manner as a mapplet connects to other mapping objects. When the
Data Integration
user runs the mapping, the Parse transformation applies the parse asset logic to the input field and generates output fields that you can connect to a downstream transformation.
After the mapping runs, you can evaluate the data output to determine if the data meets the parsing objectives.
Rules and guidelines for parse assets and mappings
Consider the following rules and guidelines when you work with mappings and parse assets:
A Parse transformation contains a single parse asset. You configure the transformation to perform parsing operations on a single field of input data. You select the field on the
Field Mappings
tab in the transformation.
When you run a mapping that includes a Parse transformation, the mapping creates the output fields that the parse asset specifies.
When the parse asset specifies a regular expression or a dictionary, the Parse transformation creates an output field for the results of each step. The transformation also creates a field for unparsed data and one or more fields for overflow data.
When the parse asset specifies pattern-based parsing, the Parse transformation creates multiple output fields for name data, including discrete fields for first names, family names, and full names. The transformation can also create fields for overflow data and for unparsed data.
ASK INFAPreview
