Loading

Salesforce CPQ does not support allOrNone parameter in some CPQ DML scenarios

Publiceringsdatum: Sep 27, 2025
Beskrivning
The allOrNone parameter can be set to allow DML statements to succeed for some records while only failing for those records that encounter errors (See: Database Class Developer Documentation).  Due to the nature of the triggers creating records in the background, some CPQ processes do not support the allOrNone parameter or may have limited support for the parameter.
Lösning

While many operations in Salesforce CPQ will allow for this operation to work as expected, there are some known exceptions to support for allOrNone=FALSE DML operations within the Salesforce CPQ package.

Note: This is not a comprehensive list of places where CPQ does not support allOrNone, but it covers the most common use cases.

  • Checking Ordered on multiple Opportunities - If one of the Orders fails to create due to an error, then the entire operation fails (i.e. All Opportunities are returned to their original state)
  • Checking Ordered on multiple Quotes - If one of the Orders fails to create due to an error, then the entire operation fails (i.e. All Quotes are returned to their original state).
  • Checking contracted on multiple Opportunities while using 'Contract in Foreground' - If one contract fails to generate, then the entire operation fails (i.e. All Opportunities are returned to their original state).
  • Checking Renewal Forecast/Renewal Quoted on a list of contracts - If the synchronous portion of the Renewal Opportunity creation fails for any contract, then the entire operation will fail (i.e. All Contracts are returned to their original state).
Knowledge-artikelnummer

000393650

 
Laddar
Salesforce Help | Article