Setting Up and Using Sync to m3ter Invocable Action

• Allows for easy integration with Salesforce Flows and Apex, enabling automated sync processes based on a customer business process or automation needs.
• Extends the current manual sync functionality and leverages the same metadata / configuration driven approach by adding a layer of extensibility, namely via a new IA named Sync To m3ter

• Implementing Sync to m3ter IA
• Reviewing Feature Details
• Reviewing Guardrails and Limits
• Enforcing Asynchronous Processing

​

Implementing Sync to m3ter IA

• Flow
• APEX

​

Flow

1. To enable Run Asynchronously, you must select the checkbox for:

• Include a Run Asynchronously path to access an external system after the original transaction for the triggering record is successfully committed.

2. In the options for When to Run the Flow for Updated Records, you must select:

• Only when a record is updated to meet the condition requirements.

3. You must add the Action to the Run Asynchronously path.

​

APEX

// Create a new sync request
m3.SyncToM3terService.M3terSyncRequest req = new m3.SyncToM3terService.M3terSyncRequest();
req.parentRecordId = '006S900000795MMIAY';  // Replace with an actual Salesforce ID

// Call the invocable action
List<m3.SyncToM3terService.M3terSyncResult> results = m3.SyncToM3terService.syncToM3ter(
    new List<m3.SyncToM3terService.M3terSyncRequest>{req}
);

// Process the results
if (!results.isEmpty()) {
    m3.SyncToM3terService.M3terSyncResult result = results[0];
    
    System.debug('Overall Sync Success: ' + result.success);
    System.debug('Sync Status: ' + result.syncStatus);
    System.debug('Sync Message: ' + result.message);
    
    // Output concatenated results
    System.debug('Concatenated Results:\n' + result.concatenatedResults);
    
    // Process individual object results
    for (m3.SyncToM3terService.M3terSyncObjectResult objResult : result.objectResults) {
        System.debug('Object: ' + objResult.objectName + 
                     ', Success: ' + objResult.success + 
                     ', Message: ' + objResult.message +
                     ', Salesforce ID: ' + objResult.salesforceId);
    }
} else {
    System.debug('No results returned from sync operation.');
}

​

Sample Outputs

1. Success = True, Sync Status = Completed:

2. Success = False, Sync Status = Partial Success:

​

Reviewing Feature Details

​

Invocable Action - Sync to m3ter

​

Individual Sync Results Details

​

Reviewing Guardrails and Limits

​

Single Record Processing

• The Action is explicitly designed to process only one record at a time.
• Multiple record requests will result in a Failed status with appropriate error message.

​

Record Validation

• Performs existence check on the parent record before initiating sync.
• Returns specific error statuses for:
  • Invalid/null record IDs.
  • Non-existent records.
  • Record access issues.

​

Status Codes and Messages

• Completed: All objects synced successful.
• Partial Success: Some objects synced successfully, others failed.
• Failed: System-level failures (CPU limits, validation errors, and so on).

​

Enforcing Asynchronous Processing

• “You have uncommitted work pending. Please commit or rollback before calling out”

1. Flows: If the action is not set to run asynchronously, and there are any DML operations before it in the flow, you will encounter this error.
2. Apex: If you try to call the action directly after performing DML operations in the same transaction, you will get this error.

1. Flows: Always use the “Run Asynchronously” option for the Sync to m3ter action.
2. Apex: Use the @future(callout=true) method. This ensures the callout happens in a separate transaction.