Table of Contents

Search

  1. Preface
  2. Components
  3. API collections
  4. Business services
  5. File listeners
  6. Fixed-width file formats
  7. Hierarchical schemas
  8. Intelligent structure models
  9. Refining intelligent structure models
  10. Mapplets
  11. Saved queries
  12. Shared sequences
  13. User-defined functions

Components

Components

Transformation names

Transformation names

When you use a mapplet in a Mapplet transformation,
Data Integration
renames the transformations in the mapplet at run time.
When you use a mapplet in a Mapplet transformation, the mapplet might contain transformations with names that conflict with other transformation names in the mapping. To avoid name conflicts,
Data Integration
prefixes the names of the transformations in the mapplet with the Mapplet transformation name.
For example, a mapplet contains an Expression transformation named Expression_1. You create a mapping and use the mapplet in the Mapplet transformation Mapplet_Tx_1. When you run the mapping, the Expression transformation is renamed to Mapplet_Tx_1_Expression_1.
If a mapplet contains another Mapplet transformation,
Data Integration
also prefixes the transformation names with the second Mapplet transformation name. For example, the mapplet in the previous example also contains a Mapplet transformation named MappletTx, which contains FilterTx_1. In the mapping, FilterTx_1 is renamed to Mapplet_Tx_1_MappletTx_FilterTx_1.
Data Integration
truncates transformation names that contain more than 80 characters.
Data Integration
only renames transformations in mapplets when the mapplet is used in a mapping created after the April 2022 release.

0 COMMENTS

We’d like to hear from you!