Add one or more writeback object nodes to your Data Processing Engine definition to write back the transformed results from your data source. Configure your writeback object node to select the appropriate target object based on the runtime where you plan to run your definition.
Required Editions
Make sure to add at least one writeback object node in every Data Processing Engine definition.
- In the node canvas, click New Node.
- Select Writeback Object as the node type.
-
Enter a name for your writeback object node.
The API name automatically populates from the name. For example, if the writeback object name is Writeback1_Test, the API name autopopulates as Writeback1_Test.
- Optionally, enter a description.
-
Save the node.
The writeback object node appears on the node canvas.
Add more writeback object nodes if required. You are now ready to configure the writeback object nodes in your chosen runtime.
- Configure a Writeback Object Node in CRM Analytics (CRMA) Runtime
After you add writeback object nodes to your definition, configure your writeback objects to indicate the target type. In the CRMA runtime, you can write back to Salesforce objects or Analytics datasets. - Configure a Writeback Object Node in Data 360 Runtime
After you add writeback object nodes to your definition, configure your writeback objects to indicate the target type. In the Data 360 runtime, you can write back to a Salesforce object, data lake object, or data model object. - Map Related Fields by Using Einstein
Use Einstein generative AI to simplify the tedious task of manually mapping fields when you configure a writeback node. - Write Related Records from Multiple Objects Together
Use the composite writeback node in your Data Processing Engine definition to collate related records from multiple writeback objects. Then write back all the interrelated records together to the target objects, so that you maintain data integrity and avoid any inconsistencies in case of failures.