> 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/10.2-analytics/data-source-model-editor-cp/edit-multidimensional-data-source-models/assign-time-dimension-properties.md).

# Assign time dimension properties

Typically, you might sort your data by year or month. However, by designating a time dimension in the Data Source Model Editor, you can filter on a variety of date ranges and relative date options, such as previous periods, before \[a user-defined period], after \[a user-defined period], current period, or next period.

Analyzer supports many types of relative date filters. To apply them to a level of a time hierarchy, you need to define the time-specific properties for that level. This is because each data warehouse implementation may have a different date format and set of time hierarchy levels.

These steps show you how to assign a time property to a dimension in a multidimensional model.

1. Within the Data Source Model Editor, click the **Analysis** tab.
2. Select the dimension you want to assign as a time dimension.
3. Within the **Properties** pane on the right, click the **Time Dimension** box to assign the dimension as a time dimension.
4. Expand the dimension to display its hierarchy, then expand the hierarchy to display its levels. Choose the level for which you want to assign time dimension properties.

   The properties of the level display in the **Properties** pane.

   The options for **Time Level Type** and **Source Column Format** do not display for a child-level if the time dimension property is not set for its parent-dimension.
5. Set the **Time Level Type** and **Source Column Format** to match the format of your data. The **Time Level Type** and **Source Column Format** must match the format of the data stored in your data source for relative date filtering to work properly in Analyzer. This does not affect how your values display. For more information regarding the time level types and formats, see **Pentaho Schema Workbench** for details.


---

# 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/10.2-analytics/data-source-model-editor-cp/edit-multidimensional-data-source-models/assign-time-dimension-properties.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.