> 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/9.3-analytics/pentaho-analyzer-cp/advanced-topics/use-calculated-measures-in-analyzer-reports.md).

# Use calculated measures in Analyzer reports

In Pentaho Analyzer, calculated measures are user-defined measures based on a user's customizations to base measures in the data model. By applying a formula, in this case an MDX statement, to a selected base measure, the user creates a calculated measure to use in their Analyzer report.

As part of inline modeling, you can now save your calculated measure to the data model while creating or editing your report in Analyzer. Previous to Pentaho 6.0, if you wanted to add a particularly useful calculated measure to the model for others to use in their reports, you had to submit a request to IT and wait until it was available. Now you can save the calculated measure to the model from within Analyzer so other users can benefit immediately from your work.

To add calculated measures to the model or to edit calculated measures saved to the data model, you must be assigned the **Manage Data Sources** operation permission in Users and Roles. For more information on setting and maintaining permissions and roles for users, see [Use Pentaho Security](/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc.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/9.3-analytics/pentaho-analyzer-cp/advanced-topics/use-calculated-measures-in-analyzer-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.