Ideas

When navigating through the Designer and Reports tabs, and reviewing the properties for "Groups", "Hierarchies" and "Folders" the dialog is missing the description for the element name. (Check mockup)

Many websites and SaaS applications allow a user the option to login with their LinkedIn, GMail, or similar account by aggreeing to link their login credentials. The obvious benefit to the Jedox end user would be less passwords to remember or rese...

Currently, the weight of the elements will always be set to +1 after uploading an Excel file into the dimension, regardless if you set a different weight for those elements prior to uploading. This behaviour is encountered when using 'Full hierarc...

Processing speed for embedded palo.eprev or palo.enext functions within rules are very slow especially when more than one function exists in a rule. For demographic modelling where age in the current year depends on age(-1) in year(-1) the time to...

Jedox currently displays a straight average in a pasteview report when we select multiple element in a dimension. However it would be useful to have weighted average option that the report can display . In the below example we attempted to use mul...

Some query types for rule templates return a list of elements, for example the query "Dimension element like (list)". Variables with a list result can only be used in specific places in rules and require correct syntax. However, the Rule Editor st...

When setting formats in modeller on a dimension, could we set a default format for all items and then adjust from there? In Jedox 2020.1 we have element formats. It would be great if we could set a 'default' number format and cell styles that is a...

Currently we have a very complex model that is depending a lot on the SVS server. But we noticed that with the amount of interaction between the spreadsheet and SVS server sometimes the SVS server "freezes". In order to solve this we must restart ...

I would like to propose being able to make user defined queries for rule templates. I'm thinking exposing it from the integrator which could generate the query, and then expose the result to the rules engine. This would create a much more flexible...

We have major frontend performance issues, which stems from the HIDEROW() and HDECOLUMN() functions are not performing well. However, with the current Jedox functionality, these are key to nice UI, so increasing performance would really help out.