As a team with our customers, we are continually updating lots of records at once. As much as we love Salesforce, sometimes it needs a little help with this and that’s where Gridbuddy comes into play.
Full Disclosure: This is a continuation of an occasional series of apps that we either use and/or have recommended to clients. Some of these amazing ISV’s allow us free access within our own system so that we can understand its functionality and how it can apply to our clients. Our relationship with Gridbuddy goes back many years and if it were a dog, it would be old enough to order its own beer. To that we say, “Cheers!”
What is this Again?
I could talk about the functionality of Gridbuddy, but I think this video does a great job:
Instead of talking directly about features, let me discuss with some internal examples.
Yes, Salesforce has an excellent reporting and analytic tool. There is no reason why not to continue to use that function. Even if you have Salesforce Analytics (Wave) or Tableau, you will probably still work and use the built-in reporting tool. But that’s another blog post.
A key aspect of Gridbuddy is its inherent ability to show detail of not just the parent, but also the children. While it is not a pivot table or matrix, the reporting tool and its summary abilities are not there, but it does have the ability to show good shares of data in an excel file. And if you need the detail, that is helpful, as well.
Ever try to report on a long text area fields? Go and try it in Salesforce reporting. It truncates it! Gridbuddy? Nope. All those fields in all there wondrous glory, all formatted like you left it. Easy-peasy.
Another feature we like is that the export function also breaks apart the children into separate tabs and includes the salesforce ID’s. This makes mass editing and working with data loading tools easier for an admin.
Respect the Record Type
It may seem not a large deal but if you have record types you know that its important to protect the fields and field accessibility layered into our app. While salesforce does a decent job of protecting us when using the standard page layouts, its important that other editors also enforce those rules. Gridbuddy will enforce your record type’s field protections and so even if a user attempts to make a mass edit – the system will stop them from saving.
Thinking WAY Outside the Box
Unfortunately we cannot show a screen shot of this but there was a client that wanted to center their salesforce usage on only Gridbuddy screens. Fortunately it is possible with a some ingenuity to allow your users to do almost all of their day-to-day effort using Gridbuddy. For example:
- Use Visualforce and the Tab function to create a tab for each grid in the sales process.
- Define your grids so that there is a grid for each stage in your opportunity pipeline.
- As Opportunity stages change, the records will naturally flow from one grid to another.
- Consider using workflow actions to record completed call activity records based on information stored as fields on the opportunity.
- Consider creating a call back date field on the opportunity so that each grid is sorted based on a call schedule.
There are so many options to consider for this tool. Again Gridbuddy does a great job of defining their core components but we wanted to highlight some features that are typically not shown in the standard tool.