Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Merging data

Updated on May 17, 2024

Combine data from the primary and secondary paths into a single track to merge an incomplete record with a data record that comes from the secondary data source. After you merge data from two paths, the output records keeps only the unique data from both paths. The Merge shape outputs one or multiple records for every incoming data record depending on the number of records that match the merge condition.

  1. In a data flow, click the Plus icon on a shape, and select Merge.
  2. Double-click the secondary Source shape and configure it.
    Note: When you select a data set, it must be a data set that you can browse by keys, for example, Database Table, Decision Data Store, Event Store, HBase, or Interaction History data set.
  3. Click Submit.
  4. Double-click the Merge shape to configure it.
  5. In the Name field, enter a name for the shape.
  6. Click Add condition and select a property that needs to match between two sources. You can add more than one condition. For example, When .CustomerID is equal to .ID.
  7. Optional: Select the Exclude source component results that do not match merge option when there is no data match. If one of the specified properties does not exist, the value of the other property is not included in the class that stores the merge results.
  8. Select which source takes precedence when there are properties with the same name but different values.
    • Primary path - The merge action takes the value in the primary source.
    • Secondary path - The merge action takes the value in the secondary source.
  9. Click Submit.
For example: You can merge a data record that contains Customer ID with banking transactions of this customer. When there are five banking transactions for a single customer, the Merge shape outputs five records for one incoming data record that contains Customer ID. Each of the five records contains the Customer ID and details of a single banking transaction.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us