[SalesForce] Failing to save an object from a constructor of a standard controller class

We have a use case in which we wish to modify/save fields in the Lead objects from the constructor of a standard controller class.

Changing the fields goes well, but trying to modify the lead using "Standard Controller->Save()" method, or using "Upsert" fails due to "System.LimitException: DML currently not allowed"

I also tried to use @Future or schedule a job to do that change, but unfortunately @Future is not allowed in constructor and scheduling a job also fails; I can't find any trace for the job and I don't get any exceptions.

Appreciate your advice

Best Answer

You can't perform DML operations in a constructor, you can however use the VF page action function. This will allow you to perform any logic or DML operations and it is invoked before the page is rendered.

You use the action method in the tage like this

<apex:page controller="myController" action="{!myMethod}">

and in the controller

public void myMethod{
    //your logic and code here
}

You can learn more about the Visualforce page action method here

http://www.salesforce.com/us/developer/docs/pages/index_Left.htm

Related Solutions

[SalesForce] Schedule apex class to run every minute as there can only be 5 batch jobs

You could also create you own custom apex batch queue. I did this myself and created the GitHub project SObject Work Queue which had the following design goals:

Must prevent Max 5 batch in parallel limit - We should never run into this limit with work that is processed over the queue.
The queue needs to be so generic that "work" on any type of database object needs to be enqueued.
Any type of modification of database objects need to be possible. This should be transparently handled by the queue.
Provides better error diagnostics like Batch. Knows last successful Id, full stacktrace and sends email to developers.
Secures data integrity like Batch or better. Failures should not leave data in inconsistent state or user of the infrastructure should be able to handle them.
Optimistic locking : Instead of locking all many records we do not to process work on Ids that have other work already scheduled.
Work that can be run synchronously, should not be queued and processed asynch.

Maybe you want to check if that could be used in you case or collaborate on GitHub to extend it for your purpose.

Here is an overview sequence diagram that shows how work is defined, enqueued and processed in such a custom Apex Queue:

enter image description here

[SalesForce] How to get the object reference from a standard controller save()

If you're trying to get the Id, you should just go back to stdController.

Id issueId = stdController.getId();

I also very much doubt that this is getting the value from the query string, as the documentation suggests. I'm almost positive I've used this method in pages with no query params and it works. I'll try to test later and amend my answer based on those results.

Best Answer

Related Solutions

[SalesForce] Schedule apex class to run every minute as there can only be 5 batch jobs

[SalesForce] How to get the object reference from a standard controller save()

Related Topic