Sticking with Standard Functionality - Yet Another Example
“But why do I want to stay with standard functionality? It does not give me exactly what I want.”
This is a question/statement that comes up often when providing a solution on the Force.com platform. The out-of-the-box functionality may meet almost all of the requirements, but there are some requirements that will require leaving the standard functionality and moving into completely new custom development.
It is at this point in the process where we all must recognize the fork in the road. Should we follow Robert Frost’s advice?
Two roads diverged in a wood, and I—
I took the one less traveled by,
And that has made all the difference.
If we follow the road less traveled by and start developing custom code and leaving the standard functionality behind, we must recognize the risk in doing that. One might respond that the current standard functionality simply does not meet my needs, so why should I stick with it?
The reason why is that you are paying license costs that are going into the development of new and improved features on the existing standard functionality. Salesforce is not going to innovate on your custom code. Salesforce is going to innovate around its core product supporting Sales and Marketing by extending it to do more and more awesome features with each release.
Just today I tweeted about the new ‘Sales Reach’ solution that was recently released. Here is the link that I tweeted about. If you had implemented your own new custom Lead and Campaign objects you would not be able to leverage this new functionality that is basically given to you for free just because you are paying for your licenses.
There are times in life to follow Robert Frost’s advice to take the road less traveled by. But with Salesforce let’s try to stay close to the main road. :)