# Field Set Grid

GridMate provides a lightning grid component **GM -  FieldSet Grid** to display list of records with advanced features and bypass Salesforce standard UI limitations like the number of columns, number rows and displaying parent fields without writing formulas. 

In this tutorial, we will create a grid of contacts using **GM - FieldSet Grid** to bypass the Account Contact Relationship. With this grid, we will get an instant access to the contact records. 

1. Open the contact object in the object manager.
2. Add a FieldSet (**GM *****ACR FieldSet***) with the right fields to display including parent fields.
3. Go to an account record and edit the page in the app builder.
4. From the components list, drag and drop the component **GM - FieldSet Grid**.
5. The grid component is now ready for configuration in the Lightning App Builder.
6. The property values can be configured to tailor the data grid to the needs of the end-user.
7. To perform a quick configuration, populate required property values: 
   * Related Object Name : ***Contact***
   * FieldSet Name : **GM\_*****ACR\_FieldSet***
   * Custom Label : ***Contacts***
   * Row Limit : **100**
   * Page Size : **50**
   * Grid Height : **480**
   * Filter : **`{"Id":{"operator":"in","value":"SELECT ContactId FROM AccountContactRelation WHERE AccountId=$$recordId$"}}`**
   * Search Fields : **FirstName,LastName,Title**
   * Wildcard Search : **Checked**
   * Show Border : ***Checked***
   * Show Column Border : ***Checked***

Below is a step by step tutorial to configure the **GM - FieldSet Grid** component..

{% embed url="<https://youtu.be/uRVs0UP7Uas>" %}
**GM - FieldSet Grid**
{% endembed %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gridmate.io/product-tour/field-set-grid.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.