---
schema_version: "1"
id: df2508f896e1cc24d30c152b0a28e7112759b9a776b42e5e2d3f99dadc4c3d61
title: Writeback Objects
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dpe_writeback.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dpe_writeback.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 01e9d135bdf245321adc3926fda4d600ad49a07fab4a20bf33586d860690597a
description: 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.
products:
  - Cross Cloud
release: "264"
---
# Writeback Objects

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

<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>

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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-data_processing_engine-264-0-0-production-enus/80e06924-e6c0-4b82-81cf-e99ccd77d857/images/icon_note.png)

Note You can write back results to Salesforce Shield encrypted fields.

#### See Also

- [_SOQL and SOSL Reference_: Understanding Relationship Names](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_relationships_understanding.htm)
- [Enable Sharing Inheritance](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_sharing_getting_started.htm&type=5&language=en_US)