In-Memory DB

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...

It would be very useful to have an icon or other indication which cells are being held with a Hold Statement. Currently Doohickey's/Dept 1 is being held (highlighted in Yellow), but there is not a way to determine that from visually looking. Worse...

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...

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...

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...

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,...

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...

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...

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...

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.