Five Mistakes a Salesforce Developer Should Avoid

Salesforce is a craze in the industry and many companies ranging from start-ups to large organizations have been increasingly utilizing the services of this platform for the myriad benefits provided by it. It provides the ability to build customized business solutions with the help of collaboration, sales, marketing, analytics and service capabilities.

The Salesforce developers face problems and make mistakes while developing codes on a daily basis. For those who can learn from mistakes, the article lists most common mistakes made by Salesforce developers. As a huge number of companies are using this platform for their critical business functions, the demand for Salesforce developers is also on a rise.

Five Deadly Mistakes A Salesforce Developer Should Avoid:

#1. Do Not Hardcode:

Hard coding should be avoided as the apex class cannot be modified in the production environment. If a URL is hardcoded from a report and the changes are migrated to the production environment, the URL stops working with the change in the environment.

#2. Avoid SOQL Errors:

Errors like “System. Limit Exception: Too many SOQL queries: 101”? are common during developing, as the esteemed Governor limit is being crossed. The Governor limit says that a total of 100 SOQL queries can be run in a context and not more than that. As a result, it should be ensured that a total number of less than 100 SOQL should be fired as all the triggers fired are counted in a single call or context. This could be achieved by a altering the code, so that the total SOXL fired is less than 100. The use of future annotation could be made, in which the code is made to run asynchronously. In this case, the context needs to be changed. It should ensured that the SOQL query is not inside the for loop.

#3. Streamline Multiple Triggers on the Same Object:

Multiple triggers on an object with the same event should be avoided as it would cause inconvenience. Multiple triggers can confuse the system, which then becomes unable to recognize the order of execution. Thus, a single trigger on the object with the same event is absolutely necessary.

#4. Make Code Bulky:

A strategy of writing bulky codes should be adopted, as this would help in the long run. For instance, if a code is originally written with a single record and in the future, another developer writes a batch of records to insert the accounts, the trigger would reach the governor limit. This could be avoided by processing the batch of records that invokes the Apex code, as a bulk. The problem is that only one account record is handled as the code explicitly accessed only the first record in the trigger instead of handling all the account records in the trigger. In this case the code should be revised, so that the revised version of the code iterates across the entire Trigger. Now, if the trigger is invoked with either single account or 200 accounts, all the records would be properly processed. 

#5. Follow General Design Guidelines for Application Performance:

Sometimes after designing VisualForce, a very rich UI with splendid images and pop-ups are developed, but when the user starts using this framework, he faces problems operating on it. Thus,some errors of performance impacts could be avoided by following the guidelines enumerated below.

• Pages should be designed around the specific tasks with sensible navigation and workflow between the tasks. Everywhere the DOTS should be connected.

• Pages with functionality and data should never be overloaded. Visual force pages with the unbounded data or huge number of fields, components or rows, has poor performance or ability and hence they risk hitting the governor limits for heap size, view state, total page size and record limits.

• Requests should be pushed back to include the non-essential functionality.

• Always try to push back on requests to include non-essential functionality.

• Prototypes should be built to validate the concerns.

Salesforce developers are in great demand in organizations now and hence to take your career to the zenith of success, become a certified Salesforce developer by passing some Salesforce certifications.