Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 126 of 1315

In a cube with persisted relational ETL drillthrough data, allow cube-drilldown in areas where no relational data is available.

As of version 2023.4, the Jedox drillthrough capabilities have become a native functionality outside of the SVS scripts. In the KB it says for the mode automatic: drills through if ETL is available, or else drills down. This suggest that right-cli...
8 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Modification for Actual Months rule template

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, Actual Months rule template, "If fiscal year is used, it returns a list of the first months of each fiscal year." The partner wants the rule template to give t...
8 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Improve server performance with Configuration Option to Disable Loading Inactive Databases on server startup

We have clients who archive previous databases from prior years (but these are still saved on the Jedox server so they can access the database if needed). By default, Jedox loads all databases into memory at server startup. This means the inactive...
9 months ago in Jedox Platform / In-Memory DB 1 Future Consideration

In Modeller group databases by model to which they belong.

In Modeler we often have many databases with different names. In our situation, we have several teams working on separate projects.Most projects are grouped via Models functionality where the Model groups Reports, Integrator jobs, and Scheduler ta...
9 months ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 0 Future Consideration

Keep full trace in audit trail.

When planning functions such as splashing or copy are used, the audit trail does not keep a complete record of what has been entered. For example, executing the following command “copy Actual;2023” only records the following NUMERIC_VALUE: 12345,...
11 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

OLAP access restrictions

Currently, cloud console users can create security rules that restrict inbound traffic, allowing connections only for the specified IP addresses or IP ranges (IP whitelisting). See also: https://knowledgebase.jedox.com/jedox/maintenance/cloud-cons...
about 1 year ago in Jedox Platform / Cloud Console & Administration / In-Memory DB 0 Already exists

Active by default - option "Allow multiple parents with a single hierarchy" in Dimension upload wizard"

It can be less dangerous to set the option "Allow multiple parents with a single hierarchy" active by default when elements are uploaded to the dimension. We have encountered several issues when hierarchies with multuple parents were destroyed, be...
about 1 year ago in Jedox Platform / In-Memory DB 1 Future Consideration

Perform complex consolidation logics with more dimensions (14-17)

What it is: Scale performance, while having more dimensions in the database/ cube. Challenge: While having more dimensions (14-17) to the cube, runtime for complex logics, especially consolidation rules are timing out. Use Case: Matrix Consolidati...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

Create alias for dimension name

For models, some dimension names come as part of the model and the dimension name shouldn't be changed. Therefore the request is for a platform functionality for dimensions to also have aliases, so that the dimension can be referred to by its alia...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

Automatically update Olap Lists when a dimension name is changed

Currently, when renaming a dimension, a List where this dimension is used isn't automatically updated, and then has to be manually recreated. It would be nice if this could be done automatically whenever a dimension name is changed.
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration