Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Why: When batches of records are created or updated, the processes that they trigger can fail and block records from being saved. Previously, if a failed process blocks one record in a batch from being saved, all records in the batch aren’t saved. With this critical update, Salesforce rolls back only the records whose processes failed and tries three times to save the records whose processes succeeded. This functionality is called “partial save.”
- An action in a platform-event process
- An action in an invocable process
- A scheduled action in a record-change process
- An immediate action that follows the “all or nothing” rule in a record-change process
This table shows which immediate actions follow the all or nothing rule in record-change processes.
|Immediate Process Actions||Without This Update||With This Update|
|Apex||Depends on code||Depends on code|
|Create a Record||All or nothing||Partial save|
|Email Alerts||All or nothing||All or nothing|
|Flows||All or nothing||All or nothing|
|Post to Chatter||All or nothing||All or nothing|
|Processes||All or nothing||All or nothing|
|Quick Actions||All or nothing||All or nothing|
|Submit for Approval||All or nothing||All or nothing|
|Update Records||All or nothing||Partial save|
For example, when you create an account, a process on Account creates an opportunity and sets its opportunity amount to the account revenue. A validation rule on Opportunity requires that the opportunity amount is greater than zero. When you use Data Import Wizard to import 100 accounts, and one of the accounts has revenue set to zero, the process fails to create an opportunity for that account.
Without this critical update, none of the 100 accounts and opportunities are created. The action to create an opportunity for each account is executed in bulk and follows the all or nothing rule. When the bulk operation fails to create an opportunity for the one account with zero revenue, the entire batch is rolled back.
With this critical update, 99 accounts and opportunities are created successfully. Because of partial save, only the one account with zero revenue fails to create a related opportunity, and the creation of that account is rolled back.
How: To test this critical update, we recommend working in a sandbox. If you must work in your production org, do so during off-peak hours.
- From Setup, enter Critical in the Quick Find box, then select Critical Updates.
- For Enable Partial Save for Create and Update Operations in Processes, click Activate.
- Test all your flows and processes.
If you experience issues, contact Salesforce Customer Support.