> 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/9.3-analytics/pentaho-analyzer-cp/display-the-member-properties-of-a-field-or-level.md).

# Display the member properties of a field or level

When a number in parenthesis appears next to a dimension in a list of **Available fields**, that dimension is associated with specific member properties. You can use those properties to constrain dimensions. If you want to review available fields, click **Add more fields onto the report** on the report toolbar.

Perform the following steps to filter by member properties:

1. Locate a dimension in the **Available fields** list that includes a number in parenthesis, for example, Customer (6), or Product (3).
2. Locate the corresponding dimension on your report. Right-click the row or column header for that dimension, then click **Show Properties**.

   A menu displays member properties you can choose.
3. Select or clear the member property you want in the report, then click **OK**.

Your analyzer report is filtered by the choices you made.


---

# 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/9.3-analytics/pentaho-analyzer-cp/display-the-member-properties-of-a-field-or-level.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.