Dynamic Reporting via Reporting API

A couple of weeks ago, I was in a huge dilemma. I had to showcase a dashboard with multiple reports spanning across Cases, Contacts and Accounts on my portal landing page, each one with a different dashboard component. Additionally, the displayed reports should only contain the graphical part and exclude all the other irrelevant details. Since this facility is not available in Salesforce, like most developers, I instantly thought of using ‘iframes’ in my Visualforce page. But alas, that proved to be quite an issue ridden solution! Visualforce charting was also another alternative I considered and then discarded, for it would have been a time-consuming task. That’s when Reporting API, with its effective UI and quick implementation lifecycle came to my life as my savior.

Reporting API is built on REST API

Salesforce introduced a limited feature pilot of Analytics API in Summer ’13 and the Analytics REST API was made generally available from Winter ’14. The Analytics API allows us to integrate Salesforce report data into apps programmatically and has several resources that let you query metadata, and record details. This API is based on REST, which means that all the information that a user needs is generated real-time. The Reporting API is part of all the available REST APIs generated by Salesforce.

Reporting API: Making our lives better

Salesforce has provide multiple ways to display charts, namely Standard Reports and Visualforce Charting. However, Visualforce Charting requires controllers and test classes, and uses JavaScript to draw the charts. Standard Reports have their own set of drawbacks, their rigid format being a primary road-block.

On other hand, Reporting API has abundant advantages, including real time display of data. The <analytics: reportChart> tag, along with a Report Id will display the report chart of the associated report. Additionally, the users have an option to run reports synchronously or asynchronously.

Most importantly, users can get a Single-View representation for multiple objects.

Some Useful Attributes of <analytics: reportChart>

• showRefreshButton: The need for accessing the report in order to refresh it whenever new records are added is eliminated through the use of this attribute
• cacheResults: Users can choose to display information from the cached date for multiple report runs within 24 hours
• filter: In order to get the API name of the field that we need to filter and the operator, we need to make a describe request via the Analytics REST API. For example, I used the Status field of the Case object in my filter condition, the details of which were retrieved as shown below.

Reporting API: a Walkthrough

Creation of a Report

Note: 

• Reporting API supports Summary and Matrix reports. Apply filter criteria and add field for column grouping, if needed, and click on Add Chart.
• Use the following tag in a Visualforce page: <analytics: reportChart cacheResults=”false” size=”small” reportId=”00O90000007fzQc”> where reportId will be the ID of the report you created.

This will display the report chart associated with your report in the page, thus allowing you to create a custom dashboard.

Done! Our Visualforce page is displayed with report charts, as shown below:

Disadvantages

Reporting API comes with its own share of drawbacks. I have listed a few of them below:

1. Reporting API supports only Summary and Matrix reports type
2. You can pass only the Report IDs as the parameter, and not the Dashboard IDs

Its disadvantages notwithstanding, Reporting API has proved great for implementations with strict time constraints, which require an effective UI for displaying reports dynamically in Salesforce. Give it a try and let me know how was your experience.