Contents
What are mixed DML operations?
Mixed DML operations within a single transaction aren’t allowed. You can’t perform DML on a setup sObject and another sObject in the same transaction. However, you can perform one type of DML as part of an asynchronous job and the others in other asynchronous jobs or in the original transaction.
What is mixed DML in Salesforce?
DML operations on certain sObjects, sometimes referred to as setup objects, can’t be mixed with DML on other sObjects in the same transaction. This restriction exists because some sObjects affect the user’s access to records in the org. For example, you can’t update an account and a user role in a single transaction.
How are sobjects used in mixed DML operations?
Mixed DML Operations in Test Methods 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.
Can you do mixed DML in one transaction?
It creates a test user with a role and a test account, which is a mixed DML operation. Mixed DML operations within a single transaction aren’t allowed. You can’t perform DML on a setup sObject and another sObject in the same transaction.
Can you use mixed DML in asynchronous jobs?
However, you can perform one type of DML as part of an asynchronous job and the others in other asynchronous jobs or in the original transaction. This class contains an @future method to be called by the class in the subsequent example.
When to perform mixed DML operation in apex?
To avoid this error, we should perform DML operation on standard/custom object records in a different transaction. In general all the apex classes and apex triggers execute synchronously (execute immediately).