renames the transformations in a mapplet when you use the mapplet in a Mapplet transformation. If you reference a transformation in the mapplet in a downstream transformation, be sure to use the updated name.
The mapplet that you use in the Mapplet transformation might contain transformations with names that conflict with the names of transformations in the mapping. To avoid name conflicts with transformations in the mapping,
Data Integration
prefixes the names of transformations in the mapplet with the Mapplet transformation name at run time.
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 the 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.
In most cases,
Data Integration
truncates transformation names that contain more than 80 characters.
Data Integration
doesn't truncate the names of Mapplet transformations that contain Hierarchy Builder, Hierarchy Parser, or Structure Parser transformations. When you use a Hierarchy Builder, Hierarchy Parser, or Structure Parser transformation in a mapplet, to prevent runtime errors, be sure that the combined Mapplet transformation name doesn't exceed 80 characters.
Data Integration
only renames transformations in mapplets when the mapplet is used in a mapping created after the April 2022 release.