Predefined Data Processing Engine Definitions for Summary Rollups in Flexible Hierarchies
Explore the predefined Data Processing Engine definitions provided to roll up account and contact opportunities with Data Cloud or CRM Analytics. Understand how each definition functions and when to use it.
Required Editions
Available in: Lightning Experience Available in: Unlimited and Agentforce Editions |
Flexible Hierarchies includes these predefined Data Processing Engine definitions.
- Roll Up Account and Contact Opportunities with Data Cloud
- Roll Up Contact Opportunities with Data Cloud
- Roll Up Account and Contact Opportunities with CRM Analytics
- Roll Up Contact Opportunities with CRM Analytics
Note Access to these standard definitions depends on Data Cloud Runtime and CRM
Analytics Runtime availability. The Roll Up Account and Contact Opportunities with Data Cloud
and the Roll Up Account and Contact Opportunities with CRM Analytics Runtime definitions use
deduplication to prevent double-counting opportunities that appear at multiple hierarchy
levels.
Select between predefined and custom Data Processing Engine definitions according to your business requirements.
| Scenario | Recommended Approach |
|---|---|
| You want to roll up Opportunity Amount for Account and/or Contact nodes | Use a predefined definition. Clone it, and make these changes.
|
| You want to roll up a different value, such as Financial Account balance | Clone a predefined definition and customize the data source and join nodes to point to the new object. |
| You want to filter opportunities, such as only Closed Won opportunities | Clone a predefined definition and add a filter node after the data source node. |
| You have a completely different node type or measure type | Clone a predefined definition and update the Formula node (Format Node Contributions and Measures) to set the correct measure type value. |
| Your transform logic is significantly different from the predefined definitions | Create a new Data Processing Engine definition. Make sure to select Flexible Hierarchy as the process type and Flexible Hierarchy Node Summary as the writeback object. |
To understand how the rollup logic works, review the node-by-node explanation of the predefined definition, Roll Up Account and Contact Opportunities With Data Cloud. When customizing these predefined definitions, consider these key nodes.
| Node | What it Does | When to Customize |
|---|---|---|
| Filter Nodes for Hierarchy Type | Filters data to include only records relevant to your hierarchy type | Always required Enter the API name of your hierarchy type in the filter condition. |
| Join Opportunities and Accounts / Join Opportunities and Contacts | Links source records to hierarchy nodes using the reference record ID | Customize if you're rolling up a different object (for example, Financial Account or Financial Balance). Update the join keys to match the new object's relationship fields. |
| Merge Opportunities (Append node) | Combines account-linked and contact-linked opportunity records into a single dataset | Customize or remove if your hierarchy uses only one node type (for example, only Contact nodes). |
| Format Node Contributions and Measures (Formula node) | Assigns the Node Measure Type value and sets null contributions to zero | Always required
|
| Data source nodes (Load objects) | Load the source records—for example, Opportunity, Account, Contact, Flexible Hierarchy Node | Customize if you're rolling up a different source object. Update to load the correct object and select the relevant fields. |
- Explore the Roll Up Account and Contact Opportunities Data Processing Engine Definition
Explore a practical example of analyzing the predefined Data Processing Engine definition, Roll Up Account and Contact Opportunities With Data Cloud. Included with Flexible Hierarchies, this definition rolls up opportunity amounts linked to account and contact nodes.
Did this article solve your issue?
Let us know so we can improve!
