> 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/10.2-analytics/pentaho-dashboard-designer-cp/advanced-topics/set-dashboard-parameters/getting-started-with-the-query-editor-set-dashboard-parameters.md).

# Getting started with the Query Editor

When you place a chart in a dashboard panel, you use the Query Editor to retrieve data from a database for display on your chart or data table. If applicable, you can add conditions or constraints that filter the data so that the chart or data table displays the information you want dashboard consumers to see.

Using parameters is critical if you plan on using dashboard prompts or linking content in one dashboard panel to content on another dashboard panel. For example, suppose you create a pie chart and you want to filter details associated with an exploded pie slice in the adjoining data table as shown in the example below. In this instance, you must use a parameter that allows the data table to update when a dashboard consumer clicks on a pie slice. Optionally, you can parameterize the query condition so that the content is updated based on a user interaction, such as changing a prompt value.

![Example of content linking](/files/fjT25av2r9gePct6EivK)


---

# 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/10.2-analytics/pentaho-dashboard-designer-cp/advanced-topics/set-dashboard-parameters/getting-started-with-the-query-editor-set-dashboard-parameters.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.