Ideas

Whit large implementations, where many hierarchies and cubes exists, a lot of time is spent on finding and scrolling to the hierarchies related to the cube being worked on. Although the forward and back buttons help a lot, it would also be great t...

In a time dimension, there are month and day value attributes, which are super helpful for retrieving a date range with an attribute filter etc. However, these are currently strings and therefore may not work with some comparisons and mathematical...

The suggestion is to add the following two languages as supported by Jedox Web: Polish (pl-PL) Slovak (sk_SK) This should allow the user to change the language of the UI - Jedox Web as well as to use it to translate elements/attributes/reporting i...

In the CubeSliceCopy load, if a single record fails, the whole process fails. There should be an additional option "Continue on error". This would still log an error in the log for that specific record, but it would allow the rest of the load to c...

Challenge: When multiple users are working on same file, which needs to be imported (Example: Manual Journal Entries), the files are getting overwritten by other users. Recommendation: If users can create sub folders under import folder to manage ...

Cube-to-Cube drillthrough would allow cubes to be linked logically for users and assist in data discovery. The drillthrough would use the shared dimensions for a particular drillthrough intersection to create a view on the destination cube.

This would be helpful to enable setting the target fields in a cube extract. When copying a slice to another one, I use a cube extract, then a fieldtransform where I put a constant. We could cut the FieldTransform if the target structure could be ...

The Jedox Knowledgebase is a helpful treasure chest of knowledge in my daily work. However, I do see room for optimization: 1. due to the size of the knowledgebase, searching for a topic always results in a large number of hits. This could be coun...

Global variables available across the whole platform would make integration, modeling and planning much more simple and unified. One way of doing this is with setting keys (there could be other, better ways to achieve this). Right now, setting key...

Options to add these within combobox properties. These are required to ensure users understand the context of the combobox. Currently this is done through separate pictures or labels and having the option would simplify set up.