---
schema_version: "1"
id: aa6a925a06a790e54f3cbc83ead36f3690987ef5036349aeb0ac3025aa75d855
title: Use Salesforce Object as Target Object
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dpe_salesforce_object_as_wb_datacloud.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dpe_salesforce_object_as_wb_datacloud.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7824781254e6320ec28a068ddcc78b34e7704d944e0afa4a16d57b3cdb83a978
description: Configure Salesforce objects as target writeback objects in the Data 360 runtime
products:
  - Cross Cloud
release: "264"
---
# Use Salesforce Object as Target Object

Configure Salesforce objects as target writeback objects in the Data 360 runtime

### 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;"><a href="https://help.salesforce.com/s/articleView?id=ind.dpe_editions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported editions and availability for Data Processing Engine (DPE).">View supported editions</a>.</td></tr></tbody></table>

On home orgs, you can write back to objects that are present in home orgs and connected companion orgs. Whereas in companion orgs, you can only write back to objects that are available in the companion org.

1. In the Configuration section, select **Salesforce Object** as the target type for the source node.
    
    ![Writeback object configuration section in Data 360 runtime with Salesforce object selected as the target type.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-data_processing_engine-264-0-0-production-enus/80e06924-e6c0-4b82-81cf-e99ccd77d857/data_processing_engine/images/dpe_datacloud_salesforce_obj_wb.png)
2. In the Action Type dropdown, select one of the following action types:
    
    Select **Insert** to add records to the target object with the data that you want to write back. To insert, map the mandatory fields from the target object to a field from the source node.
    
    Select **Update** to update records of the target object with the data that you want to write back. To update, map the mandatory fields in the target object to a field from the source node.
    
    Select **Upsert** to update or add records to the target object with the data that you want to write back. Use a Salesforce ID or an external ID to ensure the system can accurately match and either update existing records or insert new ones based on the value in that field.
    
    Select **Delete** to delete existing records in the org.
3. In **Target Object**, select the object that you want to write the data back to or delete records from.
4. In **User with Writeback Permission**, add a user who has permissions to create target object records. Only users with the System Administrator permission can be selected as writeback users.
5. In **Writeback Sequence**, specify a whole number to indicate the processing order for the writeback object node when the definition is run.
6. Select **Update changed records only** to update or upsert data for only those records that have changed. If a definition is run multiple times, the option updates only the records that changed after the last run.
7. In the Field Mapping section, map source node fields with target object fields. The field mappings determine the values to be added to the new or updated target object records. To delete records from the target object, map the source node field and the target object field that uniquely identify the records that you want to delete.
    
    If you're upserting records, select the
    
    **ID Field**
    
    checkbox next to the mapping to use a Salesforce ID or external ID. This allows the system to accurately match and either update existing records or insert new ones based on the value in that field.
    
    To simplify field mapping process, use Einstein generative AI to generate field mapping suggestions.
8. In the Related Field Mapping section, specify the relationship name, the parent object, and the target field of the related object.
    
    Use related field mapping to map related fields to populate the lookup or master-detail field of an object when there’s no corresponding Salesforce ID for that record. The relationship name works like a pseudo-field to get information about the related object. Also, use related field mapping to insert, update, or upsert records.
    
    For target objects with master-detail field or mandatory lookup fields, use related field mapping to populate the target fields of the parent object. Use the Move field to related field mapping and Move field to field mapping switch buttons to move fields across the Field Mapping and Related Field Mapping sections. Also use related field mapping to populate multiple lookup fields with different matching criteria for the same parent object.
9. To manage row locks for related records during writeback, turn on the **Related Record Writeback Setting** and select the **Group By** field. To know about row lock, see [Manage Row Locks with Related Record Writeback](https://help.salesforce.com/s/articleView?id=ind.dpe_configure_rowlock.htm&language=en_US).
10. Save your node configuration.

- **[Manage Row Locks with Related Record Writeback](https://help.salesforce.com/s/articleView?id=ind.dpe_configure_rowlock.htm&release=264.0.0&type=5)**  
    Use Related Record Writeback in Data Processing Engine (DPE) to reduce row lock errors when writing large volumes of child records. This feature is only applicable for definitions having Data 360 runtime.

#### See Also

- [Map Related Fields by Using Einstein](https://help.salesforce.com/s/articleView?id=ind.dpe_map_related_fields_using_einstein.htm&release=264.0.0&type=5 "Use Einstein generative AI to simplify the tedious task of manually mapping fields when you configure a writeback node.")