> For the complete documentation index, see [llms.txt](https://docs.sprinkledata.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinkledata.com/product/analysing-your-data/reports/build-sql-reports/visualizations.md).

# Visualizations

In **Report** you can create simple to complex visualization reports using various visual chart options available as per your need.

After you have selected the desired **SQL Report** as an input you can simply go to the **Visualization** pane by clicking on the **Visualization** Icon ![](/files/ffS6E8sjmPi7orBRsWbk) left of the Schema Browser and choose the type of chart as per your need. 

You can create **Line Charts**, **Bar Charts**, **Pie Charts Scatter plots,** etc. kinds of reports using **Report**  with Model as an Input**.**

To know more about the different Visualization types available in **Report** in detail refer to the below docs.

{% content-ref url="/pages/Q2RdUfK3mHnDnUIssrIr" %}
[Visualizations](/product/analysing-your-data/reports/build-using-tables/visualizations.md)
{% endcontent-ref %}


---

# 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.sprinkledata.com/product/analysing-your-data/reports/build-sql-reports/visualizations.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.