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

# Dynamic components

Make a grid row drive other components on the page, so users see related data without leaving it.

Dynamic components react to the row a user clicks in a parent grid, so related records or details appear on the same page.

The parent (master) grid needs the **Enable Dynamic Interaction** option checked, so it publishes the events the other components react to.

## Which guide do I need?

| Guide                                                                                                                     | Use it to…                                                                                                                        | Good to know                                                                                                                                 |
| ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| [Grid - Dynamic Interaction](https://docs.gridmate.io/advanced-guides/dynamic-components/grid-dynamic-interaction.md)     | Publish grid events to the Lightning App Builder so other page components react without leaving the page.                         | Turned on with the Enable Dynamic Interaction option on the grid.                                                                            |
| [Grid - Dynamic FieldSet Grid](https://docs.gridmate.io/advanced-guides/dynamic-components/grid-dynamic-fieldset-grid.md) | Show the related records of the row selected in a parent grid.                                                                    | Has the same properties as GM - FieldSet Grid, plus Parent Object Name, Parent Grid Name and Parent Grid Code to link it to the parent grid. |
| [Grid - Dynamic Record Card](https://docs.gridmate.io/advanced-guides/dynamic-components/grid-dynamic-record-card.md)     | Display record details in a card when users click a row of a master grid (GM - RelatedList, GM - ListView or GM - FieldSet Grid). | The master grid needs **Enable Dynamic Interaction** checked.                                                                                |

## Go further

* [User Grid - Dynamic Interactions](https://docs.gridmate.io/advanced-guides/user-grid/user-grid-dynamic-interactions.md): drive a GM - Dynamic FieldSet Grid from User Grid rows.
* [GM - Dynamic FieldSet Grid](https://docs.gridmate.io/package-reference/components-library/dynamic-components/gm-dynamic-fieldset-grid.md): every property of the component.
* [GM - Dynamic Record Card](https://docs.gridmate.io/package-reference/components-library/dynamic-components/gm-dynamic-record-card.md): every property of the component.


---

# 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.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.
