---
schema_version: "1"
id: 77f62c6629bf32df231d266743d9bce167c482eea2521621b2abf66c8d99a921
title: Merge Records with Multi-Definition Transforms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_batch_transform_multidefinition_merge.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_multidefinition_merge.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d65c7a3c2f0341622945dd3442bbd9c8b290bfe0fe1f5d29a27204af57badcdb
description: A transform definition specifies the sequence of operations applied to the data during a batch data transform. Definitions appear as nodes in the data flow canvas. You can combine multiple definitions to produce a single, unified output.
products:
  - Data 360
release: "264"
---
# Merge Records with Multi-Definition Transforms

A transform definition specifies the sequence of operations applied to the data during a batch data transform. Definitions appear as nodes in the data flow canvas. You can combine multiple definitions to produce a single, unified output.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d202463e67">User Permission Sets
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permission Sets Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d202463e67 ">To create batch data transforms</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d202463e67 ">
            <p>Permission set: </p>
            <ul>
              <li>Data Cloud Architect</li>

            </ul>
          </td>

        </tr>
      </tbody>
    </table>

A transform must have at least one definition, but it can support up to five. When writing to an output object, Upsert (or "merge") Mode processes only new and updated records. This feature optimizes resource usage and limits unnecessary reprocessing. Upsert Mode is typically used with multi-definition transforms.

Consider these limitations when using multi-definition transforms:

- If you have multiple transform definitions for a single transform, only one definition can be scheduled to run at a time, but a flow can trigger any of the definitions to run.
- Definitions within a single transform can write to the same output object. Different transforms can’t write to the same output object. For example, when multiple definitions belong to the same transform, a single definition can write to the same output object.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_example.png)

Example You can use multi-definitions and Upsert Mode to isolate a particular definition to fix errors in the output of a transform. This entails a corrected transform definition that writes to the same output object in Upsert Mode.