Ideas

The user is confused, when adding a new report, or published an existing one, that the report does not show in the menu. When a user adds new reports or publishes existing ones, the user wants to get a pup-up message with a hint that the user must...

Account for Different Fiscal years e.g. 1st of July to 30th of June 

it could be usefull to have a new log level "Info+" : sometimes it is useful to log informations that are relevant and that you want to catch attention to, but you do not want to cause a warning. A new method "LOG.infoPlus()" or something would be...

Create an additional allocation to allocate HR cost centers with Finance cost centers instead of a 1:1 cost allocation. e.g. create a dimension to store the possibilities/allocations, so a nightly job can easily be added.

Wenn performing a load of a cube with drillthrough parallel load a log line states : Number of rows in table "<schema>"."table" changed from xxx to yyy the query performed to do that is select count(*) from <schema>.<table> thus ...

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

Hello, the idea is to have a connection type Audit that enables us to extract all audit information for a specific cube. Also it should be possible to select if the extract is as ID or as element name from the dimensions. This is necessary for sev...

Description: Jedox currently does not support line‑item level granularity out‑of‑the‑box. When a user needs to enter multiple records on the same dimensional intersection (e.g., multiple transactions for the same Cost Center × Account), the only a...

When loading a dimension, attribute values can be loaded at the same time. But what if some of those attributes are watched by SVS ? This would be helpful to be able to deactivate the SVS Events for dimension loads like in the cube loads

Scenario:There is a long running ETL job and the Jedox server or part of services went down or "crashes". After the (re-)start of the components/services the ETL jobs are marked as failed or aborted. Here there is need for a feature or a new optio...