> 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/distinct-values-build-large-reports-in-pir.md).

# Distinct values

By default, Interactive Reports queries data with the SQL `SELECT DISTINCT` statement when no `GROUP BY` is used in the SQL query. This SQL statement returns only distinct (different) values, which may require an extensive sorting operation in the database. To stop the query from returning distinct values, clear the **Select Distinct** option in the Query Settings dialog box. Your setting of the **Select Distinct** option is saved with your report. For example, if you clear **Select Distinct** then save and close your report, this option will be cleared when you reopen the report.

**Note:** If you are logged in as an administrator, you can right click on the toolbar and select **View SQL** to verify if `DISTINCT` is a part of the SQL statement.

If you want to clear the **Select Distinct** option by default for new reports, ask your system administrator to review the **Administer Pentaho Data Integration and Analytics** document for further information.


---

# 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/distinct-values-build-large-reports-in-pir.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.