> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/hierarchyfilter/getting-started/introduction.md). # Introduction The HierarchyFilter extension can interact with your dashboard through parameters that can be used in calculations, filters, and set/parameter actions. It also allows you to set a filter that can be used to limit the data in the hierarchy to the current node and all child nodes and mark selections of selected nodes and child nodes. #### Supported data structures It is important to know that the HierarchyFilter extension supports two different data models to visualize and interact with your hierarchy dataset. Both datamodels require a different approach in configuring the HierarchyFilter extension. This Product Guide will elaborate on both data models/structures. 1. Dimensional data. The hierarchy is based on the dimensions in your dataset. An example of this model is the Product Structure in the SuperStore demo dataset of Tableau (Category >> Sub-Category >> Manufacturer >> Product Name) 2. Recursive data. The data structure you will often find in organization structures and consists of a Parent-Child relationship. --- # 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.infotopics.com/hierarchyfilter/getting-started/introduction.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.