.svg)
Dynamic Record Card
The details you need - right where you need them.
It’s time to stop making users chase context across tabs. With the Dynamic Record Card, record-specific details appear instantly the moment a row is selected in any GridMate master grid - List View, Related List, or FieldSet. It’s the easiest way to bring a master-detail interface to life, all within a single pane of glass.
Context, without compromise.
Stay in sync with your grid.
This component listens to any connected GridMate grid and automatically displays the record details of the selected row. It’s a seamless, live update experience that keeps users focused and informed - without switching tabs.
Configure what matters.
You choose which fields and layouts to show, so users always see the most relevant information. Whether it's summary fields, long text areas, or custom lookups, the layout is completely in your control.
Designed for clarity. Built for speed.
From sales overviews to service cases, display detailed insights alongside your main grid. Save users from context-switching by embedding the full picture directly into their workflow.
See the Dynamic Record Card
in action!
Make the leap from standard to standout.
Unlock the full potential of master-detail experiences in Salesforce - no Visualforce, no navigation compromises.
Frequently Asked Questions
Are GridMate grids supported on the Salesforce Mobile App?
Absolutely! Here's what we recommend:
- Duplicate the existing grid in your Salesforce Org. This duplicated grid should be specifically configured for access by mobile users.
- Set a unique name that clearly identifies it as a mobile-friendly grid.
There are two key considerations when it comes to accessing grids on mobile devices:
Set the width for each column – This allows users to scroll horizontally.
Refer to column width specification here.
Set the height of the grid – This enables vertical scrolling.
Refer to the height specification here.
Note: We will be introducing a new component called ‘Mobile Grids’, which will be optimized specifically for mobile phones.
Do I need technical experience with GridMate?
Not at all. We’ll equip you with everything you need - from product overviews to sales guides and demo walkthroughs.
Does GridMate store or process data outside of my Salesforce Org?
No. GridMate is a native Salesforce package. We do not store or process any data outside of Salesforce. All our components are metadata-driven and built on Salesforce APIs.
If I install the GridMate package for all users, do I need to assign GridMate permission set(s) for each new user going forward?
Yes. The GridMate permission sets grant access to Apex classes, Visualforce pages, objects, and other components. When you first install the package and choose “Install for All Users,” these settings are automatically applied to existing users.
However, when new users are added later, you must manually assign the appropriate permission set. GridMate access is managed entirely through permissions, so assigning the permission set is highly recommended.
GridMate User
This is the base permission set required for any user who needs access to GridMate components (except User Grids). It includes object and field access, as well as Apex classes. Each GridMate user should have this permission.
GridMate Advanced User
This permission set is used to grant access to User Grids. Its purpose is for advanced users who require permission to create their own grids.
GridMate Admin
This permission set is used for Business Analysts to have access to the config wizard, inline configuration and SOQL Preview buttons. It's applicable only if they don't have access to the setup.
GridMate Cockpit User
The GridMate Cockpit User permission set allows users to manage all GridMate settings in one place - including grid-level field access, action controls, and component visibility. It grants access to the Cockpit tab and its features.
Can I prevent my users from creating, editing, or deleting filters?
Yes. By default, GridMate provides a permission set called GridMate User to easily grant access to package components, including object settings, Apex classes, and more.
With this permission set assigned, users can create, edit, and delete end-user filters - provided this option is enabled on the grid.
However, in certain scenarios, admins may want to restrict these actions. Rather than duplicating and manually adjusting the permission set, we recommend using the Muted Permission Set feature in Salesforce.
1. Create a Permission Set Group that includes the GridMate User permission set.
2. Add a Muted Permission Set to that group by creating a new Muted Permission Set.
3. In the Muted Permission Set, mute Create/Update/Delete access for the DataGrid Preferences object.
4. Finally, remove all direct assignments of the GridMate User permission set from users. Instead, assign them the new Permission Set Group.
This approach ensures your users retain access to essential GridMate components while preventing them from modifying filter settings.
Please refer to Salesforce documentation for Muted Permissions.
Got any more
questions?
