You might get this Error fairly frequently when developing complex Apex Triggers. In this article, we will look at the causes and possible solutions to address the issue.

What?

This error message typically means that the Apex Trigger is taking too long to execute. The maximum CPU time for a trigger is 10,000 milliseconds or 10 seconds. Note that the time taken for DML and SOQL operations does not fall into this category. 

Why?

When you get this error, it DOES NOT mean that you have too many DML operations or large SOQL queries. Rather, it means that there is a problem in the way you handle the result of those operations.

Things to check

1. Try using a MAP instead of a LIST. A MAP is always much efficient to use.
2. Try to avoid iterations or FOR loops wherever possible.
3. Check your nested FOR Loops. This is one MAJOR area which consume too much time. Try to minimize the iterations.

Ever faced a situation when you wanted to deploy a bunch of fields or page layouts and the Apex Tests execution would take hours and hours to complete?.

A recent feature 'Quick Deploy' enables you to skip Apex Test execution when you deploy. However, you will have to run the validation which executes test cases.

The feature does reduce the deployment time by half, since traditionally test cases were executed both during 'Validation' and 'Deployment'.

Here's the official release note from Salesforce http://releasenotes.docs.salesforce.com/en-us/spring15/release-notes/rn_quick_deployment_ga.htm. The feature is Generally Available and does not require any activation.

This blog post is an extension of a previous blog post (http://www.forcetree.com/2011/09/radiobutton-in-datatable-in-visualforce.html).

The code below explains the way to retain the RADIO button selection on a Visualforce page.

SCREENSHOT:



Apex Class:


Visualforce Page: