> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses/semantic-model-editor.md).

# Semantic Model Editor

Coming soon — Build semantic models in the Semantic Model Editor: connect to the data, define cubes, dimensions, hierarchies, levels and measures, then publish and test them in Analyzer.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** **🚧 In development — coming soon.** This Speciality is still being written. The outline below comes from the draft course `analyst-sme-specialty` in Pentaho Content Manager: module and lesson names, kinds and estimated times are taken from its lab manifests, and may change before release. The labs have not yet been tested on a lab server. Items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

Build semantic models in the Pentaho Semantic Model Editor: connect to the data, define schemas and cubes, dimensions, hierarchies, levels, measures and properties, then publish and test them in Analyzer, on the Steel Wheels and Classic Models samples.

{% columns %}
{% column %}

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i><br><strong>12 lessons</strong><br><em>across 5 modules</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-flask" style="color:orange;">:flask:</i><br><strong>7 workshops</strong><br><em>hands-on labs</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-clock" style="color:cyan;">:clock:</i><br><strong>~6h 55m</strong><br><em>estimated</em></p>
{% endcolumn %}
{% endcolumns %}

{% hint style="success" icon="cloud-arrow-up" %}
Every workshop will be hands-on, on a Windows lab machine with the Lab Guide embedded. REPLACE-ME — confirm the hosted lab for this Speciality.
{% endhint %}

***

<h3 align="center">Before you start</h3>

{% columns %}
{% column %}
{% hint style="success" icon="circle-check" %}
**What you'll need**

Business Analytics, Level 1 — Practitioner, or day-to-day use of Analyzer. Schema Workbench is a natural lead-in, since it covers the same modelling ideas in Mondrian schemas, and the last module maps one to the other.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="tag" %}
**Built against**

Pentaho Enterprise Edition **11.0.0.0-232**, the build every course on the Academy runs, on a Windows lab machine.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% hint style="info" icon="trophy" %}

#### What you'll build

A Steel Wheels model built a layer at a time in the Semantic Model Editor — connection, the Steel Wheels Sales cube, dimensions with hierarchies and levels, measures and calculated members, formats and properties — then published and checked in Analyzer against known figures. The capstone models the Classic Models sample, with Orders and Payments cubes sharing a Customers dimension.
{% endhint %}

***

<h3 align="center">Course outline</h3>

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i> reading · <i class="fa-flask" style="color:orange;">:flask:</i> hands-on workshop</p>

{% hint style="info" icon="circle-info" %}
This is the draft outline. Times are the lab guides' own estimates, and the course is not yet open for enrolment.
{% endhint %}

<table data-search="false"><thead><tr><th width="382">Module</th><th width="115" align="center">Reading</th><th width="132" align="center">Workshops</th><th width="100" align="right">Time</th></tr></thead><tbody><tr><td>Getting Started</td><td align="center">2</td><td align="center">—</td><td align="right">~30m</td></tr><tr><td>Building the Model</td><td align="center">1</td><td align="center">2</td><td align="right">~1h 15m</td></tr><tr><td>Dimensions and Measures</td><td align="center">1</td><td align="center">3</td><td align="right">~2h 15m</td></tr><tr><td>Publish and Test</td><td align="center">1</td><td align="center">1</td><td align="right">~55m</td></tr><tr><td>Capstone Project</td><td align="center">—</td><td align="center">1</td><td align="right">~2h</td></tr><tr><td><strong>Total</strong></td><td align="center"><strong>5</strong></td><td align="center"><strong>7</strong></td><td align="right"><strong>~6h 55m</strong></td></tr></tbody></table>

{% stepper %}
{% step %}

### <i class="fa-rocket" style="color:blue;">:rocket:</i> Getting Started

`2 readings · ~30m`

