# Create a shared dimension

Create a shared dimension for aggregated data that you want to use consistently across multiple cubes in the same semantic model. For example, a shared time dimension with annotations like Year, Month, and Week can be linked to several cubes, ensuring uniform time-based analysis. 

Complete the following steps to add a table or view as a shared dimension of a cube: 

1. Log into the **Pentaho User Console** (PUC).  
2. Open the Semantic Model Editor by taking one of the following actions:

   * If you are using the Modern Design of PUC, in the menu on the left side of the page, click **Semantic Model Editor**.
   * If you are using the Classic Design of PUC, click **File** > **Semantic Model Editor**. 

   The **Semantic Model Editor** opens. 
3. Open the semantic model to which you are adding a shared dimension by completing the following sub steps: 
   1. In the **Semantic Models** list, navigate to the model you want to open by searching or scrolling through the list. 
   2. Click **Open**. The model opens in the canvas. 
4. In the **Data Source** tab, navigate to the table or view that you want to use as a shared dimension. 
5. (Optional) To preview data in the table or view, click the **Preview** icon next to the table or view. The **Preview Data** panel opens. You can take one or more of the following additional actions while previewing the data: 

   * Hover over a column header to see metadata information for that column.
   * Click a column header to sort the table by the data in that column. 
   * Click the Preview icon again to close the Preview Data panel. 

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> You can preview one table or view at a time. By default, the maximum number of rows shown is 100. The administrator can change the maximum value by editing the <code>row-limit</code> property in the <code>application.properties</code> file, located in: <code>\Pentaho\server\pentaho-server\pentaho-solutions\system\semantic-model-editor</code>. The administrator must restart the Server for the new row value maximum to take effect.</p></div>
6. Drag and hold the table or view over a blank area of the canvas until the **Do you want to:** dialog opens and then drop the table or view onto the **Use as Shared Dimension** option. A shared dimension is created with one hierarchy that has one level, and the **Shared Dimension Editor** window opens with the top position of the Dimension tree selected.&#x20;
7. Edit options for the shared dimension by completing the following sub steps:&#x20;
   1. In the **Dimension Name** section, enter a unique **Name**.&#x20;
   2. In the **Dimension Type** section, select one of the following options for the Type of dimension you want to use:&#x20;

      <table><thead><tr><th width="174.444580078125">Option </th><th>Description </th></tr></thead><tbody><tr><td>StandardDimension </td><td>A dimension used for basic analysis. <strong>StandardDimension</strong> is the default value. </td></tr><tr><td>TimeDimension </td><td>A dimension used for time-based analysis. A time dimension might have annotations like Year, Month, and Week. </td></tr></tbody></table>
8. (Optional) Expand the **Optional Information** section, and then select a value for **Visible** to specify whether the shared dimension element is visible in the **Pentaho Analyzer** design environment. Elements that are not visible cannot be accessed directly in **Pentaho Analyzer** to use in reports. However, hidden elements can still be used to build expressions and conditions that are internally evaluated by the Mondrian engine for reporting. The default value is **true**.&#x20;
9. (Optional) Expand the **Describe Dimension** section and edit one or more of the following options:&#x20;

   <table><thead><tr><th width="129.7777099609375">Option </th><th>Description </th></tr></thead><tbody><tr><td>Caption </td><td>String of text that is displayed instead of the shared dimension's name. You can use captions to provide a user-friendly label for reports or for localization so that the shared dimension's name appears in the local language. </td></tr><tr><td>Description </td><td>Description of the cube. </td></tr></tbody></table>
