> 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/get-started-with-the-data-source-model-editor.md).

# Get started with the Data Source Model Editor

The model editor displays if you choose to customize your model in the last step in the Data Source Wizard, or if you edit the data source later by clicking **Manage Data Sources**, selecting a data source, and clicking the **Edit** icon.

1. Open the Data Source Model Editor by clicking **Manage Data Sources**, selecting a data source, and clicking the **Edit** icon.

   The Data Source Model Editor appears.
2. Select the **Reporting** tab to edit a reporting relational model, or the **Analysis** tab to edit the analysis multidimensional model.
3. You can now edit the model or clear the model and start building a model from scratch. For instance, you can choose a field and drag it to the appropriate folder on the **Analysis/Reporting** model pane.

   This causes that field to be displayed and used when designing reports.
4. Click **OK** when you are done editing your model.

The model builds and appears in the **Data Source** list.


---

# 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/get-started-with-the-data-source-model-editor.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.