> 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/9.3-report-designer/create-queries-report-designer-cp/create-mdx-queries-create-report-designer-queries.md).

# Create MDX queries

For Pentaho Analyzer data sets, such as OLAP and OLAP (advanced), you can create MDX queries by specifying a Mondrian cube definition schema file.

You must be in the Data Source Configuration window to follow this process. You should also have configured a JNDI data source connection.

Perform the following steps to add a MDX query:

1. In the **Data** tab, right-click on **Data Sets** and select one of the following options to access the Pentaho Analyzer Data Source Editor window:
   * **OLAP** > **Pentaho Analysis**
   * **OLAP** > **Pentaho Analysis (Denormalized)**
2. Specify a Mondrian cube definition schema file for Pentaho Analysis Schema File.

   You can use the Pentaho Schema Workbench to create this file.
3. Select your data source in the **Connections** pane on the left, then click the round green **+** icon above the **Available Queries** pane on the right.
4. Type a concise yet sufficiently descriptive name for your query in the **Query Name** field.
5. Type an MDX query into the **Query** pane on the right.
6. Click **Preview** to view the unformatted query results.
7. Click **OK** to finish working on the query.


---

# 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/9.3-report-designer/create-queries-report-designer-cp/create-mdx-queries-create-report-designer-queries.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.