> 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/data-source-model-editor-cp/add-member-properties-to-a-level.md).

# Add member properties to a level

Within the Data Source Model Editor, you can add member properties to any level of a data source model for use in generating Interactive and Analyzer reports.

1. Click the **Analysis** tab.
2. Select a field from the **Available** pane to the **Analysis** pane.
3. With the field selected, click the **Add Member Property** icon.

   The New Member Property dialog box appears.
4. Enter a name for the new member property. Click **OK**
5. Set the source column for the new member property. Expand the level with new member property and choose the member property.

   A yellow caution icon appears next to the parent dimension, hierarchy, and level of the new child member property. The icon indicates you need to specify the source column for the new member properties before proceeding. Enter a name for the new member property.
6. Specify the source column for the new member property. Click **Fix Missing Column**.

   The Select Source Column dialog appears.
7. Chose a column from the available list. Click **OK**.


---

# 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/data-source-model-editor-cp/add-member-properties-to-a-level.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.