Skip to main content


Showing posts from 2016

Quick Tips: Some things about Salesforce Validation rules you may not know

What are validation rules? While creating any application, one of the most crucial building block is clean and good data. We do get ability to define required fields on field and page layout level, but there can be complex scenarios where the business rule needs multiple fields to ascertain data quality.  Salesforce provides a very helpful feature called "Validation rule" to ensure administrators/ developers can create custom validation rules on Salesforce objects. These validation rules help ensure that any record being created or updated qualifies to defined business rules. If not, then developers/ administrators can display required error message. Validation rule constitutes of:- Formula - formula to evaluate business rule. If formula evaluates to TRUE, validation error is thrown, else it's considered as validation success Error message - error message to be displayed on validation failure Location - Enables admin/ developer to define location to displa

New Salesforce Book - Apex Design Patterns

  Refer below links to purchase: Packt publications (US) (India) (UK) I'm really excited to share that today my book (co-written with Jitendra Zaa ) has been published. Here are some personal insights A little history This particular topic was always in my head and coming from .Net background and having worked with lots of design patterns in MS development world. I first successfully used Factory design pattern with Apex in 2009, when all my team was scratching their head and (cursing me badly) for "overtly complicating" the code architecture. They were happy with creating 20-30 different VF pages, which I emphasized needs to be designed with the help of 4-5 VF pages, VF components and factory method pattern. Well, we were able to complete the whole stuff in time and deliver it flawlessly. It was then and similar instances later that I realized that a larger faction of Salesforce developers (back then) had very l