> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba-report-designer/10.2-report-designer/add-a-chart/create-a-sparkline-chart-create-report-designer-charts.md).

# Create a sparkline chart

Sparkline charts require comma-separated values (CSV) for input. If your data is not in CSV format, you must create a Pentaho Data Integration transformation to put commas between each data point, or you can manually insert commas between your data points.

Perform the following steps to add a sparkline chart to your report:

1. Drag and drop a **Sparkline Pie**, **Sparkline Bar**, or **Sparkline Line** element into a layout band.
2. Using the resize handles, change the size of the chart to fit your specifications.
3. Click the round green **+** icon in the **Value** row.

   A formula field will appear.
4. In the formula field, select the function that formats your sparkline data, or type in comma-separated values by hand directly, then click **Close**.
5. Click **Preview** to verify that your chart appears as intended.


---

# 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.pentaho.com/pba-report-designer/10.2-report-designer/add-a-chart/create-a-sparkline-chart-create-report-designer-charts.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.