Apex Code Development You need to sign in to do that
Don't have an account?
Alesia Dvorkina 11 MIXED_DML_OPERATION in an Autolaunched Flow
I am working on a flow that would create a Contact when a new User (UserType = Standard) is created.
I am getting the following error:
An error occurred at element Create_Contact (FlowRecordCreate).
INSERT --- INSERT FAILED --- ERRORS : (MIXED_DML_OPERATION) DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): Contact, original object: User,
I have researched and found out that this is a common error when trying to perform DML operations on non-setup (Contact) and setup (User) objects. The solution for those who encountered this error from a Trigger is to split DML operations into future and non future context (perform DML on Non-Setup object type, then perform DML on Setup object type in @future methods).
How can I apply this logic to a Flow used in a Process? Any ideas? Thanks in advance for help!
@Carlos - I believe we are getting different results, since my Process is using a Flow, instead of the Action, since there's quite a lot of logic behind it (if statements and loops) that a flow cannot handle.
@James - creating multiple processes and multiple flows was my "last resort" solution (as creating a Trigger is not an option for me :) - it would take me weeks). But before I rebuilt my flow, I have decided to contact Salesforce Support and luckily :) got a very knowledgeable representative, who already dealt with this type of scenario.
Here is the solution:
In the process I used a Criteria of "No criteria - just execute the actions!" and for the Action I had my Flow that handled all of the logic. What I needed to do is to add some sort of criteria ("Conditions are met" or "Formula") and then add my Flow as an Action for Scheduled Actions, instead of Immediate Actions. Since I needed to execute my flow as soon as possible and the smallest time parameter is "1 Hour", the rep suggested to add a Time Schedule as "1 Hours BEFORE User.Last Modified Date (or use any other field you need)". It worked beautifully. So in Flows, equivalent of "@future" is a Scheduled Action.
I hope this helps to whoever else runs into this issue!
All Answers
Otherwise, you'll have to implement the logic in a trigger and use the future method as you have already mentioned.
I have just try to reproduce the behavior you explain using process builder and "sadly" I have created the contact record without any problem...
As you can see, the record creation is quite simple. The criteria diamond just checks a checkbox field value in order to trigger the contact record creation.
I'm not sure if this is the same scenario you are experiencing, so please let me know if I can help you further.
Regards,
@Carlos - I believe we are getting different results, since my Process is using a Flow, instead of the Action, since there's quite a lot of logic behind it (if statements and loops) that a flow cannot handle.
@James - creating multiple processes and multiple flows was my "last resort" solution (as creating a Trigger is not an option for me :) - it would take me weeks). But before I rebuilt my flow, I have decided to contact Salesforce Support and luckily :) got a very knowledgeable representative, who already dealt with this type of scenario.
Here is the solution:
In the process I used a Criteria of "No criteria - just execute the actions!" and for the Action I had my Flow that handled all of the logic. What I needed to do is to add some sort of criteria ("Conditions are met" or "Formula") and then add my Flow as an Action for Scheduled Actions, instead of Immediate Actions. Since I needed to execute my flow as soon as possible and the smallest time parameter is "1 Hour", the rep suggested to add a Time Schedule as "1 Hours BEFORE User.Last Modified Date (or use any other field you need)". It worked beautifully. So in Flows, equivalent of "@future" is a Scheduled Action.
I hope this helps to whoever else runs into this issue!