Analyze a Data Processing Engine Run in Explainability Mode

View how records flow through a Data Processing Engine (DPE) definition by analyzing a run in Explainability mode. Use detailed counts for checkpoints or output nodes to validate the setup and confirm that eligibility criteria are applied correctly.

Required Editions

Available in: Enterprise, Unlimited, and Developer Editions that have Rebate Management enabled.
User Permissions Needed
To run a DPE in explainability mode: Rebate Management Admin permission set
  1. Click Setup, and select Developer Console.
  2. Click Debug and select Open Execute Anonymous Window.
  3. Paste the following script. Replace the BatchJobPart ID with the value for the node you want to review.
    try {
                BatchJobPart record = [
                    SELECT RecordFileBody, RecordFileName 
                    FROM BatchJobPart 
                    WHERE Id = '0meLT000000YonMYAS'
                    LIMIT 1
                ];
    
                Blob decodedBlob = record.RecordFileBody;
                String fileData = decodedBlob != null ? decodedBlob.toString() : 'No file data found.';
    
                System.debug('Decoded File Data: ' + fileData);
            } catch (Exception e) {
                System.debug('Error: ' + e.getMessage());
       }
  4. Click Execute.
  5. Open the Logs tab in the Developer Console and double-click the most recent Execute Anonymous log entry.
  6. In the Execution Log, select the Debug Only checkbox.
  7. Locate the log entry starting with Decoded File Data: to view the retrieved output records.

The decoded output data for the selected DPE node is displayed in the debug logs. Use this data to verify how records were processed during the DPE run and confirm expected outcomes.

Note
Note If no records are returned, the log may display the error: “List has no rows for assignment to SObject”. Verify that the BatchJobPart ID is correct and corresponds to a valid DPE run node that contains data.