Charting Your Business' Course With GridBuddy's New Charts


Charting Your Business' Course With GridBuddy's New Charts

Posted by AppBuddy on Dec 4, 2015 10:21:20 AM | Share

pac_man_pie_chart.jpgCharts have come to GridBuddy! Launch the confetti and cue the brass band!

In all seriousness, the latest version of GridBuddy adds one of our most-requested features: the ability to embed a chart into any grid. But it's more than just that.

Let's take a quick look at the new functionality, and then cover a couple use cases you might not have thought about.

GridBuddy's Charts come in a few flavors: bar, line and donut. They're easy to configure, and once set up, they always directly reflect the data in your grid. Any changes you make to your grid will directly be updated in the chart instantly. And I mean ANY changes. 

Applying a user filter? The chart gets updated.



Applying a filter to a field on the fly? The chart gets updated.



Updating the data inline and saving? The chart gets updated.


Wait wait wait. What was that?! Is that... the chart updating itself BEFORE hitting save? So you can tweak your data, see how it affects your data in real-time on a CHART, and then revert as if nothing happened? Or, of course, commit your changes to as many records as you want?

Salesforce Wave, eat your heart out.

So what can YOU use GridBuddy's new charts for? We've got use cases! Who doesn't love use cases?!



This is a fairly popular request, and while giving your execs the ability to visualize their pipeline is a crucial element to success, it can also be put on grids to give managers and salespeople an idea of where the funnel stands at any given moment. Never underestimate the power of giving your users visibility into what's going on! And not only will you have the ability to edit your opportunities right from the grid, making this a truly actionable report, but you can make revertable changes to see how they directly affect your pipeline!

Let's take a quick look at the setup and the result. You'll need to create a Grid on the Opportunity object and choose your fields. Keep in mind you must have the fields you're going to be charting in your Grid. For a pipeline, you'll want Stage and Amount, at the very least.pipeline2.png

Now scroll down below the fields, and lo, there is a new Configure Chart section! Bar Charts are the recommended format for a pipeline, since they can show each stage easily, but you could use Donut if you are so inclined. Line Charts are more for data based on, well, dates.

Here, set the X-Axis to Opportunity.Stage and the Y-Axis to Opportunity.Amount. The X and Y axis fields are designed to work with specific types of data, and it's best suited to having numbers and currency in the Y-Axis. 


Hit Save and take a look at your new chart! Beautiful.pipeline1.png



Here's a great use case for Support. Leadership always wants to know how well your help desk is performing, and a key metric for this is how many cases are closed each day.

But why do this in a grid instead of a report? Cases are one of the objects that often needs attention AFTER a Closed status has been achieved: cases need to be categorized after the true solution has been ascertained, solutions or knowledge articles need to be written, and employee performance needs to be assessed. By putting these options in a Grid, you can edit them all at once, and have the chart to show your team's performance right in-line.

Let's set it up!


Because we're working with dates, a Line Chart is recommended. We're going to be working with the Closed Date, so make sure it's a column in your Grid.

Set the X-Axis to Case.Closed Date, and the Y-Axis will not be a field at all; instead set it to Case Record Count. This will count the number of cases for each Closed Date. Hit Save and...



I recommend setting this up with a date filter on the next configuration page, showing something like the last 2 weeks. If you don't know how to set this in the filter, use LAST_N_WEEKS:and change the last n to the number of weeks you're looking for. For example, the last 2 weeks would be LAST_N_WEEKS:2You can find more details on how to do similar things in our documentation.

Stay tuned for more use cases to come!

Install a Free GridBuddy Trial Now


Subscribe To The AppBuddy Blog

Or Leave A Comment


Stay Connected

Related Posts

Popular Posts

New Call-to-action