> 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/dimensional-dataset/set-up-viz-extension.md).
# Set-up Viz extension
To set up the Viz extension, we will need to create or use a datasheet with a dimensional data structure. In this example, we will use the Product structure from the SuperStore dataset which is already available as an hierarchy.
The HierarchyFilter extension can be loaded into the datasheet using the Viz trex or by using the extension exchange. After loading in the extension, the datasheet should look like this:
You can start a dimensional tree by dragging dimensions or measures onto the Fields mark in the marks pane. After which, the datasheet will look something like this.
The order of the items in the marks pane is the same as the order of the HierarchyLevels from top to bottom. You can rearrange these items by dragging them.
It is also possible to drag measures onto the "Measures" field in the marks pane to quickly create aggregations next to the tree.
You can click the format extension button in the marks pane to configure extra features of the extension. More information can be found in the Configuration pages of this wiki.
From here, you can use the HierarchyFilter in dashboards by dragging in this datasheet. It is important to click the "use as Filter button" on the extension box.
Now that this button is enabled, clicking any item in the tree should filter on the rest of the dashboard items.
---
# 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/dimensional-dataset/set-up-viz-extension.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.
