> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/super-filter/filter-types/8.-play-axis/i.multilevel-selection.md).

# i.Multilevel Selection

The **Multi-Level Selection** feature in Play Axis allows filtering through **all unique data point combinations** when a multi-level hierarchy (more than one category) is added to the visual.

## **How to Configure**

{% stepper %}
{% step %}
Add a **multi-level hierarchy** (e.g., **Category > Subcategory > Product**).
{% endstep %}

{% step %}
In the Format Visual enable **Play Axis** and **Multilevel Selection**.
{% endstep %}

{% step %}
**When Multi-Level Selection is Enabled:**

* Filters cycle through **all unique combinations** in the hierarchy instead of just categories. Filtering is done based on the **unique combinations** of values across those levels, rather than treating each level independently.
* Examples:
  * If the hierarchy includes **Category, Subcategory, and Product**, the filter will display in the sequence of unique pairs, such as **Electronics → Mobile Phones → iPhone → Electronics → Mobile Phones → Samsung Galaxy → Apparel → Footwear → Sneakers → Apparel → Footwear → Sandals**, and so on.
  * If the hierarchy includes **Year and Month**, the Play Axis will filter in the sequence of **unique Year-Month pairs**, such as **2022 - August → 2022 - September → ... → 2022 - December → 2023 - January → 2023 - February**, and so on.
    {% endstep %}

{% step %}
**When Cumulative Selection is enabled along with Multilevel selection:**

* It allows users to apply filters incrementally rather than replacing them. With each new value, the filter builds upon the previous one, preserving earlier selections. 
* In Multi-Level Selection, this means that all unique data point combinations are added one by one—creating a cumulative view that reveals how the trend evolves across different levels of the hierarchy.
* In the video below, a Date Hierarchy consisting of Year and Month is added to the category section. Both Multi-Level Selection and Cumulative Selection are enabled in the Play Axis format pane. As a result, the data builds up incrementally starting with July 2022, then adding August 2022 to show a progressive trend

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPIvQSuyE40UC9wv5uGgW%2Fuploads%2F6b50Y8qwlGQwq4agzpq8%2FPlay%20Axis.mp4?alt=media&token=c8cf0d96-550c-46e0-806e-e46b4aa89412>" %}
Video 1: Play axis with Date hierarchy in category and cumulative selection enabled.
{% endembed %}
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inforiver.com/super-filter/filter-types/8.-play-axis/i.multilevel-selection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.