> 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/components/slider/range-slider-setting-a-price-filter.md).

# Range Slider: Setting a Price Filter

This example shows a range slider for selecting a price filter. The selected values are automatically available as a component attribute (`$Component.apiName.Value`), a collection where index 0 is min and 1 is max—eliminating the need for a separate variable binding unless required for advanced scenarios. Set an initial range directly in the Value property if needed (e.g., \[50, 250]).

{% stepper %}
{% step %}
**Add Slider Component**

* **API Name**: priceRangeSlider (used for referencing the Value attribute later)
* **Label**: "Filter by Price Range:"
* **Multiple Values**: On
* **Value**: (Optional initial: \[50, 250]; no binding needed for basic use)
* **Min**: 0
* **Max**: 500
* **Step**: 10
* **Unit**: currency
* **Show Pin**: On
* **Disable Swap**: On
  {% endstep %}

{% step %}

#### Integrate with Data Table

In the Data Table's query filters, use `$Component.priceRangeSlider.Value[0]` (min) and `$Component.priceRangeSlider.Value[1]` (max) to apply the range dynamically
{% endstep %}

{% step %}

#### Add Interaction

In the Interactions Panel for the Slider, add an "On Change" action to refresh the Data Table's Data Source.
{% endstep %}
{% endstepper %}

**Result:** Range selections filter data dynamically.


---

# 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/components/slider/range-slider-setting-a-price-filter.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.