How to get the most out of this guide, and what the Semantic Model Editor is: the semantic layer between raw data and every report.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2F7Kap65NY66TWizv43h26%2Fsemantic-layer.svg?alt=media" alt="The semantic layer in three rows. An Analyzer report asks for Sales by Territory in MDX; Mondrian reads the semantic model and sends SQL to the tables. The model holds Sales, the sum of TOTALPRICE as currency; Territory, from CUSTOMER_W_TER, rolling up from Country and City; and Average Price, Sales divided by Quantity. Canvas mode and Advanced mode both write the same XML."><figcaption><p>The semantic layer: the model says once what Sales and Territory mean, and Mondrian turns each question into SQL</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Before You Start</td><td>~15m</td></tr><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>What the Semantic Model Editor Is</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-cubes" style="color:blue;">:cubes:</i> Building the Model

`1 reading · 2 workshops · ~1h 15m`

Connect the editor to the Steel Wheels data and lay down the schema and cubes the rest of the course builds on.

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Semantic Models</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Connect to the Data</td><td>~30m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Schemas and Cubes</td><td>~30m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-sitemap" style="color:blue;">:sitemap:</i> Dimensions and Measures

`1 reading · 3 workshops · ~2h 15m`

Dimensions with hierarchies and levels, measures and calculated members, and the properties and formats that make a model read well.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FCUBogBZIDn2ftLY09PID%2Fdimension-kinds.svg?alt=media" alt="The Steel Wheels Sales cube. ORDERFACT is at the centre; the regular dimensions Markets and Customers join it on CUSTOMERNUMBER and Product on PRODUCTCODE; the degenerate Order Status reads its STATUS column with no join. Time, a shared dimension on DIM_TIME at schema level, is used through a DimensionUsage on TIME_ID. Below, Markets opened up: dimension, hierarchy, level Country, member France."><figcaption><p>Four kinds of dimension in one cube: regular, degenerate, and a shared time dimension used from schema level</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2Foh3EKCNmHz98yAW88pSk%2Fsql-vs-calculated-measure.svg?alt=media" alt="Two measures side by side. List Value, created with SQL: QUANTITYORDERED * PRICEEACH is worked out on each of the 2,996 ORDERFACT rows, then summed. Average Price, a calculated measure: Sales and Quantity are summed first (4,987,740 and 49,417 units in 2004), then divided in MDX, giving 100.93. A warning: an average stored as a column and summed is wrong above one row."><figcaption><p>A SQL measure multiplies on every row and then adds up; a calculated measure adds up first and then divides</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Dimensions and Measures</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Dimensions, Hierarchies and Levels</td><td>~45m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Measures and Calculated Members</td><td>~40m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Properties and Formatting</td><td>~35m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-cloud-arrow-up" style="color:blue;">:cloud-arrow-up:</i> Publish and Test

`1 reading · 1 workshop · ~55m`

Publish the model to the Pentaho Server and test it in Analyzer, and see how it relates to the Mondrian schemas of Schema Workbench.

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Publish and Test in Analyzer</td><td>~40m</td></tr><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>From Schema Workbench to the Semantic Model Editor</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-trophy" style="color:blue;">:trophy:</i> Capstone Project

`1 workshop · ~2h`

Model the Classic Models sample from an empty model to a published one, tested in Analyzer.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FwedH1z3iFypWQUjuTYGu%2Fclassic-models-target.svg?alt=media" alt="The Classic Models model on SampleData. The Orders cube, on ORDERFACT, holds Product, Time, the degenerate Order Status, and Sales, Quantity, Order Lines (hidden) and Average Price. The Payments cube, on PAYMENTS, holds the degenerate Payment Year and Amount, Payments and Average Payment. Both fact tables use the shared Customers dimension on CUSTOMERNUMBER."><figcaption><p>The target: two cubes, each with its own dimensions and measures, sharing one Customers dimension</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Capstone: Classic Models</td><td>~2h</td></tr></tbody></table>

</details>
{% endstep %}
{% endstepper %}

***

{% hint style="info" icon="award" %}
**Optional, not part of the path**

Speciality courses are open to any learner who wants to go further. They are not among the five mandatory courses of the Certified Solution Analyst path. The course ends in a capstone project. REPLACE-ME — confirm whether it carries its own exam and course accreditation.
{% endhint %}

***

<p align="center"><a href="https://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses.md" class="button secondary" data-icon="arrow-left">Back to Speciality Courses</a></p>


---

# 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://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses/semantic-model-editor.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.
