---
schema_version: "1"
id: 1b37bd4714189570bb7da2c028e92a195e39ddad5ecf7e17816366324aa467f9
title: Write Recipe Output to Data 360
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_recipe_output_results_dc.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_recipe_output_results_dc.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2546fdf631b2705f1a4f9b9974fd99491454730fc480bc4f976f737c54044700
description: Use the Data Prep output node in CRM Analytics to save your prepared data as a Data 360 data lake object (DLO). After your data is in Data 360, you can create calculated insights, semantic models, and Data 360 reports and dashboards.
products:
- CRM Analytics
- Cross Cloud
release: "264"
---
# Write Recipe Output to Data 360
Use the Data Prep output node in CRM Analytics to save your prepared data as a Data 360 data lake object (DLO). After your data is in Data 360, you can create calculated insights, semantic models, and Data 360 reports and dashboards.
### Required Editions
User Permissions
Needed
To manage and create a recipe:
Edit CRM Analytics Dataset Recipes
To view Data 360:
Data 360 User permission set
Note As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you may see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remain unchanged.
For information on limits, see [Write To Data 360 Limits](https://help.salesforce.com/s/articleView?id=analytics.bi_limits.htm&release=264.0.0&type=5).
Note Enable Data 360 to create and use DLOs.
A recipe created to write output to Data 360 can only contain 3 node types, input nodes, filter nodes, and output nodes. Perform any other necessary data prep on the data in a separate recipe first.
To write out to multiple DLOs from one recipe, add an input, filter it, and write it out, and then repeat as necessary. At run time, the recipe job processes each set of input and output nodes sequentially.
You can only use existing CRM Analytics datasets as input sources. You can't use input directly from external connectors or data sync objects.
## Enable the Write to Data Cloud Feature
1. From Setup, in the Quick Find box, enter Analytics, select **Analytics**, and then **Settings**.
2. Select **Enable CRM Analytics recipe to write output dataset to Data Cloud** and then save your changes.
Note Turn on this setting to make the **Data Cloud** option available in the Output node.
Starting in Winter '27, you can write recipe output to Data 360 in Government Cloud.
## Create Data Cloud Output
1. In Data Manager, click **Recipes**.
2. Open an existing recipe or click **New Recipe**.
3. In the recipe editor, after adding an input node and an optional filter node, select the add node button ().
4. For the node type, select **Output**.
5. To create a DLO, for Write To, select **Data Cloud**.
1. Enter the DLO name, and optionally, the DLO API name.
If no DLO exists with this name, the recipe creates one. If you don’t specify the DLO API name, node creation generates a unique value.
Warning If the DLO exists, the recipe overwrites it. Make sure that you use a unique name if you don’t want to overwrite an existing DLO.
2. Select one or more Data 360 data spaces.
You can add up to 5 data spaces.
3. Select the DLO category.
4. Select the primary key for the DLO from the input fields.
Any text field can be the primary key as long as the field doesn't contain empty values. Select a field that is a unique identifier.
6. To update an existing DLO, for Write To, select **Existing DLO**.
1. Select the operation: Append, Upsert, or Delete.
2. Select a Data Lake Object to run the operation on.
The append operation adds all data from the input to the existing DLO. Appending can duplicate records. The upsert operation appends data from the input to the DLO if new, and overwrites existing rows when they match. The delete operation removes input data from the existing DLO when existing rows match.
The data space and primary key values default to the existing DLO values and aren't editable.
Both Home and Companion Data 360 orgs support these operations.
7. Verify the results in the Preview panel.
If **Apply** is disabled, check that you have values for every output field and that the recipe input is a CRM Analytics dataset.
8. Click **Apply**.
9. Save and run the recipe to generate one or more Data 360 DLOs.
Schedule the recipe to run at regular intervals or based on other data sync events. You can view the recipe output in Data 360, on the Data Lake Objects tab.
**Considerations for DLO creation:**
- Multi-value fields in CRM Analytics datasets convert to text fields in the Data 360 DLO.
- Recipes fail validation during creation in these situations:
- The DLO API name exceeds 40 characters. The name can't contain . characters.
- An API name of any field in the CRM Analytics dataset contains \_\_c.
- An API name of any field in the CRM Analytics dataset is a duplicate of a field in the Data 360 DLO.
- The number of fields in the CRM Analytics dataset exceeds 1050.
- The number of fields of a specific type exceeds 800.
- DLO field names have a `__c` suffix. For example, the `sku` is `sku__c`.
- After the recipe associates a DLO with a data space, you can't remove the DLO from the data space in the recipe editor. After the recipe creates successfully, you can add data spaces to the output node as needed.
- The input dataset can't contain columns with these names, as they're reserved keywords in Data 360:
- DataSource
- DataSourceObject
- InternalOrganization
- cdp\_sys\_PartitionDate
- cdp\_sys\_SourceVersion
- cdp\_sys\_record\_currency
- KQ\_
**Working with Home Orgs and Companion Orgs**
The CRM Analytics recipe creates and updates the DLO in your Data 360 home org, even though the recipe can run in the home org or any Data Cloud One companion org. Always verify that the DLO was created and output correctly in your home org.
If the DLO isn't visible in the home org, verify that the recipe ran and completed successfully.
The recipe shares the DLO to the selected data space when it's created. To use the data in companion orgs, map the DLO to one or more data model objects (DMO). Then, sync your data space to your companion orgs for DMO visibility and use.
For more information on companion orgs, see [Access Data Cloud One from a Companion Org](https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud_one_app.htm&language=en_US).
#### See Also
- [_Salesforce Help_: Data Objects in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_objects.htm&language=en_US)
- [_Salesforce Help_: Data Lake Object Naming Standards](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_object_naming.htm&language=en_US)