Skip to main content

Five things to do while writing an apex code to prevent pulling your hair out later.

A new intern joined the team excited to learn about Salesforce. She had a little Java background and thought that Salesforce was very easy compared to Java. In her eagerness, she wrote a 20 lines of code to prove her skills and grasp on Salesforce. The problem was, the code could be written in just 3 lines.

When you are coding on Salesforce, you have to keep in mind the following things:

i) If you can save some lines of code, save it, you can use those lines later. 
If you can write a code in 5 lines, don't waste a 6th one. That one line you saved could be the difference between spending a weekend in office optimizing the code or going to a party at the weekend.

ii) Write like the code will run forever.
Yes, your Sales team has taken in writing that there will only be three records in the system. Yes, you have written a good code for that. But when you are dealing with Salesforce, remember that data is going to increase over a period of time. Today you may be processing a 100 records but there will be a time when you might have to process 1000 or 100000. That period might be beyond your warranty support but it is going to come. You cannot write a prophecy about the day your code broke. Bulkify your code to handle as much data as you can. Put a check if the data is beyond your limit and print a decent, good error message for the future developer to understand what is wrong.

iii) Dread the governor limits
You may hate them, you may love them but you cannot ignore them. Salesforce governor limits are the harsh reality of this world, just like it will rain when you forget your raincoat at home. The governor limit are going to show their face just when you are about to close your day. Write a code to avoid the limits. Have you heard of a developer who wrote such an efficient code that no Governor limit was broken? Neither have I. But you can try to be as close as possible to the legend.

iv) SOQL/DML should not be allowed to enter a FOR loop
This rule is Salesforce 101. No DML or SOQL statement should be inside for loop, even if you are running the loop for only two records.

for(Contact c: ContactList){
//THIS IS A NO NO NO
account a = [Select id,name from Account where id=:c.accountid];
c.name=c.name+a.name;
//THIS IS A EVEN BIGGER NO
update c;  
}

The code written above is a recipe for disaster. Instead the same code can be optimized as:

for(Contact c: ContactList){
accountSet.add(c.accountid);
}
//Whuuu huuu not inside any loop
Map<id,Account> accountMap = new Map<id,Account>([Select id,name from Account where id=: accountSet]);
for(Contact c: ContactList){
//Like they say in treasure hunt movies, a map comes in handy.
c.name=c.name+ accountMap.get(c.accountid).name;
}
update ContactList;

v) Use Collections Set, Map wherever possible
If in your code you have to loop inside a loop, make sure to use a map instead of a list for the inner loop. When we use a map, it is easier to fetch data and will save you a lot of time. Using map also helps speed up the code.

for(Contact c: ContactList){
for(account a: accountList){
if(c.accountid==a.id){
//do something awesome
}
}
}

This code is good enough but can be optimized even more like this

for(Contact c: ContactList){
if(c.accountid==accountMap.get(c.accountid)){
//do something awesome
}
}


These are five simple things can will make your life easier. Being a Salesforce developer is a great honor, use it wisely. Use it fairly.

Comments

  1. Hello Sid
    I would like to know if Java, HTML, XML,Jquery etc are important to learn before trying to code in salesforce Apex?

    What if a person with no knowledge of programming back ground would like to move to salesforce and want to advance as a developer?

    Do let me know what you think.
    Thank you for the patience.

    ReplyDelete
    Replies
    1. Hi DarleneFerminaEusebia,
      Ideally Java and XML is not necessary to learn apex. Having a prior experience of Java helps grasp things much better than otherwise. If you have no programming background, you can move into salesforce. Learning apex as your first language is rare but not unheard of.
      However, remember, Salesforce or otherwise having knowledge of HTML and XML is necessary for anything you do in any language or code.

      Delete
  2. Hello Sid,
    Great site for Salesforce, kudos..!
    I am jumping into salesforce as a developer , my background is JAVA/j2EE, so can you please guide me, how much time i might require to don the salesforce platform and how apex and visualforce are different from Java. I am planning to take course in salesforce also. so kindly please give me initial advise to start as a developer in salesforce .
    Thanks in advance.

    ReplyDelete

Post a Comment

Popular Post

The unofficial guide to become a Certified Salesforce Administrator (ADM 201)

In my attempt at maximum certifications in 60 days, I completed Salesforce Certified Administrator exam on February 11th 2013 So you have decided to ramp up your career and take certifications in your hand. Good choice. It is also likely that this is the first time you have heard of Salesforce, certification and since your company has a vision of you completing the certification you have decided to do it. At this stage it is likely that, You have done extensive googling. You have received countless brain-dumps. And you have received plenty of advise from different types of users which ranges from Admin certification is easier than making coffee to Admin certification is tougher than building a rocket-ship to fly off to the moon. The purpose of this guide is to give you a clear understanding of what to expect when you are expected to become Certified Salesforce Administrator. To bring sense to all the things you have seen so far and to clearly explain what to do and what

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag. For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag <apex: page renderAs='pdf'> This will render the entire page as PDF. Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media . Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the p

The Basics of writing a Apex Trigger

One of the most important and common asked question on Forums and everywhere is how do I write a trigger. Coding in Apex Trigger is like going to a dentist for a root canal, you keep dreading the moment until you realize it is actually not going to hurt you. If you plan to write an Apex Trigger this quick guide will help you doing so. The first and foremost rule in writing a trigger is to remember the oldest suggestion given to the most comprehensive Hitchhikers Guide to Galaxy, ' Don't Panic. ' Writing a trigger is not a rocket science, in-fact we should thank the team at Salesforce and ForceDotCom for making everything so simple, that anyone can do it. Enough of talk, lets code. So you want to write a trigger. Let us have a glimpse of what we are going to build. The problem statement is as follows Problem:  When the User is entering the Opportunity, check for the Opportunity Amount. If the Opportunity Amount is greater than 50,000. Mark the Parent Account as