> 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](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-4cda96716b03e357b3bce32b2b82db6177e8744f%2FAnalyzer_ShowHidden.png?alt=media)
3. To prevent the hidden fields from appearing in the list, clear the **Show Hidden Fields** option.

   ![Show Hidden Fields option](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-6b3c8e3a94f10d88db4b3ec61c33884ad4ad08df%2FAnalyzer_ShowHidden_Unselect.png?alt=media)

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