> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/troubleshooting/faq.md).

# FAQ

Answers on support, licenses, permission sets, mobile, archived data and grids that load empty.

<details>

<summary>How do I contact support?</summary>

You can reach out to us by email <mark style="color:blue;"><support@gridmate.io></mark>. For any technical assistance, please grant access to your Salesforce org and share:

* The Salesforce organisation Id (Org Id)
* The page link(s) related to the issue
* The steps to reproduce the issue

</details>

<details>

<summary><strong>When installing the GridMate package, do I Install for all Users, Admins Only or Selected Users?</strong></summary>

We recommend installing for Admins only. Users that require (view/edit) access to GridMate components will require a license and permission sets assigned.

</details>

<details>

<summary><strong>Does GridMate support dependent PickLists?</strong></summary>

**Yes.** GridMate supports dependent PickLists and dependent record types PickLists.

</details>

<details>

<summary><strong>Does GridMate support inline editing for multiple record types?</strong></summary>

**Yes.** GridMate supports inline editing for multiple record types at the same time. Dependent PickLists will be respected as well.

</details>

<details>

<summary><strong>Does GridMate store or process data outside of my Salesforce Org?</strong></summary>

**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).

</details>

<details>

<summary><strong>Does GridMate support Salesforce Classic?</strong></summary>

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

![GridMate on Salesforce Classic](https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEsSbGy_U_OhthKUpxu%2F-MFF8hfcrYQjwiQf8ApK%2F-MFFBPu3XgYQMxdQ9fob%2FScreenshot%202020-08-21%20at%2010.45.17.png?alt=media\&token=2ca3a133-ab3d-4232-9f01-d54a7baffe5f)

Step by step guide is available here 👉 [Salesforce Classic deployment](https://docs.gridmate.io/advanced-guides/grid-setup/salesforce-classic-deployment.md)

</details>

<details>

<summary><strong>Does GridMate run on Tablet?</strong></summary>

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

![GridMate on iPad](https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEsSbGy_U_OhthKUpxu%2F-MFF8hfcrYQjwiQf8ApK%2F-MFFAB5Ti0Sm3Pxz77s9%2FScreenshot%202020-08-21%20at%2010.39.38.png?alt=media\&token=cafb619f-aeba-4c9f-a5fb-6c8122a3a256)

</details>

<details>

<summary><strong>Should we grant GridMate license to each user?</strong></summary>

**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](https://help.salesforce.com/articleView?id=sf.lightning_page_components_visibility.htm\&type=5).

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](https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEsSbGy_U_OhthKUpxu%2F-MRoyXtpsRDPAvCQ_f4E%2F-MRpYnpaqPJSg4kLhv30%2FScreenshot%202021-01-24%20at%2019.00.57.png?alt=media\&token=61a0ca2f-5cbb-480e-a35f-620d4d98810f)

</details>

<details>

<summary><strong>Can I prevent my users creating/editing/deleting filters?</strong></summary>

**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 users from creating, editing or deleting filters. Instead of duplicating this permission and adjust it, we suggest using **Muted Permission** feature:

* Create a Permission Set Group that includes GridMate User

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2Fnc1wOyRuZ6E9tqBrF1FH%2FScreenshot%202023-03-17%20at%2014.59.54.png?alt=media&amp;token=44313a6c-d758-4412-ae64-147fe2fe46ee" alt=""><figcaption></figcaption></figure>

* Create a new Muted Permission Set to mute the actions

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2F3rcTnzv2jUgw5iAsUlum%2FScreenshot%202023-03-17%20at%2015.17.55.png?alt=media&amp;token=892b4897-efea-4674-9664-adca81b2aaea" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FUicfG4DFyp3vM87MDs0U%2FScreenshot%202023-03-17%20at%2015.19.08.png?alt=media&amp;token=7fcde2ed-5ea1-43f7-ad1d-f717551b0a22" alt=""><figcaption></figcaption></figure>

