Skip to main content

Build your own infographics resume using Salesforce reports and dashboard

If you are following our mutual friend, Daryl Shaber on Twitter you have come across the Salesforce Dashboard resume created by me. If you have not seen it, you are welcome to see the original first version and the version 2.1 with some more added features here.

For those who joined in late (I always wanted to say that, ignore if you didn't understand the reference) it happened on one night when I could not sleep. I had experimented with coffee and red bull (I dare you don't do it) and had lost one night of sleep.

I was reading about the modern way of resume building. People were showing off their info-graphic resumes and that is something, I wanted to do. As a Salesforce consultant what was any better way to show off infographic resume than using Salesforce reports and dashboards to do it.

Many people requested that they wanted a similar resume and hence, I have deployed a package on AppExchange. It is a private listing, use this link to access it.



It is a complete unmanaged package and there is no support for it. Its very simple, add your data in the objects and go crazy. I have two sample dashboard inside but Ill request you play with it and built your own resume. To know more about reports and dashboard you can use this link or better google it.



Take a screenshot of the finished dashboard and you can add the header to it. I use Pixlr.com which is a cloud based photo editor to add the header.

If all goes well you will have something similar to this.





All the best
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…