Skip to main content

Displaying Aggregate result on Visualforce using SOQL

There are some who jump out of bath-tub nearly naked when they are highly excited, fortunately I am not one of them, but when I saw the Aggregate functions in Spring 10 release, I was nearly in tears, ok, thats too dramatic but Aggregate functions giving a very beautiful meaning to data altogether.

For those of you who knew SQL you obviously know what aggregate functions are and how they beautify your code. Those who do not know, aggregate functions help you aggregate the date based on certain field.

Say for example, you want to show the count and Opportunities created on a day, you can aggregate them using SOQL.

AggregateResult[] groupedResults  = [SELECT Name, Count(Amount) FROM Opportunity GROUP BY CreatedDate];

So how do we display it on Visualforce:

Just iterate on the AggregateResults and get elements one by one.

for (AggregateResult ar : groupedResults)  {
    System.debug('Created Date' + ar.get('CreatedDate'));
}

A few pointers for debugging:

1. Always use API version 18.0+ while using Aggregate Functions. If you are eclipse, you might want to update it. And frankly if you are still using older version of eclipse, my mind wants to scream and ask you...why?

2. If you are Aggregating using a relationship e.g., Object1__r.object2__c in your SOQL, while fetching from AggregateResults you only need Object2__c, ar.get('Object2__c') I am not really sure why, because I found no documentation supporting this, but it worked for me in the code.


Thats it for today,
Happy Coding,
 How does a project get to be a year late?... One day at a time.
-- Fred Brooks


P.s. Did you see the new symbol I created for the site? Star wars and cloud in one icon. :D

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…