Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Where to Assign Parameters
  6. Mapping Outputs
  7. Generate a Mapping from an SQL Query
  8. Dynamic Mappings
  9. How to Develop and Run a Dynamic Mapping
  10. Dynamic Mapping Use Cases
  11. Mapping Administration
  12. Export to PowerCenter
  13. Import From PowerCenter
  14. Performance Tuning
  15. Pushdown Optimization
  16. Partitioned Mappings
  17. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Overriding Parameters Using the Parameter Hierarchy

Overriding Parameters Using the Parameter Hierarchy

When you create a parameter for a transformation, a logical data object, a mapplet, or a mapping, you can override the parameter by specifying a new parameter for the transformation, logical data object, mapplet, or mapping at a higher level in the parameter hierarchy.
For example, you create a parameter in a transformation. Then you add the transformation to a mapplet. You can either use the default parameter value from the transformation or you can create a mapplet parameter to override the transformation parameter value.
You can also override parameters using a parameter set or a parameter file. The parameters in the mapping use the parameters specified in the parameter set or parameter file. In a parameter set or a parameter file, you can specify only workflow and mapping parameters.

0 COMMENTS

We’d like to hear from you!