> 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/working-with-the-available-fields-list/view-the-list-of-available-fields.md).

# View the List of Available fields

You may organize the list in four ways. To change the organization, do the following.

1. Click the **View** button at the top of the pane.
2. Select one of the following sort options for organizing the list of fields:
   * **By Category (default)**

     This grouping is set by an administrator.
   * **By Type**

     Lets you see the list where all measure fields come first, followed by level fields.
   * **A to Z**

     Alphabetical order with no grouping.
   * **By Schema**

     This displays the grouping as defined by the administrator in the cube’s underlying schema.

To find a particular field, on the **Available Fields** list, type the first characters of the field name in the **Find** box.


---

# 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/working-with-the-available-fields-list/view-the-list-of-available-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.