sObjects That Can’t Be Used Together in DML Operations
DML operations on certain sObjects, sometimes referred to as setup objects, can’t be mixed with DML on non-setup sObjects in the same transaction. This restriction exists because some sObjects affect the user’s access to records in the org. You must insert or update these types of sObjects in a different transaction to prevent operations from happening with incorrect access-level permissions. For example, you can’t update an account and a user role in a single transaction.
Don’t include more than one of these sObjects in the same transaction when performing DML operations or when using the Metadata API.
These sObjects also can’t be used with the @IsTest (IsParallel=true) annotation. Split such operations into separate transactions.
This list includes sObjects that cannot be used together in the same DML transaction, but is not an exhaustive list.
Note
AuthSession
ContentWorkspace
FieldPermissions
ForecastingShare
Group
You can only insert and update a group in a transaction with other sObjects. Other DML operations aren’t allowed.
GroupMember
With legacy Apex code saved using Salesforce API version 14.0 and earlier, you can insert and update a group member with other sObjects in the same transaction.
Note
ObjectPermissions
ObjectTerritory2AssignmentRule
ObjectTerritory2AssignmentRuleItem
PermissionSet
PermissionSetAssignment
QueueSObject
RuleTerritory2Association
SetupEntityAccess
Territory
Territory2
Territory2Model
User
You can insert a user in a transaction with other sObjects in Apex code saved using Salesforce API version 14.0 and earlier.
You can insert a user in a transaction with other sObjects in Apex code saved using Salesforce API version 15.0 and later when UserRoleId is specified as null.
You can update a user in a transaction with other sObjects in Apex code saved using Salesforce API version 14.0 and earlier
You can update a user in a transaction with other sObjects in Apex code saved using Salesforce API version 15.0 and later when the user isn’t included in a Lightning Sync or Einstein Activity Capture configuration (either active or inactive) and the following fields aren’t updated:
UserRoleId
IsActive
ForecastEnabled
IsPortalEnabled
Username
ProfileId
UserPackageLicense
UserRole
UserTerritory
UserTerritory2Association
If you’re using a Visualforce page with a custom controller, you can’t mix sObject types with any of these special sObjects within a single request or action. However, you can perform DML operations on these different types of sObjects in subsequent requests. For example, you can create an account with a save button, and then create a user with a non-null role with a submit button.
You can perform DML operations on more than one type of sObject in a single class using the following process:
Create a method that performs a DML operation on one type of sObject.
Create a second method that uses the future annotation to manipulate a second sObject type.
This process is demonstrated in the example in the next section.
Example: Using a Future Method to Perform Mixed DML Operations
This example shows how to perform mixed DML operations by using a future method to perform a DML operation on the User object.
1public with sharing class MixedDMLFuture{2 public static void useFutureMethod(){3 // First DML operation4 Account a = new Account(Name='Acme');5 insert as system a;67 // This next operation (insert a user with a role)8 // can't be mixed with the previous insert unless9 // it is within a future method.10 // Call future method to insert a user with a role.11 Util.insertUserWithRole(12 'mruiz@awcomputing.com', 'mruiz',13 'mruiz@awcomputing.com', 'Ruiz');14}15}
1public with sharing class Util{2 @future3 public static void insertUserWithRole(4 String uname, String al, String em, String lname){56 Profile p = [SELECT Id FROM Profile WHERE Name='Standard User' WITH SYSTEM_MODE];7 UserRole r = [SELECT Id FROM UserRole WHERE Name='COO' WITH SYSTEM_MODE];8 // Create new user with a non-null user role ID9 User u = new User(alias = al, email=em,10 emailencodingkey='UTF-8', lastname=lname,11 languagelocalekey='en_US',12 localesidkey='en_US', profileid = p.Id, userroleid = r.Id,13 timezonesidkey='America/Los_Angeles',14 username=uname);15 insert as system u;16}17}
Test methods allow for performing mixed Data Manipulation Language (DML) operations that include both setup sObjects and other sObjects if the code that performs the DML operations is enclosed within System.runAs method blocks. You can also perform DML in an asynchronous job that your test method calls. These techniques enable you, for example, to create a user with a role and other sObjects in the same test.