Write back transformed data to standard and custom objects, data lake objects (DLO),
data model objects (DMO), JSON, or Analytics datasets. Use the writeback object node to create,
update, or upsert records with the transformed data. You can also delete records from the org
using the writeback object node. Use related field mapping to write data to multiple objects in
a definition.
Required Editions
Every Data Processing Engine definition must have at least one writeback object node. You can
add up to twenty writeback object nodes in your definitions. A writeback object node can write
back transformed data from only one source node.
Based on the runtime, you can choose to write back to a Salesforce object, a JSON, an
analytics dataset, data lake object, or data model object.
You can also write back transformed data to virtual objects that store records in an external
system instead of in your Salesforce org. Data Processing Engine supports writeback only to
Apache HBase-backed virtual objects for CRM Analytics and Data 360 runtime
definitions. Use the object's external ID field in the writeback object node's field mapping
to match records for upsert. Make sure that you have the required object and field-level
security (FLS) permissions and access for the virtual object before you write back to it.