> 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-interaction.md). # Grid - Dynamic Interaction Publish grid events to the App Builder so other page components react without leaving the page. **GridMate - Dynamic Interaction** feature enhances usability by allowing users to access or view related data without navigating away from the current context. It provides a seamless way to explore associated records or details without the need for switching between different screens or pages. Additionally, it reduces the need for multiple clicks or page reloads, streamlining the user experience and improving productivity. ## Enable Dynamic Interaction Enable Dynamic Interaction option allows the component to publish events that can be leveraged by the Lightning App Builder to create more [interactive UI](https://help.salesforce.com/s/articleView?id=sf.dynamic_interactions_overview.htm\&type=5). With this feature GridMate can be integrated with Lightning Component.

## Next steps


Grid - Dynamic FieldSet Grid	Show related records of the row selected in a parent grid.	Grid - Dynamic FieldSet Grid
Grid - Dynamic Record Card	Display record details when users click a master grid row.	Grid - Dynamic Record Card
User Grid - Dynamic Interactions	Drive a GM - Dynamic FieldSet Grid from User Grid rows.	User Grid - Dynamic Interactions

## Dynamic Interaction 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 **Dynamic Interaction** 👇. {% embed url="" %} Dynamic Interaction {% 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-interaction.md?ask=&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.