In-Memory DB

Overview: Currently, Jedox’s rolling forecasting setup primarily supports historical or past periods, limiting the ability to plan dynamically for future months. To support more agile and forward-looking planning, it is recommended to introduce a ...

Decimal symbols are currently linked to the user-locale. English setting will give a dot (.) as decimal symbol whereas the Dutch setting, for example, will give a comma (,) This feature works on the screens/reports, but this does not happen with ...

Actually it is only possible to move a single rule up or down line by line which is extremely annoying when I need to move a few rules by many lines.Proposal is to select multiple rules and have the option to "move to position no. xx"

In order to create a backup of a database one has to download and the upload the database. This should be possible with one step only. Like the duplicate function for Integrator projects.

Currently, in the PALO.DFILTER function, filtering based on a string value is limited to only one specific value at a time (e.g., = "Comment a"). This limitation restricts the ability to filter multiple values or patterns dynamically. It would be ...

Adding a description field to the Database would allow better documentation of the type of data in the database. Dimension and Cube descriptors are helpful, and this would enhance the documentation. Tags would also be useful (like Dimension "Type"...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.

Currently there are two options when you click on the "Export" button in the rules area of a cube: 1) Database Script / 2) Text File. It looks like these are two options for the same outcome. But actually it's not: 2) extracts the rules only / 1) ...

In the modeler, if I select a cube or dimension, I would like to see where in my application they are used: In which workbook In which ETL step In which rule etc Currently, this is quite a manual exercise and practically impossible to gras...

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,