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

Define Targets Based on the Mapping Flow

Define Targets Based on the Mapping Flow

When you define columns by mapping flow, target columns are determined by upstream transformations. When an upstream transformation changes the port order and metadata, the Write transformation picks up the changes.
You can retain keys when you create or replace the target if the key columns in the upstream transformation match the key column names in the target.
The following image shows how the Write transformation appears when you define target columns based on mapping flow:
When you configure dynamic ports in a Write transformation, the Developer tool groups them into a single All Ports node.
To avoid unexpected results, do not configure a run-time link to a Write transformation that defines targets based on the mapping flow.
Configure this functionality on the
Ports
tab of the Write transformation for flat file and relational targets.

0 COMMENTS

We’d like to hear from you!