> 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-interactive-reports-cp/build-large-reports.md).

# Build large reports

If you are building Interactive Reports with a large amount of data, you might find that it is quicker to build the report if the data is not constantly refreshing or returning a large number of rows. You can manually refresh the report to view your results at any point in the process.

**Note:** When you are done designing the report and want to run it with the entire data set, you can generate the full report by simply [scheduling](https://docs.pentaho.com/pba/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports.md) the report to run.

You can limit how often you query the data while building your report to help reduce the amount of time required to refresh the report. Use the options in the **Query Settings** dialog box to adjust refresh times while you are building your report.

* In the **Data** tab, click the Settings icon in the upper-right corner to open the **Query Settings** dialog box. Make changes as needed and close the dialog box when you are done.

![Query Settings dialog box](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-a13663a51c27288b26e3335a07fe8047920575bf%2FssPIRQuerySettingsDialogBox.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-interactive-reports-cp/build-large-reports.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.
