---
schema_version: "1"
id: 884932345d1738dae23857d3f89ea189182003019a4779299fbe222672eb0141
title: Clone and Customize the Predefined Data Processing Engine Definition for Collections Summary
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/collections_clone_dpe_account_summary.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.collections_clone_dpe_account_summary.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9f7a6e06faea8345acbd2ffac6b17f940c3ea03d9db9a4be3a9c499f3ecfc0b1
description: Clone and customize the predefined Data Processing Engine definition. This definition is designed to compute the aggregated summary of specific collection plan fields, such as the initial amount due, current amount due, payments received, and the average days past due for all collection plans linked to an account.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Clone and Customize the Predefined Data Processing Engine Definition for Collections Summary

Clone and customize the predefined Data Processing Engine definition. This definition is designed to compute the aggregated summary of specific collection plan fields, such as the initial amount due, current amount due, payments received, and the average days past due for all collection plans linked to an account.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <a href="https://help.salesforce.com/s/articleView?id=ind.collections_editions_permissions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported products, editions, and permissions for Collections. Then learn how your product handles permissions and how to assign them.">View product and edition availability.</a></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d13595e68">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13595e68 ">To clone and customize the prebuilt Data Processing Engine definition:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d13595e68 ">
              <p>Collections and Recovery Admin permission set</p>
              <p>AND</p>
              <p>Customize Application
                permission</p>
              <p>AND</p>
              <p>Modify All Data permission</p>
              <p>AND</p>
              <p style="margin-bottom:0;">Data
                Pipelines Base User permission set</p>
            </td>

          </tr>
        </tbody>
      </table>

1. From Setup, in the Quick Find box, enter Data Processing Engine, and then select **Data Processing Engine**.
2. To download the predefined Data Processing Engine definition, Collections Summary for Account, from the action menu, click ![Download Data Processing Engine Definition](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-collections-264-0-0-production-enus/3689d02c-0a37-45ca-bd97-514087074dd3/collections/images/collections_dpe_download.png).
3. Open the definition that you downloaded, which is in the JSON format.
4. Replace the FullName according to your requirements. For example, CollectionsSummaryForCaroleWhite. Make sure that the full name doesn't contain any spaces or special characters.
    
    ```
    {
      "FullName": "CollectionsSummaryForCaroleWhite",
      "Metadata": {
        "aggregates": [
          {
            "fields": [
    ```
5. Replace the label and name according to your requirements. For example, Collections Summary for Carole White.
    
    ```
    "groupBy": [
              "AccountId"
            ],
            "label": "Collections Summary for Carole White",
            "name": "Collections_Summary_For_Carole_White",
            "sourceName": "Collection_Plan_Filter"
          }  
    ```
6. Make sure that the field aliases for the custom sourceFieldNames in the Data Processing Engine definition match those listed in the table. If you've created custom fields with different API names, update the corresponding field aliases accordingly.
    
    |  |  |
    | --- | --- |
    | SourceFieldName | Alias |
    | DaysPastDue | AccountAverageDaysPastDue |
    | CurrentDueAmount | AccountTotalCurrentDueAmount |
    | InitialDueAmount | AccountTotalInitialDueAmount |
    | TotalPaymentsReceived | AccountTotalPaymentsReceived |
    
    ```
    {
      "FullName": "Account Collections Summary","AccountCollectionsSummaryCloned",
      "Metadata": {
        "aggregates": [
          {
            "fields": [
              {
                "aggregateFunction": "Avg",
                "alias": "AccountAverageDaysPastDue",
                "sourceFieldName": "DaysPastDue"
              },
              {
                "aggregateFunction": "Sum",
                "alias": "AccountTotalCurrentDueAmount",
                "sourceFieldName": "CurrentDueAmount"
              },
              {
                "aggregateFunction": "Sum",
                "alias": "AccountTotalInitialDueAmount",
                "sourceFieldName": "InitialDueAmount"
              },
              {
                "aggregateFunction": "Sum",
                "alias": "AccountTotalPaymentsReceived",
                "sourceFieldName": "TotalPaymentsReceived"
              }
            ],
            "groupBy": [
              "AccountId"
            ],
    ```
7. Set isTemplate to False.
    
    ```
    "isTemplate": false,
        "label": "Account Collections Summary","Account Collections Summary Cloned"
        "parameters": [
          {
            "dataType": "Text",
            "isMultiValue": false,
            "label": "Input Record Id",
            "name": "Input_Record_Id"
          }
    ```
8. Make sure that definitionRunMode is set to OnDemand.
    
    ```
    "definitionRunMode": "OnDemand",
        "description": "Adds quote line items from a CSV file to a quote.",
        "doesGenAllFailedRecords": false,
        "executionPlatformObjectType": "None",
        "executionPlatformType": "CORE",
    ```
9. Set writebackUser to a user ID who plans to run this cloned Data Processing Engine definition. Make sure that this user has create, read, update, delete permissions on the Collection Plan and Account objects.
    
    ```
     "isChangedRow": false,
            "isExistingDataset": false,
            "label": "Collection Plan Writeback",
            "name": "Collection_Plan_Writeback",
            "operationType": "Update",
            "shouldCreateTargetObject": false,
            "sourceName": "Collection_Plan_Aggregate",
            "storageType": "sObject",
            "targetObjectName": "Account",
            "writebackRecordMaxLimit": 0,
            "writebackSequence": 1,
            "writebackUser": "<User ID who runs this cloned definition>"
    ```
10. Run the API endpoint and provide the content of the cloned and customized Data Processing Engine definition in JSON format as the payload.
    
    ```
    /services/data/v65.0/tooling/sobjects/BatchCalcJobDefinition
    ```
11. From the API endpoint's response, note the record ID of the cloned and customized Data Processing Engine definition.
12. From Setup, in the Quick Find box, enter Data Processing Engine, and then select **Data Processing Engine**.
13. Make sure that the cloned and customized Data Processing Engine is listed.