> 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/pdia-data-integration/pdi-transformation-steps-reference-overview/mondrian-input-pdi-transformation-step-cp.md).

# Mondrian Input

The Mondrian Input step reads data from a Mondrian cube using a Multidimensional Expression Language (MDX) query and a Mondrian schema description (catalog).

You can create Mondrian schemas using **Pentaho Schema Workbench**. For information about configuring the `mondrian.properties` file, see [Mondrian configuration](http://mondrian.pentaho.com/documentation/configuration.php). Place `mondrian.properties` in the `data-integration/lib` directory or another location on your classpath.

![Mondrian Input dialog](https://773338310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwnJ6Fexn4LZwKRHghPK%2Fuploads%2Fgit-blob-c0b1048f7775d550084b13f9ff85d0a0aaf5604a%2FPDI_TransStep_Mondrian_Input_dialog.png?alt=media)

### General

| Field                           | Description                                                                                                                                                                                                                                           |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step name**                   | Specify the unique name of the Mondrian Input step on the canvas. You can customize the name or leave it as the default.                                                                                                                              |
| **Connection**                  | Specify the database connection to query. Select **Edit** to modify an existing connection, **New** to create a new connection, or **Wizard** to open the Database Connection wizard.                                                                 |
| **MDX query**                   | Specify an MDX query to define a result set and retrieve data. An example query appears in the **MDX query** area.                                                                                                                                    |
| **Replace variable in script?** | Select to replace variables in the MDX query before sending the query to the database.                                                                                                                                                                |
| **Catalog location**            | Specify the path to the Mondrian schema file. Select **Browse** to choose the catalog location.                                                                                                                                                       |
| **Role**                        | Specify a role to use for access control. You can specify multiple roles separated by commas. If a role name contains a comma, escape it with an extra comma. When you use multiple roles, queries execute with the combined privileges of all roles. |


---

# 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/pdia-data-integration/pdi-transformation-steps-reference-overview/mondrian-input-pdi-transformation-step-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.
