> 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](/files/Nb2dszUXI3OZXknZu4Tl)

   **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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
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=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.