sObjects That Can’t Be Used Together in DML Operations

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.

• 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.

This process is demonstrated in the example in the next section.

1public class MixedDMLFuture {
2    public static void useFutureMethod() {
3        // First DML operation
4        Account a = new Account(Name='Acme');
5        insert a;
6        
7        // This next operation (insert a user with a role) 
8        // can't be mixed with the previous insert unless 
9        // 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 class Util {
2    @future
3    public static void insertUserWithRole(
4        String uname, String al, String em, String lname) {
5
6        Profile p = [SELECT Id FROM Profile WHERE Name='Standard User'];
7        UserRole r = [SELECT Id FROM UserRole WHERE Name='COO'];
8        // Create new user with a non-null user role ID 
9        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 u;
16    }
17}