❓FAQ

How do I contact support?

You can reach out to us by email [e-mail]. For any technical assistance, please grant access to the your salesforce organisation and share:

• The salesforce organisation Id (Org Id)

• The page link(s) related to the issue

• The steps to reproduce the issue

Does GridMate supports dependant PickLists?

Yes. GridMate supports dependent PickLists and dependant record types PickLists

Does GridMate support inline editing for multiple record types?

Yes. GridMate support inline editing for multiple record types at the same time. Dependant PickLists will be respected as well.

Does GridMate store or process data outside of my Salesforce Org?

No. GridMate is native Salesforce package. We don't store or process any data outside of Salesforce. All our components are metadata driven and sit on Salesforce API(s).

Does GridMate support Salesforce Classic?

Yes. GridMate has been successfully deployed on Salesforce Classic. See below 👇

GridMate on Salesforce Classic

Step by step guide is available here 👉 Salesforce Classic deployment

Does GridMate run on Tablet?

Yes, GridMate has been successfully deployed on iPad. See below 👇

GridMate on Salesforce1

Shall we grant GridMate license to each user?

No, GridMate license should be granted only to the relevant users. GridMate components can be combined with standard components using visibility conditions in the Lightning App Builder.

We suggest to create a custom permission, assign it to the licensed users and finally use this permission to show or hide the component from the Lightning App Builder. See below 👇

GridMate Component Visibility

Can I prevent my users creating/editing/deleting filters?

Yes. By default GridMate provides a Permission Set GridMate User to easily grant access to the package components including object settings, apex classes...etc.

With this permission, the user will be able to create, edit and delete end user filter when this option is enable on a grid.

For some scenarios, admins want to prevent those of transaction. Instead of duplicating this permission and adjust it, we suggest using Muted Permission feature:

• Create a Permission Set Group that includes GridMate User

• Add a Muted Permission Set to mute the actions by creating a new Muted Permission Set

• Mute Create/Update/Delete for DataGrid Preferences object

• Finally remove all the assignments from GridMate User and use the new Permission Set Group instead.

Please refer to Salesforce documentation for Muted Permission:

https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_muting.htm&type=5

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 the apex classes, visualforce pages and objects, etc. When you install the package for the first time, all these settings get assigned to all existing users if you check ‘install for all users’.

You have to assign the permission set if you enroll a new user. We maintain all the access to GridMate components through permissions. So assigning the permission set is highly recommended.

GridMate User

This permission set is the base for any users who need access to GridMate components, except for User Grids. It includes Objects, Fields Access and 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 are required 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 relevant only if they don't have access to the setup.

GridMate Cockpit User

The GridMate Cockpit User was introduced to manage GridMate settings in one place including field access at the grid level, actions and component access, etc. This permission set grants access to this tab and all the included features.

Actions 👇	GridMate User	GridMate Admin User	GridMate Advanced User	GridMate Cockpit User
View and Edit Components
Configure Components
View and Edit User Grids
Cockpit Access + Adoption Dashboard

Are GridMate’s Grids supported on the Salesforce Mobile Application too?

Absolutely! Here's what we recommend:

1. Duplicate the existing grid on your Salesforce Org. This duplicated grid would need to be configured for access to mobile users.

2. Set a unique name that can be identified by users as a 'mobile' friendly grid.

There are 2 things essentially to take into account when it comes to accessing grids on mobile devices:

• Set the width for each columns (with this setup we can scroll horizontally) - https://docs.gridmate.io/advanced-guides/grid-configuration#column-style-property
• Set the height of the grid to scroll vertically - https://docs.gridmate.io/package-reference/components-library/gm-relatedlist-grid#specification

Note: We will be introducing a new component called ‘Mobile Grids’ which will be optimized for mobile phones.

Can the record Id be passed to GridMate component on Experience Cloud?

Yes, GridMate can support this by defining the recordId property as {!recordId}.

Does GridMate support archived data filtering?

Yes, GridMate supports archived data through the implementation of an admin filter containing the following JSON String:

{
   "gmpkg__allRows":true
} 

Below is a smart grid example implemented on the GM - Field Set Grid