> 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/drilldowntree/getting-started/getting-started-with-drilldowntree.md).
# Getting started with DrillDownTree
For best practice and to get the best performance on your dashboard, we recommend dropping the measure(s) and dimensions on to the detail of your marks card on a separate/new worksheet.
This will give DrillDownTree the best performance and flexibility for dashboard actions. See the image below for an example of how to set up your datasheet to feed the extension. All dimensions available on the datasheet can be used in the users Drill Down path. For tips and advice check out our [BLOG](https://appsfortableau.infotopics.com/educational/tableau-tip-using-datasheets-to-supply-data-to-extensions/).
The datasheet needs to be on the dashboard. It is not the prettiest visualization so it is best to hide it for your dashboard users on the dashboard.
To do so: **Add the worksheet to your dashboard as a ‘floating’ container.** **Then , in the Layout tab, edit the size to 1x1px (and the position also to the 1,1 x,y position). This will make your datasheet active on your dashboard without being shown. This is shown below:**
---
# 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.infotopics.com/drilldowntree/getting-started/getting-started-with-drilldowntree.md?ask=&goal=
```
`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.