FAQ

How do I contact support?

You can reach out to us by email support@gridmate.io. 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 👇

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 👇

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 👇

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

Last updated