You are here:
Use Salesforce Object as Target Object
Configure Salesforce objects as target writeback objects in the Data 360 runtime
Required Editions
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.
- In the Configuration section, select Salesforce Object as the target type for the source node.
-
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.
- In Target Object, select the object that you want to write the data back to or delete records from.
- 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.
- In Writeback Sequence, specify a whole number to indicate the processing order for the writeback object node when the definition is run.
- 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.
-
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. -
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.
- 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.
- Save your node configuration.
- Manage Row Locks with Related Record Writeback
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.
