> 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/view-hidden-fields.md).

# View hidden fields

If you want to view hidden fields in your Analyzer report, use the **Show Hidden Fields** option from the **View** menu.

1. In the **Available fields** list, click the Down Arrow next to the **View** option.
2. From the context menu which appears, click **Show Hidden Fields**.

   The hidden fields now show in gray in the **Available fields** list.

   ![Show hidden fields](/files/3hR9N2q5qF5Fx4dKhuzq)
3. To prevent the hidden fields from appearing in the list, clear the **Show Hidden Fields** option.

   ![Show Hidden Fields option](/files/sQLOpIN0PbZq9k1uyaxw)

   **Note:** You can use hidden fields to create and edit the formulas for calculated measures. When you select the **Show Hidden Fields** option in the **View** menu for the**Available Fields** list, measures set as 'hidden' are available for selection in the calculated measure formula field. To view these hidden measures, you need the **Manage Data Sources** permission.


---

# 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/view-hidden-fields.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.