function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
prasanth puvvada 4prasanth puvvada 4 

future method implementation error

First i wrote about "creating of new user"  Secoend "inserting a new record into ACCOUNT object".  

ERROR at V.F.page:-  
Insert failed. First exception on row 0; first error: MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): Account, original object: User: []
Error is in expression '{!insertUserWithRole}' in component <apex:commandButton> in page futureexample1: Class.futureexample1.insertUserWithRole: line 14, column 1

An unexpected error has occurred. Your development organization has been notified.



Apex:code 
public class futureexample1 {
    @future

    public static void insertUserWithRole() 
    {

        Profile p = [SELECT Id FROM Profile WHERE Name='Contract Manager'];
        UserRole r = [SELECT Id FROM UserRole WHERE Name='COO'];
        // Create new user with a non-null user role ID 
        User u = new User(alias = 'ramu', email='prasanthssn@gmail.com', emailencodingkey='UTF-8', lastname='Yugandhar main',  languagelocalekey='en_US',  localesidkey='en_US', profileid = p.Id, userroleid = r.Id, timezonesidkey='America/Los_Angeles', username='saiprasanth1@gmail.com');
        insert u;
        
        account a1=new account(name='sai');
        insert a1;
    }
}

Visualforce page:-
  
<apex:page controller="futureexample1">
<apex:form>

<apex:commandbutton value="create user" action="{!insertUserWithRole}" />

</apex:form>
</apex:page>

 
Amit Chaudhary 8Amit Chaudhary 8
Hi,

You are getting mixed DML issue because same time you are creating user object and Account object records.
Please try below code:- 
public class futureexample1 {

   public void insertUserWithRole() 
    {
        account a1=new account(name='sai');
        insert a1;
		
		createUser();
    }
   @future
   public static void createUser() 
   {
        Profile p = [SELECT Id FROM Profile WHERE Name='Contract Manager'];
        UserRole r = [SELECT Id FROM UserRole WHERE Name='COO'];
        // Create new user with a non-null user role ID 
        User u = new User(alias = 'ramu', email='prasanthssn@gmail.com', emailencodingkey='UTF-8', lastname='Yugandhar main',  languagelocalekey='en_US',  localesidkey='en_US', profileid = p.Id, userroleid = r.Id, timezonesidkey='America/Los_Angeles', username='saiprasanth1@gmail.com');
        insert u;
	
   }	

}

Please mark this as solution if this will help you.

Thanks,
Amit Chaudhary
prasanth puvvada 4prasanth puvvada 4

Amith, if there are 30 methods in a mixed dml, then we have to use "@future" for every method ?
Amit Chaudhary 8Amit Chaudhary 8


NOTE :-
1) Methods with the future annotation must be static methods
2) can only return a void type
3) The specified parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types
4) Methods with the future annotation cannot take sObjects or objects as arguments.
5) You can invoke future methods the same way you invoke any other method. However, a future method can’t invoke another future method
6) No more than 50 method calls per Apex invocation
7) Asynchronous calls, such as @future or executeBatch, called in a startTest, stopTest block, do not count against your limits for the number of queued jobs
8) The maximum number of future method invocations per a 24-hour period is 250,000 or the number of user licenses in your organization multiplied by 200, whichever is greater
9) To test methods defined with the future annotation, call the class containing the method in a startTest(), stopTest() code block. All asynchronous calls made after the startTest method are collected by the system. When stopTest is executed, all asynchronous processes are run synchronously

IMP:-
The reason why sObjects can’t be passed as arguments to future methods is because the sObject might change between the time you call the method and the time it executes. In this case, the future method will get the old sObject values and might overwrite them.  To work with sObjects that already exist in the database, pass the sObject ID instead (or collection of IDs) and use the ID to perform a query for the most up-to-date record. The following example shows how to do so with a list of IDs

I hope above solution will help you.

Please mark the best solution if you this will help