sObjects That Cannot Be Used Together in DML Operations

Some sObjects require that you perform DML operations on only one type per transaction. For example, you cannot insert an account, then insert a user or a group member in a single transaction. The following sObjects cannot be used together in a transaction:

Group
You can only insert and update a group in a transaction with other sObjects. Other DML operations are not allowed.
GroupMember
You can only insert and update a group member in a transaction with other sObjects in Apex code that is saved using Salesforce API version 14.0 and earlier.
QueueSObject
User
You can insert a user in a transaction with other sObjects in Apex code that is saved using Salesforce API version 14.0 and earlier.
You can insert a user in a transaction with other sObjects in Apex code that is saved using Salesforce API version 15.0 and later if UserRoleId is specified as null.
You can update a user in a transaction with other sObjects in Apex code that is saved using Salesforce API version 14.0 and earlier
You can update a user in a transaction with other sObjects in Apex code that is saved using Salesforce API version 15.0 and later if the following fields are not also updated:
- UserRoleId
- IsActive
- ForecastEnabled
- IsPortalEnabled
- Username
- ProfileId
UserRole
UserTerritory
Territory
Custom settings in Apex code that is saved using Salesforce API version 17.0 and earlier.

For these sObjects, there are no restrictions on delete DML operations.

Important

The primary exception to this is when you are using the runAs method in a test. For more information, see System Methods.

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.

If you are using a Visualforce page with a custom controller, you can only perform DML operations on a single type of sObject within a single request or action. However, you can perform DML operations on different types of sObjects in subsequent requests, for example, you could create an account with a save button, then create a user with a submit button.