Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

Ideas

Showing 147 of 1403

Data Locking

Challenge: Currently users are allowed to save/ post data to the closed periods. Eg: 2022.Dec, financial report is approved and published. Users are not supposed to alter/ change this data. However, currently in Jedox it is possible.
about 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Planned

Total in Jedox drill through

We have a customer who is very happy with the drill through functionality in Jedox. It pulls out all the transactions that makes up the number in the cube cell but it doesn't show the sum of all the lines. Is is possible to add the total or have i...
12 months ago in Jedox Platform / In-Memory DB 2 Already exists

Sort Rules of a cube with Drag and Drop

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

Aggregate lists of elements for each dimension in PALO.DATA functions instead of single.

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,
over 6 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Rule Editor usability/GUI - grouping in folders

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...
over 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

Additional argument in PALO.DATA function to omit hashtag (#) sign for data splashing

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 #.
over 6 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

To enable users to lock data at month and version dimension for fincon model

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

HR - move data from a new position to an employee

Add the possibility to plan by new positions instead of employees and then to move the data from the new position to the employee. Currently I can add a new position in the employee dimension. e.g. I am looking for a new IT system administrator. A...
about 1 year ago in Jedox Solutions / Human Resources 0 Planned

Splashing for string elements

Possibility to splash a string to aggregated cell so every base cell will have the same string afterwards. Practically this would mean adding support for splashing strings via splash operation ! and also adding support for copy operation with stri...
over 6 years ago in Jedox Platform / In-Memory DB 1 Not Planned

Cancel / Abort Calculation in Jedox Web V2

Unfortunately there was no official statement to my comment on topic http://feedback.jedox.com/forums/220460-jedox-feature-voting-tool?query=cancel Thats why I opened the same feature reqest again. The main problem is, that during calculations...
over 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration