Skip to main content

A Handbook to help you with DEV 401

Every-time I am in a training room, there is a single most query asked by almost everyone, is there a book on Salesforce. The answer is very difficult to answer for multiple reasons. One, Salesforce is always on steroids, meaning it changes a lot in too shorter time, the changes are good and excellent, however it poses a trouble for book publishers. Any book project takes at-least 8 to 9 months to complete and going by that standard, Salesforce would be already changed thrice in that period.

Yet, still books are there and some very good books are available on Salesforce. One small effort in the books was Force.com Developer Certification Handbook (DEV401) written by me along with the great team of Packt Publishers and even greater reviewers Ankit Arora, Matthew Botos and John Rotenstein 

The book is primarily aimed at certification and will be helpful in easing out the biggest trouble, where to start. Its a simple marker which says, start here. With the help of the book you can begin preparing for Force.com Developer certification. Its helps you understand the concepts in simple, clear manner with examples and screen shots. This book was written based on the notes I collected during the DEV 401 certification.


  • Simple and to-the-point examples that can be tried out in your developer org
  • A practical book for professionals who want to take the DEV 401 Certification exam
  • Sample questions for every topic in an exam pattern to help you prepare better, and tips to get things started
  • Full of screen-shots, diagrams, and clear step-by-step instructions that cover the entire syllabus for the exam

You can read the Sample Chapter, Table of Contents on the page of the book. The book also answers some of the FAQs about the DEV exam which arise while preparing for it. 

If there are DEV 401 related queries you can post a comment below, ill try to answer them as best as I can. 

All the best for the exam. May the Force be with you. 

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

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…