---
schema_version: "1"
id: deaebe44f16deb66ea552e511b3dcb90280165554b63b0daa935ae0843959578
title: Write the Batch Data Transform Results to a Data Lake Object Output Node
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_output_node_dlo.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_batch_transform_output_node_dlo.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c1e001b8ec9999c15429fcea4437c960ee6d09c475942259eafb48df5f8e429b
description: To use your batch data transform as input to identity resolution, calculated insights, or segmentation, you write the results to a new or existing data lake object (DLO) in an output node. The object that holds the output is called a target data lake object. You can’t save a batch data transform without an output node.
products:
  - Data 360
release: "264"
---
# Write the Batch Data Transform Results to a Data Lake Object Output Node

To use your batch data transform as input to identity resolution, calculated insights, or segmentation, you write the results to a new or existing data lake object (DLO) in an output node. The object that holds the output is called a target data lake object. You can’t save a batch data transform without an output node.

1. At the end of your batch data transform, click the Add Node button (![Branch Recipe icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/resources-global/analytics/images/bi_button_add_node.png)) and select **Output**.
    - To use an existing DLO, select **Use Existing**. Select the object to write the results to, and then click **Apply**.
    - To create a new DLO, select **Create New**.
        
        ![Modal of output node characteristics showing Create New DLO selected](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/c360_a_batch_transform_output_write_2025-12-02.png)
2. For the output Write Mode, select either **Replace** or **Upsert**.
    - Replace mode:
        
        - Loads all input data in every run.
        - Merges input data into the output by replacing all columns in the record during the upsert operation.
        - Requires all columns in the output object to be mapped.
        - Doesn't allow carrying over values from the existing record.
    - Upsert mode:
        
        - Replace attempts incremental transforms, loading only changes from previous runs into the output.
        - Allows unmapped columns in the output object.
        - When the transform runs, unmapped columns will contain null values.
3. Choose which data lake object fields to map to the batch data transform’s fields. You can only map fields that have the same data type. Fields that share the same name are automatically selected.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)
    
    Note You can't map the system fields, Data Source and Data Source Object. If you edit a transform that has these fields manually mapped, remove them from the output node and save your changes.
    
    1. When you map transform results to an output node, the transform’s currency (ex. USD, INR, GBP) is written to the output’s currency field. The currency field can't be used as a primary key.

#### See Also

- [_Salesforce Help_: Data Objects in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_objects.htm&release=264.0.0&type=5 "When working with Data 360, it’s helpful to know about Data 360 data objects including data lake objects (DLO) and data model objects (DMO).")