Setting Up Sync for End Dating m3ter Account Billing Entities

• Account Plan
• Prepayment/Commitment
• Contract
• Pricing
• Counter Pricing

• End Dating Using Set Up and Submit Form in UI
• End Dating Using Invocable Action

​

End Dating Using Set Up and Submit Form in UI

1. In your Salesforce Org under Page Layouts, use the Mobile and Lightning Actions list to add the End Date m3ter Billing Data button to the page where you want it to reside.

2. On the page, select the End Date m3ter Billing Data button. The set up form opens for the selected Account:

3. Use the End Date calendar icon to open and select the end date you want to apply to the Account billing entities.
4. Under Select Billing Entities, select each of the entities linked to the Account you want to end date in the Available box and use the arrow to transfer them to the Selected box:

• Note that the Submit to m3ter button is now activated.

5. If the selected Account is a parent Account and you want to apply end dating to the selected billing entities linked to the Account’s child Accounts in your m3ter Organization, select the Apply to Child Accounts checkbox.
6. Select Submit to m3ter. The end dating sync action is performed:

• If the action is successful, you’ll receive a confirmation message with details of the Account billing entities that were updated accordingly in your m3ter Organization:

• If the action fails, you’ll see an error message:

​

End Dating Using Invocable Action

• 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

• Importantly, note that you must check and alter for the correct namespace and depending on the environment:

List<m3tertest.EndDateM3terEntitiesInvocable.M3terEndDateSyncRequest> requests;
List<m3tertest.EndDateM3terEntitiesInvocable.M3terEndDateSyncResult> results;

System.debug('Testing Valid Record');
requests = new List<m3tertest.EndDateM3terEntitiesInvocable.M3terEndDateSyncRequest>{
        new m3tertest.EndDateM3terEntitiesInvocable.M3terEndDateSyncRequest()
};
requests[0].recordId = '006Pu00000G88gkIAB';
requests[0].endDate = '2024-12-30T00:00:00Z';
requests[0].applyToChildRecords = false;
requests[0].billingEntities = new List<String>{'CONTRACT'};

results = m3tertest.EndDateM3terEntitiesInvocable.endDateM3terEntities(requests);
if (!results.isEmpty()) {
    m3tertest.EndDateM3terEntitiesInvocable.M3terEndDateSyncResult result = results[0];
    System.debug('=== Result Details ===');
    System.debug('Success: ' + result.success);
    System.debug('Message: ' + result.message);
    System.debug('Response: ' + result.response);
    System.debug('====================\n');
}

​

Sample Output

​

Reviewing Feature 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
  • Invalid End Date format
  • Invalid Billing Entities

​

Status Codes and Messages

• Success: All objects synced successful.
• 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.