> 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/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/customize-pdi-data-explorer/use-discrete-axis-for-line-area-and-scatter-charts/set-discrete-axes-for-time-dimensions-in-pdi-data-explorer.md).

# Set discrete axes for time dimensions in PDI Data Explorer

To display Time dimensions in the line and area visualizations on a discrete axis, perform the following steps:

1. Navigate to the `pentaho/design-tools/data-integration/system/karaf/config/web-client` system directory and open the `config.js` file with any text editor.
2. Locate the `Example Rule 9 - Disable the continuous date strategy` code block, as shown in this example:

   ```javascript
   // Example Rule 9 - Disable the continuous date strategy, to revert
   // to the old behavior (Before 8.1) that represents Time dimensions in a discrete axis.
   /*
   {
     select: { module: "pentaho/visual/role/adaptation/EntityWithTimeIntervalKeyStrategy" },
     apply: { isBrowsable: false }
   },
   */
   ```
3. Remove the `/*` marker and the `*/` marker to uncomment the `EntityWithTimeIntervalKeyStrategy` command.
4. Save and close the file, then refresh the browser.

Your line and area visualizations will display Time dimensions on a discrete axis and the scatter visualization will not be able to provide Time dimensions.


---

# 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/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/customize-pdi-data-explorer/use-discrete-axis-for-line-area-and-scatter-charts/set-discrete-axes-for-time-dimensions-in-pdi-data-explorer.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.
