Ability to set value to a range of cells. Currently this can be done by setting separate actions for each target cell. It would be nice to have functionality to set a range of cells to the desired value to run multiple If then logics based on valu...
Library of pre-generated button/checkboxes examples
During my last project, the customer mentioned that would be great if we have a list of button examples so she/he can choose one of them. Also, it should look like "2020s", not a 90s graphic. So maybe the idea can be like we have for the cell type...
Balance Carry Forward for planning periods longer than one year
Idea was raised from Mark Schildgen Incorporate a Balance Forward for a planning horizon which is longer than one year. To keep this performant it is probably not necessary to plan all years on a monthly base, instead of that it could be a proper ...
Designed web reports for master data maintenance to the Finanical Consolidation model
Provide designed web reports to add, inspect, modify and remove master data items such as legal entities, scopes, accounts, transaction types, currencies, etc.
Only stop the services when no Integrator job is running
We have implemented on our own systems that the restart of the services, which is carried out during the backup, only takes place when an ETL job is no longer running. This is also necessary for the cloud.
Too Big Splash Warning incorrectly focuses Planning Assistant on "Like" not "Splash"
When you attempt a number that impacts many cells, Jedox give you a warning that you are potentially impacting more then you intend. It gives you the option through the Planning Assistant to modify it. However, when you delete a large number with ...
Sometimes the large subset option is not suitable for all users (e.g. 1 user needs it because a huge amount of elements are to be displayed, and another not) ; the possibility to make the option variable would be really helpful
Shared Dimensions / rule performance between different databases
The concept of Jedox models is really great to split a big EPM applicationinto different manageable modules (modularization). Example: You could have 3 different models for planning sales of products, production of products purchasing of material ...
when a component refers to several sources (e.g. FieldTransform with n lookups) it would be nice to highlight the "main" source in the flowchart (for instance a bold line)