Salesforce Ninja: An Elite Blog about Salesforce.com

A few days ago I was speaking to a developer friend, he was asked about a Singleton design pattern and he had no idea about. He spoke about how we developers never talk about patterns. And that time it hit me, we developers do not talk about design patterns and algorithms. There are many design patterns available off the shelf, they talk in detail about the problems they can solve. However, in my experience, I have come across and used the following 1. Singleton This is one of the most common and important design pattern to be used. When initiating objects, we need to make sure only one instance of the object is initiated. In a multi-tenant system like Salesforce, it becomes imperative that we do not hog more resources than needed Lets look at an example trigger AccountTrigger on Account (before insert, before update) { for(Account record : Trigger.new){ AccountMasterRecordType rt = new AccountMasterRecordType (); .... } } public class AccountMa...

In December 2012 I attended a Salesforce Foundation roadshow in Bangalore. Many Salesforce foundation costumers had gathered at the venue to listen to salesforce or share their stories. One common complaint that was shared was what to do once I get the salesforce license. A little variation to the complain was, there was xyz who introduced us to salesforce but now he has moved on or has no time for implementation. There were a lot of technical queries on building an app on Salesforce. If you are a non-profit and cannot afford to hire a consultant to configure Salesforce for your needs, you can always use the DIY approach. Building a basic data collection app on Force.com is very easy and takes hardly a week. Compiling here is the collection of some implementation questions if you are building a Force.com app for yourself without any prior knowledge. What is salesforce? What is force.com To begin with, the very first thing you need to understand is the difference betw...