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 posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…