> 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/creating-dashboards/add-a-report-from-report-designer.md).

# Add a report from Report Designer

Use these steps to add a report created with Report Designer.

1. Select a panel in the Dashboard Designer.
2. Click the **Insert** icon and choose **File**.

   A browser window opens.
3. Locate the appropriate report file.
4. Click **Select** to place the report inside the dashboard panel.

   Pagination control arrows at the top of a report allows you to scroll through long reports. Notice that the report file name, `Inventory.prpt`, appears under **Content** in the dashboard edit pane in the sample below. This sample report contains parameters. You can enter values manually and link them to a dashboard filter in the text boxes under **Source**. When the report renders again, the parameter value(s) you entered are included in the report.

   ![Sample report in dashboard](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-26405fe3cb82b8c6330ad3c5cb982b5ac6c69cd1%2FPDD_sample_report.png?alt=media)

   **Important:** If you choose a Report Designer file to place in a dashboard, but do not supply values for required parameters, the report will show up blank.


---

# 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/creating-dashboards/add-a-report-from-report-designer.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.
