> 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/data-source-model-editor-cp.md).

# Data Source Model Editor

The Data Source Model Editor guides you through editing relational and multidimensional models created using the Data Source Wizard. The Data Source Model Editor gives you the ability to move fields by dragging them to the appropriate location, mix and match fields from different tables, add fields to more than one category, or remove a field altogether.

**Note:** You can edit the models with the Data Source Model Editor or use **Pentaho Schema Workbench** or **Pentaho Metadata Editor** for more advanced modifications. Relational and multidimensional models that have been edited in Metadata Editor and Schema Workbench can no longer be edited in the Data Source Model Editor.

The following tasks are things you can do to refine your relational and multidimensional data models with the Data Source Model Editor. Also included are some things that you can do specifically to refine your multidimensional data models, including:

* Assign Geographic Properties
* Assign Time Dimension Properties
* Use Ordinal Columns
* Properties of Time Dimension Levels


---

# 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/data-source-model-editor-cp.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.