I have a "wizard" that is basically one VF page with multiple page blocks rendered according to different steps in it. I have a next and back button for each "screen" that changes the rendered variables in the controller. 
When I click on a back button after filling out a form, it clears the previous form. How do I prevent this? I have instantiated a new object and stored values of the fields in the next() method. However, these fields return null in the debugs, despite the fact that when I save on the last screen, the record gets inserted. 

About once in ten times, email to case fails for us with the error message:

The following errors were encountered while processing an incoming email:
 
UNABLE_TO_LOCK_ROW : unable to obtain exclusive access to this record

While I understand why this is happening, I can't seem to be able to find a way around it. Since the incoming email doesn't get stored anywhere when the insert fails, there is no way for me to attempt a reinsert using Apex. (We managed to implement that when new emails come to cases that are closed, as we can insert those emails to the same case and then use that to create a new case.)

Is there any workaround for this? We would really prefer it if we didn't get glaring errors in the email. Can a chatter post be implemented with the details of the incoming email? Any help would be appreciated. Thanks!

I have a "wizard" that is basically one VF page with multiple page blocks rendered according to different steps in it. I have a next and back button for each "screen" that changes the rendered variables in the controller. 
When I click on a back button after filling out a form, it clears the previous form. How do I prevent this? I have instantiated a new object and stored values of the fields in the next() method. However, these fields return null in the debugs, despite the fact that when I save on the last screen, the record gets inserted. 

About once in ten times, email to case fails for us with the error message:

The following errors were encountered while processing an incoming email:
 
UNABLE_TO_LOCK_ROW : unable to obtain exclusive access to this record

While I understand why this is happening, I can't seem to be able to find a way around it. Since the incoming email doesn't get stored anywhere when the insert fails, there is no way for me to attempt a reinsert using Apex. (We managed to implement that when new emails come to cases that are closed, as we can insert those emails to the same case and then use that to create a new case.)

Is there any workaround for this? We would really prefer it if we didn't get glaring errors in the email. Can a chatter post be implemented with the details of the incoming email? Any help would be appreciated. Thanks!

Hi,

We have set up Email to Case functionality. We are getting this error at least once in a day and the case is not opened:

UNABLE_TO_LOCK_ROW : unable to obtain exclusive access to this record

We have gone through this knowledge Article: https://help.salesforce.com/apex/HTViewSolution?urlname=Email-to-Case-error-UNABLE-TO-LOCK-ROW-unable-to-obtain-exclusive-access-to-this-record&language=en_US (https://help.salesforce.com/apex/HTViewSolution?urlname=Email-to-Case-error-UNABLE-TO-LOCK-ROW-unable-to-obtain-exclusive-access-to-this-record&language=en_US)

But, when case is created, we are not updating any parent record of it.

What is the reason of this issue?

Thanks,
Rupali

Hi,

 

Occasionally we seem to have a problem where emails received by Salesforce do not create cases. his causes us a serious issue as requests (orders) from customers will likely be missed. 

 

We receive a warning by email which states: 

"...The following errors were encountered while processing an incoming email: 

UNABLE_TO_LOCK_ROW : unable to obtain exclusive access to this record..."

 

 

What i did for this is:

We have 3 triggers on Case Object, which fires upon case creation for an incoming Email from customers. Put all the code in try catch blocks and write a chatter post in catch block. There by chatter group people will get a chatter post upon any lock error from any trigger. There by we can move that code to batch class and call it in future method. So that, we can remove that lock error.

 

Does my approach solve this problem?

 

Any suggestions would be appreciated?