> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/dynamic-components/tutorials/reactive-components.md).

# Reactive Components

## What is Reactivity?

Reactivity means that components can "talk" to each other. When a user interacts with one component (like selecting a row in a Data Table), other components on the page can *automatically* update to reflect that change. This creates a much more dynamic and intuitive user experience than static pages.

### **Key Benefits:**

* **Simplified Development:** You don't need to write complex code or formulas to connect components.
* **Responsive Interface:** The UI feels "alive" and instantly reflects changes.
* **Data Consistency:** Automatic updates ensure that all components display consistent information.
* **Easier Maintenance:** Changes in one place automatically propagate, reducing errors

## How Reactivity Works in Avonni Dynamic Components

Avonni Dynamic Components make reactivity simple. It's all about connecting components through their *data*.

Here are the key concepts.

### **Key Concepts**

#### Avonni Query Data Source

The **Avonni Query Data Source** is the foundation for reactivity. It's designed to:

* **Support Dynamic Filtering:** Filters can depend on values within your Dynamic Component, including attributes of other components.
* **Automatically Re-query:** When a referenced value changes, the query automatically re-executes, updating the connected component.
* **Efficient Updates:** Optimized for frequent data changes.

#### Direct Attribute Referencing

You create these dynamic links using *direct attribute referencing*. This is a simple, visual way to connect components *without* writing complex formulas.

{% @arcade/embed url="<https://app.arcade.software/share/p8KWbkvXFNiGmXCPnIOA>" flowId="p8KWbkvXFNiGmXCPnIOA" %}

## Examples

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Reactive Map and Data Table</strong></td><td><a href="https://docs.avonnicomponents.com/dynamic-components/tutorials/reactive-components/maps-and-geolocation/reactive-map-and-data-table.md">Reactive Map and Data Table</a></td></tr><tr><td><strong>Master-Detail Relationship with Data Tables</strong></td><td><a href="https://docs.avonnicomponents.com/dynamic-components/tutorials/reactive-components/data-relationships/master-detail-relationship-with-data-tables.md">Master-Detail Relationship with Data Tables</a></td></tr><tr><td><strong>Vertical Tabs with Reactive Data Table</strong></td><td><a href="https://docs.avonnicomponents.com/projects/dynamic-components/layout-and-interactions/vertical-tabs-with-reactive-data-table.md">Vertical Tabs with Reactive Data Table</a></td></tr></tbody></table>


---

# 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.avonnicomponents.com/dynamic-components/tutorials/reactive-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.
