[SalesForce] MIXED_DML_OPERATION, DML operation on setup object is not permitted Contact User

Hi i have a problem cuz I'm trying do sth like below:
this method has adnotation AuraEnabled

Contact contact = getContact((Id)contactId);
contact.Inactive__c = true;

User user = getUserByContactId(contactId);
user.IsActive = true;
update user;
update contact;

And I'm receiving error like :
MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): User, original object: Contact: []
… what should i do ?

Best Answer

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.

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

You can’t use the following sObjects with other sObjects when performing DML operations in the same transaction.

FieldPermissions
Group
GroupMember

You can only insert and update a group in a transaction with other sObjects. Other DML operations aren’t allowed.

ObjectPermissions
PermissionSet
PermissionSetAssignment
QueueSObject
ObjectTerritory2AssignmentRule
ObjectTerritory2AssignmentRuleItem
RuleTerritory2Association
SetupEntityAccess
Territory2
Territory2Model
UserTerritory2Association

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 if the user isn’t included in an Lightning Sync configuration (either active or inactive) and the following fields are not updated:

UserRoleId
IsActive
ForecastEnabled
IsPortalEnabled
Username
ProfileId

More information here:-

Related Solutions

[SalesForce] MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa)

You are going to have to move your logic to a future method to create a separate transaction. To do so, you will need to move this logic to a separate class (which you should be doing anyway). Note that you also should not be calling any DML, futures, etc within a for loop. This is bulkification 101. Create a collection of names, then pass them in once your loop is done.

public class ApplicationService
{
    public static void createContentWorkspaces(List<Application__c> records)
    {
        Set<String> names = new Set<String>();
        for (Application__c record : records)
            names.add(record.Account__c);
        createContentWorkspaces(names);
    }

    @future
    public static void createContentWorkspaces(Set<String> name)
    {
        List<ContentWorkspace> records = new List<ContentWorkspace>();
        for (String name : names) records.add(new ContentWorkspace(Name=name));
        insert records;
    }
}

[SalesForce] System.DmlException: Insert failed: MIXED_DML_OPERATION, DML

If the underlying code under test does DML on GroupMember and DML on "normal" (i.e. non-setup) SObjects like Account or Contact, then the DML on GroupMember has to be done in a separate transaction such as @future or a queueable. Your OP indicates that GroupMember is done in a @future.

For the testmethod, if you need to pre-insert some GroupMember to test logic, you will need to do the following

System.runAs([select Id from User where Id = :UserInfo.getUserId()][0]) {
  insert GroupMember(...); // setup objects must be inserted in a separate context
}

Test.startTest();  
  new MyClass().doWork(); // code path eventually ends up calling addToPublicGroup
Test.stoptest(); // this will cause the future method to execute
System.assert(...whatever is needed...);

Best Answer

Related Solutions

[SalesForce] MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa)

[SalesForce] System.DmlException: Insert failed: MIXED_DML_OPERATION, DML

Related Topic