---
schema_version: "1"
id: cd3d6116588e0dc525d7847988a31642893e5c72c375cfc9b59dd48ed766c2bd
title: Data Processing Engine
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dpe_intro.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dpe_intro.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 374b6d93dd56c3deada751282f04231048efdbf6e2541e93654025ecade9f137
description: Simplify complex data transformation and calculations at scale with Data Processing Engine. Use an intuitive, zero-code interface to unify data from diverse sources such as objects, Data 360, datasets, and external files. Design advanced transformations like joins, aggregations, and formulas. Make the transformed data actionable by writing results directly to objects, Data 360, and CRM Analytics. Schedule data transformation runs based on your business requirements to provide users up-to-date data when and where they need it.
products:
  - Cross Cloud
release: "264"
---
# Data Processing Engine

Simplify complex data transformation and calculations at scale with Data Processing Engine. Use an intuitive, zero-code interface to unify data from diverse sources such as objects, Data 360, datasets, and external files. Design advanced transformations like joins, aggregations, and formulas. Make the transformed data actionable by writing results directly to objects, Data 360, and CRM Analytics. Schedule data transformation runs based on your business requirements to provide users up-to-date data when and where they need it.

- **[Get Started with Data Processing Engine](https://help.salesforce.com/s/articleView?id=ind.dpe_get_started_with_data_processing_engine.htm&release=264.0.0&type=5)**  
    Data Processing Engine is a metadata-driven visual tool that helps you create definitions by using various nodes for different types of data transformations. Data Processing Engine facilitates efficient and effective processing of data to make it useful for analysis, reporting, and other business intelligence activities. Run the definitions by using invocable actions in Salesforce Flow, Invocation API, or by using the Data Processing Engine designer. You can also monitor the definition runs and view detailed execution status by using Monitor Workflow Services.
- **[Supported Editions for Data Processing Engine](https://help.salesforce.com/s/articleView?id=ind.dpe_editions.htm&release=264.0.0&type=5)**  
    Review the supported editions and availability for Data Processing Engine (DPE).
- **[Learn about Data Processing Engine](https://help.salesforce.com/s/articleView?id=ind.dpe_learn_explore.htm&release=264.0.0&type=5)**  
    Learn concepts related to Data Processing Engine. Understand how Data Processing Engine works and how you can leverage Data Processing Engine to transform your org data.
- **[Data Processing Engine Setup](https://help.salesforce.com/s/articleView?id=ind.dpe_setup_parent.htm&release=264.0.0&type=5)**  
    Assign users the permissions that they require to work with Data Processing Engine. Configure Data 360 or Salesforce Data Pipelines as the runtime platform for your company's Data Processing Engine definitions.
- **[Work with Data Processing Engine](https://help.salesforce.com/s/articleView?id=ind.dpe_work_with_dpe.htm&release=264.0.0&type=5)**  
    Learn to create, activate, run, and delete Data Processing Engine definitions. Learn to monitor your Data Processing Engine definition runs and view the status of your definition runs. Also, learn best practices and troubleshooting tips.
- **[Troubleshoot Data Processing Engine Issues](https://help.salesforce.com/s/articleView?id=ind.dpe_run_error_analysis.htm&release=264.0.0&type=5)**  
    Find resolutions for commonly encountered issues during the configuration, design, and execution of your Data Processing Engine (DPE) definitions. When a run fails, use the error code in Monitor Workflow Services to identify the root cause and apply the matching fix. For most system-level errors, running the definition again resolves the issue.