> 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-report-designer/output-parameterization-by-report-designer-cp.md).

# Output parameterization

You can create reports with parameters that the report reader can adjust, which is easier than creating multiple reports with the same basic layout and similar data. Simple parameterization involves changing data values. For example, report readers might want to filter data by product. You can provide report readers with the option to filter by the values in a drop-down list. In this case, you would parameterize the column that contains product names, so report readers can change for which product they want to see data.

While simple parameters are added after the data structure has been defined through a query, advanced parameters give readers the power to change the data structure itself. For example, you might offer an option to select among multiple columns in a given table. These parameters must be expressed as formulas and are executed with the query.

For instructions on working with output parameterization, see the following topics:

* [Simple SQL output parameterization](/pba-report-designer/output-parameterization-by-report-designer-cp/simple-sql-output-parameterization.md)
* [Advanced SQL output parameterization](/pba-report-designer/output-parameterization-by-report-designer-cp/advanced-sql-output-parameterization.md)
* [Simple metadata output parameterization](/pba-report-designer/output-parameterization-by-report-designer-cp/simple-metadata-output-parameterization.md)
* [Simple OLAP output parameterization](/pba-report-designer/output-parameterization-by-report-designer-cp/simple-olap-output-parameterization.md)


---

# 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-report-designer/output-parameterization-by-report-designer-cp.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.