> 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/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/set-dashboard-parameters.md).

# Set dashboard parameters

If you are placing a file, such as an `.xaction` or `.prpt`, inside a dashboard panel, it is possible that the author of the file defined meaningful parameters for the content. If previously defined, the parameters and their associated default values, appear under **Parameters** in the edit pane of the dashboard.

In the example in this article, when the chart initially rendered, it displayed a parameter called *chart\_type* with a default value called bar. A user can change the value of the parameter to see the content rendered as a pie, line, or area chart.

Parameter names are hard-coded in the file, which means they cannot be changed. Neither can you change the number of parameters associated with a file. When you create a chart using the Chart Designer, embed a URL into a dashboard, or create a data table, you can change both the name and value of a parameter.

**Note:** In Windows, the URL parameters have a maximum limit of 2,048 characters, minus the number of characters in the actual path.


---

# 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/9.3-analytics/pentaho-dashboard-designer-cp/advanced-topics/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.