Mapping Recurring Nodes

Mapping rules for recurring nodes can:
  • Determine the output for all occurrences
  • Determine the output for specific occurrences
  • Reconcile cardinality issues, such as different minimum occurrences or source and destination schemas that model recurring structures with different levels or no recurrence.

How you map recurring nodes is determined by the recurring relationships in your source and destination schemas, as outlined in the following table.

Source Destination Action to take
Not recurring Recurring Expand the destination node to map the source nodes to specific destination node occurrences.
Recurring Not recurring Select specific occurrences of the source and map them to the destination.
Matching Recurring Levels Matching Recurring Levels Map all occurrences or select/expand specific occurrences if you need to.
More Recurring Levels Fewer Recurring Levels Select specific occurrences of the source nodes and map them to specific occurrences of the destination. See the discussion on mapping limitations for recurring nodes in the Getting Started Guide for more information.
Fewer Recurring Levels More Recurring Levels Expand specific occurrences of the additional recurring levels of the destination nodes and map the source levels within the expanded destination nodes.