> 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/working-with-analyzer-fields/selecting-unit-of-measure-in-a-report-analyzer-report.md).

# Editing units of measure in a report

If you are working with large numbers, you can select and display the applicable unit of measure for that field. This task assumes you are working with a base or calculated measure in the field of an Analyzer report.

To add or edit a unit of measure, perform the following steps:

1. In your report, right-click the column header of the measure you want to modify, such as **Quantity** or **Sales**.
2. From the menu that appears, select **Edit**. The **Edit Column** dialog box opens.
3. In the **Format** field, select **Currency** or **General Number**.
4. In the **Units** field, select the unit of measure. .

   The **Units** field is only available when the format is set to **Currency** or **General Number**
5. Click **OK** to save your changes.

   ![](https://698418877-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgb0b8jIz4HuPLxqQR6C4%2Fuploads%2Fgit-blob-1bfe9f85ef8b0293fb756f9812a7e8a96070322d%2FAnalyzer%20Edit%20column.png?alt=media)

Your report now displays the assigned unit of measure.

![](https://698418877-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgb0b8jIz4HuPLxqQR6C4%2Fuploads%2Fgit-blob-aeca43454c3709ff8b247fd88fc96ba7d93bad6f%2FAnalyzer%20Unit%20of%20Measure%20in%20report.png?alt=media)


---

# 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/working-with-analyzer-fields/selecting-unit-of-measure-in-a-report-analyzer-report.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.