Loading
Salesforce now sends email only from verified domains. Read More
CRM Analytics
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Write Recipe Output to Data 360

          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
          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 remains unchanged.

          For information on limits, see Write To Data 360 Limits

          Note
          Note Enable Data 360 in your org to create and use DLOs.

          A recipe created to write output to Data 360 can only contain 2 nodes, an input node and the output node. Perform any necessary data prep on the data in a separate recipe first.

          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.
          3. In Data Manager, click Recipes.
          4. In the recipe, select the add node button (Add Node button) at the end of the recipe.
          5. For the node type, select Output.
            The Add Node window shows all possible nodes that you can add, including the output node.
          6. To create a DLO, for Write To, select Data Cloud.
            The Data 360 option for Write To in an output node.
            1. Enter the DLO name, and optionally, the DLO API name.
              If no DLO exists with this name, the recipe creates a new one. If you don’t specify the DLO API name, node creation generates a unique value.
              Warning
              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.
              The Data 360 DLO category selection for Write To in an output node.
            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. We recommend you pick a field that is a unique identifier.
          7. To update an existing DLO, for Write To, select Existing DLO.
            The Existing DLO option for Write To in an output node.
            1. Select the operation, Append, Upsert, or Delete.
              Note
              Note Write to Data Cloud Optimized Output is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer’s sole discretion.
            2. Select a Data Lake Object to run the operation on.

              The append operation adds all data from the input to the existing DLO, and records can be duplicated. 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.

              These operations are supported for both Home and Companion Data 360 orgs.

          8. Verify the results in the Preview panel and click Apply.
            If Apply is disabled, check that you have values for every output field and that the recipe input is a CRM Analytics dataset.
          9. Save and run the recipe to generate the Data 360 DLO.

          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 at creation if
            • 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.
          • After a DLO is associated with a data space, you can’t remove it from the data space in the recipe editor. After the recipe creates successfully, data spaces can be added to the output node, but not removed.
          • 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_<PrimaryKey>
           
          Loading
          Salesforce Help | Article