10. In the **Dimension** tree, select the hierarchy that was created when you added the dimension.&#x20;

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: You can add more than one hierarchy to a dimension. </p></div>
11. Edit the options for the hierarchy by completing the following sub steps:&#x20;
    1. In the Hierarchy Name section, enter a unique Name.

       <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: All hierarchies in a shared dimension must have a unique name. An empty name is considered unique and can be used only once for a hierarchy in the shared dimension.</p></div>
    2. In the **Mandatory Data** section, enter information for the following options:

       <table><thead><tr><th width="140.66650390625">Option </th><th>Description </th></tr></thead><tbody><tr><td>Source Table* </td><td>Table used as the source of data for the hierarchy. </td></tr><tr><td>Alias </td><td>Unique text string used as an alias for the table in queries. You can assign an alias to a table used in multiple hierarchies to ensure that SQL queries work correctly. By default, the table name is used in queries. </td></tr><tr><td>Hierarchy Key </td><td>Unique text string that connects the table or view produced by the hierarchy to the cube’s fact table, which enables accurate joins between dimension data and fact data during query execution. </td></tr><tr><td>Has All* </td><td>Value indicating whether the hierarchy has an “all” member. The "all" member is the parent of all other hierarchy members, representing the total. The default value is <strong>true</strong>. </td></tr></tbody></table>

       \*Required field&#x20;
    3. (Optional) Expand the **Optional Information** section and edit one or more of the following options:&#x20;

       <table><thead><tr><th width="173.5555419921875">Option </th><th>Description </th></tr></thead><tbody><tr><td>Visible </td><td>Value indicating whether the hierarchy element is visible in the <strong>Pentaho Analyzer</strong> design environment. Elements that are not visible cannot be accessed directly in <strong>Pentaho Analyzer</strong> to use in reports. However, hidden elements can still be used to build expressions and conditions that are internally evaluated by the Mondrian engine for reporting. The default value is <strong>true</strong>. </td></tr><tr><td>All Member Name </td><td>Name of the “all” member if the hierarchy has an “all” member. Default value is <strong>All hierarchyName.</strong> For example, <strong>All Store.</strong> </td></tr><tr><td>All Member Caption </td><td>A string of text that is displayed instead of the "all” member’s name. You can use captions to provide a user-friendly label for reports or for localization so that the "all” member’s name appears in the local language. </td></tr><tr><td>All Level Name </td><td>Name of the “all” level. The “all” level is the topmost level in a hierarchy and contains only the “all” member, which represents the total aggregation of all members in the hierarchy below it. </td></tr><tr><td>Default Member </td><td>Default member of the hierarchy. </td></tr><tr><td>Member Reader Class </td><td><p>Name of the custom reader class. The custom reader class must implement the <code>mondrian.rolap.MemberReader</code> interface.  </p><p> </p><p>A custom reader class is a user-defined Java class that extends Mondrian’s default behavior for reading members of a dimension so that you can customize how dimension members are retrieved and displayed in OLAP queries.  </p></td></tr><tr><td>Origin </td><td><p>A bit mask that determines the source of the hierarchy: </p><ul><li>MD_ORIGIN_USER_DEFINED identifies levels in a user defined hierarchy (0x0000001). </li><li>MD_ORIGIN_ATTRIBUTE identifies levels in an attribute hierarchy (0x0000002). </li><li>MD_ORIGIN_INTERNAL identifies levels in attribute hierarchies that are not enabled (0x0000004). </li><li>MD_ORIGIN_KEY_ATTRIBUTE identifies levels in a key attribute hierarchy (0x0000008). </li></ul><p>The default value is <strong>MD_ORIGIN_USER_DEFINED</strong>. For Measure the default value is <strong>MD_ORIGIN_ATTRIBUTE &#x26; MD_ORIGIN_INTERNAL (0x0000006)</strong>. </p></td></tr><tr><td>Display Folder </td><td>Folder in which to list the hierarchy for users. </td></tr><tr><td>Unique Key Level Name </td><td><p>Name of the level within the hierarchy.  </p><p> </p><p>The Unique Key Level Name is used to indicate that the given level taken together with all higher levels in the hierarchy acts as a unique alternate key, ensuring that for any unique combination of those level values there is exactly one combination of values for all levels below it. </p></td></tr></tbody></table>
    4. (Optional) Expand the Describe Hierarchy section and edit one or more of the following options:

       <table><thead><tr><th width="113.1112060546875">Option </th><th>Description </th></tr></thead><tbody><tr><td>Caption </td><td>String of text that is displayed instead of the hierarchy’s name. You can use captions to provide a user-friendly label for hierarchies or for localization so that the hierarchy’s name appears in the local language. </td></tr><tr><td>Description </td><td>Description of the hierarchy. </td></tr></tbody></table>

       &#x20;
    5. In the **Dimension** tree, select the level of the hierarchy that was created when you added the shared dimension. For example, the default level is named “Level1”.&#x20;

       <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: You can add more than one level to a shared dimension. </p></div>
