--- schema_version: "1" id: cc273c6167df7bae91bf7133c061a2c139e3093f98b2910a6f75c68566b7fd62 title: Use Data Lake Object (DLO) and Data Model Object (DMO) 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_datalake_obj_as_wb.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.dpe_datalake_obj_as_wb.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a0702d82f6dd55a474c91d29d1891a75d99bf1d1df37b6142d74e76a70fb1b2d description: In the Data 360 runtime, you can writeback transformed results to new DLOs and DMOs or existing ones. products: - Cross Cloud release: "264" --- # Use Data Lake Object (DLO) and Data Model Object (DMO) as Target Object In the Data 360 runtime, you can writeback transformed results to new DLOs and DMOs or existing ones. ### Required Editions
View supported editions.
On home orgs, you can writeback to existing or new DLOs and DMOs in home orgs and connected companion orgs. In contrast, companion orgs support writeback only to DLOs and DMOs within that companion org. Review these considerations when selecting the DMO category during writeback. - DMO category selection applies only to DMOs, not DLOs. - You can select a DMO category only when creating a DMO. You can’t change the category for an existing DMO. - The selected DMO category must align with the process type selected when creating the Data Processing Engine (DPE) definition. - You can’t create a DMO with a name that already exists under a different category. - For the Engagement category, mapping an Event Time field is required. The event time field must be of type Date or DateTime. Review these considerations when selecting the operation (action) type during writeback: - For the upsert and overwrite action types, existing DMOs require mapping for both the primary Key and qualifier key. For the insert action type, only primary key mapping is required. - DLOs require mapping only for primary key. Steps to write back to a DLO or DMO: 1. In the Writeback object configuration, select the source node, then for the Target Type, select **Data Lake Object**, or **Data Model Object**. ![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 The Target Type object options vary based on what Data 360 object type you chose when first creating your definition. For example, when creating your definition, if you selected data model object, you'll see Data Model Object as a Target Type option in the configuration, but not Data Lake Object. 2. In the Action Type dropdown, select one of these action types: - **Insert**: Add new records to the target object by mapping required target fields to source node fields. - **Upsert**: Update existing records or insert new records by using a Salesforce ID or external ID for matching. - **Overwrite**: Replace target data according to the overwrite behavior for the selected target object. ![Writeback action types](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/data_processing_engine_writeback_action_type.png) 3. Select whether you want to write back to an existing DLO or DMO, or create an object: - Use an existing object: select **Use existing Data Lake Object**, or **Use existing Data Model Object** checkbox, then search and select the object name. - Create an object: Deselect **Use existing Data Lake Object** or **Use existing Data Model Object** checkbox, then enter a name for the new object. 4. If you’re writing to a DMO, select **Data Model Object Category** based on the segmentation required. ![DMO categories](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/data_processing_engine_writeback_category.png) 5. 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. To simplify the field mapping process, use Einstein generative AI to generate field mapping suggestions. 6. In the Primary Key Mapping section, enter or select a value to serve as the unique identifier for records. If you're writing back to a data model object, to avoid potential identical key value errors, select a qualifier key. 7. Save your node configuration. #### 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.")