Jedox Platform

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

Create either a Groovy script or a custom-built connector to load MT940 SWIFT data to Jedox. The process would include parsing the MT940 files to extract transactional details (e.g., account balances, debits, credits, and statements) and transform...

Challenge: Predefined logic components (such as business rules, consolidation rules, or integrator jobs) are failing because users with access to the Modeler can delete dimension elements or master data that are essential for these logic processes...

The _internal_suite user gets everyone confused. Every client that is a bit less technical worries about it ("Does it take a license", "What if we delete it", "What if the password is changed" and so on and on). There is absolutely no need that I ...

- recurring enduser request - conditional formatting does not always work properly - add on in hierarchy filter or within the properties of a dyna-range - easy to implement to display certain levels with a font or background color e.g. level 1 = b...

The current function to use framesets is nice, but still a bit limited as framesets cannot be nested into each other. Sometimes you use a frameset for the overall application design - esp. to provide global menu bars and navigation structures. O...

Enter an invalid search term in the Canvas search bar. Observe that system just shows a blank box, no warning message. Expected behavior: If the user's search term does not yield any result, the system should ideally show an error message such as ...

It would be great to be able to set up a button or to have the option somewhere in a report to drilldown the whole Dynarange in one click. It can be annoying sometime for the users to have to drilldown all the lines one by one when they want to ha...

Currently, when changing the cube layout the dimensions are sorted by creation date. With a long list of dimensions it takes a while to find the correct dimension. Please change the dimensions to alphabetical order.

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