> 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/10.2-analytics/pentaho-analyzer-cp/working-with-analyzer-fields/hide-and-unhide-fields/hide-a-field.md).

# Hide a field

This task assumes you are in an Analyzer report.

1. In the **Available fields** list, hover your mouse over the field you want to hide and click the Down Arrow.
2. From the context menu which appears, click **Set Hidden** to hide the field.

   This field is no longer visible in the list.

   ![Hide a field](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-4464c7cfcc33d878689d79445477b10d9e8b1373%2FAnalyzer_SetHiddenMenu.png?alt=media)

   **Note:** When you hide a field which is currently used in one or more of your reports, the field is automatically removed from all of your reports, including [drill-through links](https://github.com/pentaho/documentation/blob/main/PDIA/10.2/Analytics/Pentaho%20Analyzer/Pentaho%20Analyzer%20cp/Set%20Analyzer%20report%20options/Turn%20on%20drill-through%20links=GUID-29ACF615-2298-4EA9-80A9-473DE845F6B8=3=en=.md). You can click the **Undo** button to restore the field to the report prior to saving your changes. Once saved, you will have to [unhide that field](/pba/10.2-analytics/pentaho-analyzer-cp/working-with-analyzer-fields/hide-and-unhide-fields/unhide-a-field.md) to restore it to the **Available fields** list.


---

# 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/10.2-analytics/pentaho-analyzer-cp/working-with-analyzer-fields/hide-and-unhide-fields/hide-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.