Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Address Validator Transformation
  4. Aggregator Transformation
  5. Association Transformation
  6. Bad Record Exception Transformation
  7. Case Converter Transformation
  8. Classifier Transformation
  9. Cleanse transformation
  10. Comparison Transformation
  11. Custom Transformation
  12. Custom Transformation Functions
  13. Consolidation Transformation
  14. Data Masking Transformation
  15. Data Masking Examples
  16. Decision Transformation
  17. Duplicate Record Exception Transformation
  18. Dynamic Lookup Cache
  19. Expression Transformation
  20. External Procedure Transformation
  21. Filter Transformation
  22. HTTP Transformation
  23. Identity Resolution Transformation
  24. Java Transformation
  25. Java Transformation API Reference
  26. Java Expressions
  27. Java Transformation Example
  28. Joiner Transformation
  29. Key Generator Transformation
  30. Labeler Transformation
  31. Lookup Transformation
  32. Lookup Caches
  33. Match Transformation
  34. Match Transformations in Field Analysis
  35. Match Transformations in Identity Analysis
  36. Merge Transformation
  37. Normalizer Transformation
  38. Parser Transformation
  39. Rank Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. Source Qualifier Transformation
  44. SQL Transformation
  45. Using the SQL Transformation in a Mapping
  46. Stored Procedure Transformation
  47. Standardizer Transformation
  48. Transaction Control Transformation
  49. Union Transformation
  50. Unstructured Data Transformation
  51. Update Strategy Transformation
  52. Weighted Average Transformation
  53. XML Transformations

Transformation Guide

Transformation Guide

Cleanse transformation output fields

Cleanse transformation output fields

View the output fields on the
Output Fields
tab of the
Properties
panel. A Cleanse transformation creates output fields based on the fields that you map in the
Field Mapping
tab.
The
Output Fields
tab displays the name, type, precision, and scale for each output field.
The transformation creates output fields in the following manner:
Cleanse asset with a single output
The transformation creates the cleansed field.
The output field name is the name of the target field appended by the name of the Cleanse transformation. For example, if you have a target field
Person_name
and you entered the name for the Cleanse transformation as
Cleanse_TX
, the operation returns the output field name as
Person_name_Cleanse_TX
.
Cleanse asset with multiple outputs
The transformation creates the cleansed fields and additionally any merged output field that you or another user configured in the asset.
The transformation attempts to adds the suffix
_Cleansed
to the name of each target field. For example, if you have a target field
FirstName
, the operation returns the output field name as
FirstName_Cleansed
.
If you created the cleanse asset in the current version of
Data Quality
, the transformation applies the suffix
_Cleansed
to all output fields. If you created the asset in an older version of
Data Quality
, the transformation may apply a different naming policy to the outputs. See
Rules and guidelines for output field names
for more information.
The merged output field names are the names of the merged fields that you configured in the asset.
You cannot edit the output field properties in the Cleanse transformation. To edit the properties, open the cleanse asset in
Data Quality
.

Rules and guidelines for output field names

You may create a cleanse asset in
Data Quality
and add outputs to the asset over time. This can impact the type of suffix that the Cleanse transformation applies to the output fields.
When you use a cleanse asset with multiple outputs in a transformation, verify that the field names meet your mapping requirements. You may need to map the output fields again to ensure that the transformation defines the field names in the manner that you expect.
Consider the following rules and guidelines when you review the output field names:
  • Some older cleanse assets supported a single output field in a single cleanse instance. If you add outputs to such an asset and you do not update the original instance, the Cleanse transformation applies the
    _Cleansed
    suffix to the newer outputs only. The transformation does not apply any suffix to the output in the original instance.
    The Cleanse transformation applies this policy regardless of when you add the asset to the transformation. The transformation deletes a suffix from an older output field when you add an output in another instance and you do not change the original instance.
  • If you add an output to the original instance in any cleanse asset, the Cleanse transformation applies the
    _Cleansed
    suffix to all output names.
    The Cleanse transformation applies this policy regardless of the age of the asset and regardless of when you add the asset to the transformation.

0 COMMENTS

We’d like to hear from you!