> 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/showmemore/features/sunburst-diagram/configuration-screen.md).

# Configuration Screen

#### Select data sheet

Select the worksheet you want to retrieve data from. This worksheet will be the input for the visualization you pick in the next step.  

### Customize sunburst diagram

Choose the dimensions you wish to show in your Sunburst Diagram. Use the dropdown menu to select your dimension. The first chosen dimension will fill out the inner part of your Sunburst Diagram. Assign your chosen measure by clicking on the measure dropdown menu. Example: A book store would use a Sunburst Diagram to see sales per genre. The hierarchy could be ‘Genre’, ‘Sub-Genre’, ‘Topic’ etc. This is an ideal way of showing which genres have the best sales.

<figure><img src="https://1632500807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ARtwElTSzdwWxw4t1pi%2Fuploads%2FeHKLiM2x25pMDnk29v1F%2FsunburstOld-config.png?alt=media&amp;token=406d4b67-0b3a-44ec-87f3-22948a7d33e8" alt="" width="375"><figcaption></figcaption></figure>


---

# 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/showmemore/features/sunburst-diagram/configuration-screen.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.