> 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/advanced-guides/dynamic-components/grid-dynamic-fieldset-grid.md).

# Grid - Dynamic FieldSet Grid

Show related records of the row selected in a parent grid, without leaving the page.

**GM - Dynamic FieldSet Grid** enhances usability by enabling users to access or view related data within the current context, eliminating the need for navigation. It offers a seamless way to explore associated records or details without switching between screens or pages, reducing the requirement for multiple clicks or page reloads. This streamlines the user experience, boosting productivity.

## Enable dynamic interaction

The **Enable Dynamic Interactions** option allows the component to publish events that can be leveraged by **GM - Dynamic FieldSet Grid**. This component is useful to create dynamic interaction experience on a record page or even on experience cloud.

<figure><img src="https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FV3hulYQs1VOlcyQtXwLe%2FScreenshot%202023-07-14%20at%2015.03.43.png?alt=media&amp;token=faf42fa7-b3b3-4eba-9356-759178f02577" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**GM - Dynamic FieldSet Grid** has the same properties as **GM - FieldSet Grid**. The component should be tied to a parent grid to get refreshed when the user clicks on a specific row. To make the link to a parent grid, the properties below should be defined:

* **Parent Object Name** : The parent object name to listen on,
* **Parent Grid Name :** The parent grid name to listen on. It could be the related list label (**GM - RelatedList Grid**), the field set name (**GM - FieldSet Grid**) or the list view api name (**GM - ListView Grid**).
* **Parent Grid Code :** The data grid code to listen on.
  {% endhint %}

{% hint style="info" %}
If you are looking for a relationship created by a lookup or master-detail field:

* Go to Setup > Object Manager.
* Select the Child Object (the object that points to the parent).
* Go to Fields & Relationships and open the specific Lookup/Master-Detail field that links to the parent.
* Look for the field labeled Child Relationship Name. This is the value you need.
* Again, if it is a custom relationship, append `__r` to this value (e.g., if the name is `My_Custom_Items`, the relationship name in SOQL is `My_Custom_Items__r`).
  {% endhint %}

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GM - Dynamic FieldSet Grid</strong></td><td>Every property of the component.</td><td><a href="/package-reference/components-library/gm-dynamic-fieldset-grid.md">GM - Dynamic FieldSet Grid</a></td></tr><tr><td><strong>Grid - Dynamic Interaction</strong></td><td>Publish grid events so other page components react without leaving the page.</td><td><a href="/advanced-guides/dynamic-components/grid-dynamic-interaction.md">Grid - Dynamic Interaction</a></td></tr><tr><td><strong>Field Set Grid</strong></td><td>Build a grid from a field set, including parent fields.</td><td><a href="/product-tour/grids/field-set-grid.md">Field Set Grid</a></td></tr></tbody></table>

## GM - Dynamic FieldSet Grid Setup

Once you enable the **Dynamic Interaction** option, you can begin creating dynamic interactions. The video below is a step-by-step tutorial to learn how to use the **GM - Dynamic FieldSet Grid**👇.

{% embed url="<https://youtu.be/GXSNWbwweUY>" %}
Dynamic FieldSet Grid
{% endembed %}


---

# 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/advanced-guides/dynamic-components/grid-dynamic-fieldset-grid.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.