CloudSense Subscription/Order Generation Fails in SFDC Batch Order Decomposition Due to Future Method in Managed Trigger

Solution

Error signature (how to recognize this issue)

You may be impacted if AsyncApexJobs/debug logs show a failure similar to:

First error: Insert failed. First exception on row 0; first error:
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, csordtelcoa.AllServiceTriggers: execution of AfterInsert
caused by: System.DmlException: Update failed. First exception on row 0 with id <record_id>...

This is commonly reported during a flow like:

1. Create Opportunity
2. Add Service Location
3. Create Product Basket → add products
4. Generate product configurations → edit configurations
5. Click “Sync Forecasted Products”
6. Change Opportunity Stage to “Ordered”

Conditions where this typically occurs

• Your org is using SFDC batch processing for order decomposition (batch mode).
• The error is thrown from a managed package trigger/class (csordtelcoa.AllServiceTriggers), so the code cannot be viewed/modified directly.
• The SM Options custom setting is not configured for batch mode.

Root cause (what is actually failing)

When SM Options → disable_triggers__c is false, CloudSense may initiate reverse mappings on Service record updates that invoke a Future method.

Salesforce restriction:

• Future methods are not permitted in Batch context.

Because order decomposition is running in Batch context, the managed trigger’s AfterInsert path fails, resulting in:

• CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY and an underlying System.DmlException.

Resolution (configuration change)

Step 1 — Update SM Options for batch mode

1. In Salesforce Setup, navigate to Custom Settings.
2. Open SM Options (CloudSense custom setting).
3. Locate the setting/field: disable_triggers__c
4. Set: disable_triggers__c = true
5. Save.

Why this works: With triggers disabled for batch mode, the reverse-mapping path that relies on Future methods is not invoked during batch processing.

Step 2 — If reverse mappings are required, use the documented batch-mode approach

When operating in batch mode (triggers disabled), follow the documented guidance to:

• Call the processReverseMapping API before MACD creation, if your process requires reverse mappings to be applied.

Note: Implementation specifics depend on your existing automation/integration pattern. Ensure the API call occurs prior to the MACD creation step in your batch-mode workflow.