Transformations > Verifier transformation > Verifier transformation configuration
  

Verifier transformation configuration

When you configure a Verifier transformation in a mapping, you first select the verifier asset that contains the address data to include in the mapping. Next, you configure the incoming fields and the field mappings. Then, you verify the output fields.
To configure the transformation, complete the following tasks:
    1Connect the Verifier transformation to a Source transformation or other upstream object.
    2On the Verifier tab, select the verifier that you want to include in the transformation.
    The following image shows the options that you use to select the verifier:
    The image shows the Verifier tab of the transformation. The verifier tab includes the verifier field, which identifies the name and location of the asset that you select.
    3On the Incoming Fields tab, configure the incoming fields.
    By default, the transformation inherits all incoming fields from any connected upstream object in the mapping. You can define a field rule to limit or rename the incoming fields.
    4On the Field Mapping tab, configure the options to connect the data from incoming fields to the target fields on the verifier asset.
    The verifier inputs might already reflect the names of the input fields in the data. If so, you can use the Automap options to connect the fields.
    For more information about connecting to upstream object fields, see Verifier transformation field mappings.
    5Verify the verifier output fields on the Output Fields tab.
    6You can optionally rename the Verifier transformation and add a description on the General tab. You can also update the tracing level for the transformation on the Advanced tab. The default tracing level is Normal.
Note: If you update an asset in Data Quality after you add it to a transformation, you may need to synchronize the asset version in the transformation with the latest version. For more information about data quality asset synchronization, see Synchronizing data quality assets.