> 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](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-002fab016f3f9306ba0356c61f0181ba189db2db%2FPDD_QE_Content_Linking_Sample_ONYX.png?alt=media)


---

# 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.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=<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.