Ability to access the Status Monitor of the Integrator using dynaranges/views (so similar to just access a cube)
For a better overview of the run Integrator jobs, we would like to be able to access their status via dynaranges/views. At the moment, the only option we have is the feedback window which opens when an Integrator job is started via a button action...
Ability to directly translate (using Alias) rgrp/fgrp ids using the database dimension from the system database to their real name
If you want to see the Alias of a rgrp/fgrp id, you need to create Integrator extracts of the System database. We would like to directly access these aliases, instead of always running an Integrator job that writes them to one of our cubes.
Allow for choosing exactly which DFilter is used with "sorting with value"
Subset editor allows for multiple DFilters, both intersecting and non-intersecting. Sort tab allows for sort by value. When there are multiple DFilters in use, customer would like to be able to select a particular DFilter only for sorting by value...
It should be possible, that the jobs in Financial Consolidation Models could run in parallel. The reason is, if you schedule normal jobs e.g. 15 min and they need about 5 min to be finished, and in between you start jobs in financial consolidation...
Integrator function to import/export a file into Designer
Jedox Integrator needs a function/load to take a file from another datasource (local neetwork drive, FTP, OneDrive, Sharepoint, etc) and load to Filemanager (Designer). Ot should be able to do the reverse as well (ie export).
Currently, you cannot use add or update load mode for an excel file that resides in JedoxFiles. This means adding additional worksheets in an existing workbook is not possible. This should be enabled.
Add the ability to create a new subset (Private or Public) in the Select Elements UI. This is where most people would want to create a quick picklist without having to go into modeler. This would really be handy(and is how TM1 does it now)
R Script logs are not returned in the cloud log files, which is hard for debugging in case a rs transformation failed during a job execution. Those log files should be included into the log session in the cloud console.