12. Edit the options for the level by completing the following sub steps:&#x20;
    1. In the **Level Name** section, enter a unique **Name**.&#x20;

       <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: All levels in a hierarchy must have a unique name. An empty name is considered unique and can be used only once for a level in the shared dimension. </p></div>
    2. In the **Level Source** section, select a value for one or more of the following options:&#x20;

       <table><thead><tr><th width="123.77783203125">Option </th><th>Description </th></tr></thead><tbody><tr><td>Source Table </td><td>Table that is the source for the level. </td></tr><tr><td>Column </td><td>Column of the source table that you want to use for the level.  If a column is not selected, a <code>KeyExpression</code> must be defined in the Advanced mode instead or an error occurs when you try to save the model. For details, see <a href="/pages/EQsu44rlUDmwreD5UqpH">Advanced mode</a>.</td></tr></tbody></table>
    3. In the **Relevant Information** section, edit one or more of the following options:

       <table><thead><tr><th width="148.6668701171875">Option </th><th>Description </th></tr></thead><tbody><tr><td>Name Column </td><td><p>Column of the table that contains the user identifier of the level.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Instead of selecting a specific column, you can define a <code>NameExpression</code> in the <code>Level</code> element of a SQL expression to use as the user identifier. For details, see <a href="https://open-2v.gitbook.com/~space/dbSFXbJFiObHB299lSSa/~/changes/t2kt8ssMcRL9ysypKbfv/~gitbook/pdf?back=false&#x26;only=yes&#x26;page=BN8aCJ7V1POiHJqh8Hrr#pdf-page-EQsu44rlUDmwreD5UqpH">Advanced mode</a>.</p></div></td></tr><tr><td>Ordinal Column </td><td><p>Column of the table that contains the member ordinals for the level. </p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> If the Ordinal Column is not specified, the key column is used for ordering. Instead of selecting a specific column, you can define an <code>OrdinalExpression</code> in the <code>Level</code> element of a SQL expression to use for ordering. For details, see <a href="https://open-2v.gitbook.com/~space/dbSFXbJFiObHB299lSSa/~/changes/t2kt8ssMcRL9ysypKbfv/~gitbook/pdf?back=false&#x26;only=yes&#x26;page=BN8aCJ7V1POiHJqh8Hrr#pdf-page-EQsu44rlUDmwreD5UqpH">Advanced mode</a></p></div></td></tr></tbody></table>

       &#x20;
    4. (Optional) Expand the **Optional Information** section and edit one or more of the following options:&#x20;

       <table><thead><tr><th width="206.4443359375">Option </th><th>Description </th></tr></thead><tbody><tr><td>Visible</td><td>Value indicating whether the level element is visible in the <strong>Pentaho Analyzer</strong> design environment. Elements that are not visible cannot be accessed directly in <strong>Pentaho Analyzer</strong> to use in reports. However, hidden elements can still be used to build expressions and conditions that are internally evaluated by the Mondrian engine for reporting. The default value is <strong>true</strong>. </td></tr><tr><td>Approximate Row Count  </td><td>Estimated number of members in the level. Setting an approximate row count can improve performance. </td></tr><tr><td>Null Parent Value  </td><td>Value that identifies null parents in a parent-child hierarchy. Typical values are NULL and 0. </td></tr><tr><td>Key Column Type  </td><td><p>The type of data in the key column for the level. Types of data include STRING, NUMERIC, INTEGER, BOOLEAN, DATE, TIME, and TIMESTAMP. </p><p> </p><p>When generating SQL statements, Mondrian encloses values for String columns in quotation marks but leaves values for Integer and Numeric columns un-quoted. Date, Time, and Timestamp values are quoted according to the SQL dialect. For a SQL-compliant dialect, the values appear prefixed by their type name, for example, DATE '2006-06-01'. </p></td></tr><tr><td>Internal Type  </td><td><p>The Java type that Mondrian uses to store the level's key column. Types include INT, LONG, OBJECT, and STRING.  </p><p> </p><p>The Internal Type value also determines the JDBC method that Mondrian calls to retrieve the column. For example, if the Java type is INT, Mondrian calls ResultSet.getInt(int). </p><p> </p><p>Usually, the Internal Type attribute is not needed, because Mondrian chooses a type based on the type of database column. </p></td></tr><tr><td>Unique Members  </td><td>Value that indicates whether members are unique across all parents in the level. For example, zip codes are unique across all states. Members of the first level are always unique. The default value is <strong>false</strong>. </td></tr><tr><td>Level Type  </td><td>Value that indicates whether the level is a regular or a time-related level. The level type is important for time-related functions such as YTD (year-to-date). The default value is <strong>Regular</strong>. </td></tr><tr><td>Hide Member If  </td><td><p>Value that indicates when a member of the level is hidden.  </p><ul><li><strong>Never</strong>: Member is never hidden. </li><li><strong>IfBlankName</strong>: Member is hidden if its name is null or empty. </li><li><strong>IfParentsName</strong>: Member is hidden if its name matches the parent’s name. </li></ul><p>The default value is <strong>Never</strong>. </p></td></tr><tr><td>Formatter Class  </td><td><p>Formatter class name for the member labels displayed. The class must implement the <code>mondrian.olap.MemberFormatter</code> interface. </p><p> </p><p>A formatter class is a user-defined Java class for customizing how values are displayed so that you can format data beyond default settings, such as applying custom date formats, currency symbols, or localized labels. </p></td></tr><tr><td>Caption Column  </td><td><p>The name of the column that holds the caption for members. </p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Instead of selecting a specific column, you can define a <code>CaptionExpression</code> in the <code>Level</code> element of a SQL expression to use as the caption. For details, see <a href="https://open-2v.gitbook.com/~space/dbSFXbJFiObHB299lSSa/~/changes/t2kt8ssMcRL9ysypKbfv/~gitbook/pdf?back=false&#x26;only=yes&#x26;page=BN8aCJ7V1POiHJqh8Hrr#pdf-page-EQsu44rlUDmwreD5UqpH">Advanced mode</a>.</p></div></td></tr><tr><td>Parent Column  </td><td><p>Parent in the transitive closure of a parent-child hierarchy. </p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Instead of selecting a specific column, you can define a <code>ParentExpression</code> in the <code>Level</code> element of a SQL expression to use as the parent. For details, see <a href="https://open-2v.gitbook.com/~space/dbSFXbJFiObHB299lSSa/~/changes/t2kt8ssMcRL9ysypKbfv/~gitbook/pdf?back=false&#x26;only=yes&#x26;page=BN8aCJ7V1POiHJqh8Hrr#pdf-page-EQsu44rlUDmwreD5UqpH">Advanced mode</a>.</p></div></td></tr></tbody></table>

       &#x20;
    5. (Optional) Expand the Describe Level section and edit one or more of the following fields:

       <table><thead><tr><th width="123.7777099609375">Option </th><th>Description </th></tr></thead><tbody><tr><td>Caption </td><td>String of text that is displayed instead of the level’s name. You can use captions to provide a user-friendly label for reports or for localization so that the level’s name appears in the local language.</td></tr><tr><td>Description </td><td>Description of the level. </td></tr></tbody></table>
13. Click **Apply**. The shared dimension is created and added as a new node on the Canvas, in the semantic model.&#x20;
14. Click **Save** to save changes to the model.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model/create-a-shared-dimension.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.