> 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/rename-a-field.md).

# Rename a field

To rename a field within a report, do the following:

1. Right-click the field you want to rename in the report.
2. Select **Edit** or **Column Name and Format** from the menu to open the Edit dialog box for that field.
3. Enter the new name in the **Name** field.

   Note that you can also view the original name of the field in this dialog box.
4. (Optional) Enter the plural version of the new name (if applicable) in the **Plural Name used within this report** field.

   Plural versions of a field name are useful because the Pentaho interface often uses field names in menus and dialog boxes. If you enter a plural version of the new field name, it automatically will be used in situations where the plural form is grammatically correct.
5. Click the **OK** button to save the new field name.

Renaming the field only effects the contents of the report. A user can view the original name of the field by [viewing the definition of the field](/pba/9.3-analytics/pentaho-analyzer-cp/working-with-analyzer-fields/view-the-definition-of-a-field.md).

**Note:** To remove a modified (renamed) field name, open the Edit dialog box and delete the existing entries using the Backspace key.


---

# 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/rename-a-field.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.