Data Processing Engine definitions can run either on CRM Analytics (CRMA) or on Data Cloud. Each runtime offers unique capabilities and is suited for different data processing needs. Select a runtime for your definitions based on the complexity of transformations and data volumes.
Required Editions
| View supported editions. |
CRM Analytics Runtime
The CRM Analytics runtime offers a comprehensive set of data transformation options that use the capabilities of the CRMA platform. It's ideal for complex data operations and transformations. Use the data from an analytics dataset or from objects, perform transformations, and store the results in an analytics dataset or an object. In CRMA runtime, perform complex operations such as evaluating formulas, forecasting data, and appending data from multiple data sources. Join multiple data sources, filter records, and aggregate data based on your specific needs.
Data 360 Runtime
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.
The Data 360 runtime efficiently handles large data volumes, managing data between Platform and Data 360. It's best for joining multiple sources, filtering records, evaluating formulas, grouping and aggregation, and storing results in Data 360. Definitions can use data lake objects (DLOs), data model objects (DMOs), calculated insights objects (CIOs), Salesforce objects, and CSV files as data sources. And write back to DLOs, DMOs, and Salesforce objects. Data 360 runtime is best suited for processing large data volumes.
Create and run definitions in home orgs and connected companion orgs. Tie definitions to data spaces to make sure that definitions only transform data that reside in the selected data space. By default, definitions always run on the default data space. On a home org, definitions can use data from the home org and the connected companion orgs as data sources. On companion orgs, definitions use data from the companion org as data source and write back results to the companion org.
Here are a few restrictions of the Data 360 runtime:
- The Forecast node isn't available in definitions.
- Definition can't run on Developer edition orgs that have a namespace prefix.