* Mute Create/Update/Delete for **DataGrid Preferences** object

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2F1VJchim68WgEXfjZkwUG%2FScreenshot%202023-03-17%20at%2015.23.39.png?alt=media&amp;token=cfb38552-2a6b-47b1-909d-e8b449a8932c" alt=""><figcaption></figcaption></figure>

* 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>

</details>

<details>

<summary><strong>If I install the GridMate package for all users, do I need to assign GridMate permission set(s) for each new user going forward?</strong></summary>

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.

<table data-full-width="true"><thead><tr><th width="202">Actions 👇</th><th width="149" data-type="checkbox">GridMate User</th><th width="195" data-type="checkbox">GridMate Admin</th><th width="223" data-type="checkbox">GridMate Advanced User</th><th data-type="checkbox">GridMate Cockpit User</th></tr></thead><tbody><tr><td>View and Edit Components</td><td>true</td><td>false</td><td>false</td><td>false</td></tr><tr><td>Configure Components</td><td>true</td><td>true</td><td>false</td><td>false</td></tr><tr><td>View and Edit User Grids</td><td>false</td><td>false</td><td>true</td><td>false</td></tr><tr><td>Cockpit Access + Adoption Dashboard</td><td>true</td><td>false</td><td>false</td><td>true</td></tr></tbody></table>

</details>

<details>

<summary><strong>Are GridMate’s Grids supported on the Salesforce Mobile Application too?</strong></summary>

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) - [Grid - Advanced Configuration](https://docs.gridmate.io/advanced-guides/grid-setup/grid-configuration.md#column-style-property)
* Set the height of the grid to scroll vertically - [GM - RelatedList Grid](https://docs.gridmate.io/package-reference/components-library/grids/gm-relatedlist-grid.md#specification)

For phones, use the dedicated [GM - Mobile Grid](https://docs.gridmate.io/product-tour/grids/mobile-grid.md) component, which is optimized for mobile.

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FWYhgUuvXwFwW7kDWftyf%2Fscreen-20240605-192804.gif?alt=media&amp;token=16895c9d-6c3e-444b-8196-032db7e680b2" alt="" width="360"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>Can the record Id be passed to GridMate component on Experience Cloud?</strong></summary>

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

</details>

<details>

<summary><strong>Does GridMate support archived data filtering?</strong></summary>

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

```json
{
   "gmpkg__allRows":true
} 
```

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

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FSYJp732LSAxEiYEJfdN9%2Funnamed.png?alt=media&amp;token=407d86cd-82b0-4b02-9276-5eaec5549cdf" alt="" width="471"><figcaption></figcaption></figure>

</details>

<details>

<summary><strong>How can I customize the style of a specific column using a JSON string (e.g., width, alignment, or wrapping)?</strong></summary>

You can override a column’s style by providing a JSON string that maps each column to a CSS-style value, such as `width:180px;` or `text-align:left`. This is especially useful for customizing the layout of specific columns in your table.

**To set the text wrapping**:

```json
{
    "Name": "cellcontent:wrap"
}
```

**To set the alignment:**

```json
{
    "Amount": "text-align:left"
}
```

**To set the width of a column:**

```json
{
    "Amount": "width:180px;"
}
```

**To set the width of any column:**

```json
{
    "gm__header": "width:120px;"
}
```

</details>

<details>

<summary><strong>Why do my grids (GM - RelatedList Grid, GM - ListView Grid) load with no data and show (0) for my users?</strong></summary>

This happens when the org locks user sessions to an IP address. GridMate can't load grid metadata when **Lock sessions to the IP address from which they originated** is enabled in the **Session Settings**

You may notice:

* The grid header shows **(0)** and the grid body is empty for every user.
* Clearing the browser cache or switching browsers doesn't help.

To fix it:

1. From **Setup**, enter `Session Settings` in the Quick Find box and select **Session Settings**.
2. Uncheck **Lock sessions to the IP address from which they originated**.
3. Click **Save**.
4. Ask your users to log out of Salesforce, log back in and reload the page.

{% hint style="warning" %}
These settings apply to the whole org. Check with your security team before you change them.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gridmate.io/troubleshooting/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
