I would like to have the opportunity of setting the print area within reports dynamically, meaning that I have the possibility of setting a variable or named range in the section "Table".
Sometimes this could be useful to be able to pin more than 1 view in Integrator (for instance up to 3) My current use case is that I have e.g. a FieldTransform (let's call it "Target"), I want a function that is in another one component (let's nam...
Because of performance degrades fast in jedox web, on rather small input templates, I would like to propose "Non-Volatile" function. Consider a function that makes other functions non-volatile, or at least does not update when user input plan data...
Dynamic implementation of report rights by Integrator
As an implementation expert or power user I would like to define which user group gets access to which report. Example: admin gets rights to all 30 reports, planner gets access to 20 reports and viewer gets access to 5 reports. Currently it is pos...
String values that match some patterns can be filtered using PALO.DFILTER
Currently, PALO.DFILTER can work with string values only when using "=" operator (Also, when using ">" operator,some string values are filtered lexicographically,though). But, it does not support pattern matching. In addition,">" operator do...
Hide ETL projects in Integrator if (reading) access is only granted with non-Integrator group
When a user is assigned to groups with different roles, where one role (e.g. designer) has access to Integrator and another (e.g. editor) has only access to reports, rights for ETL projects are “combined”. E.g. the group with access to Integrator ...
Hide Reports in Designer if (reading) access is only granted with non-Designer group
When a user is assigned to groups with different roles, where one role (e.g. designer) has access to Designer and another (e.g. editor) has only access to Reports section, rights for folder groups / reports are “combined”. E.g. the group with acce...
New Subset option: Show all missing parents/ancestors up to root level
When filtering e.g. by free text name or attribute, it's very typical that the result might only show base elements or elements from different levels. In dimensions, consolidated elements (i.e. parents/ancestors) usually provide additional, useful...
The possibilities to influence user authorisation in the ODATA Hub are currently very limited. When it comes to integrating Jedox into an existing data architecture, the ODATA Hub with the REST interface is a good option. However, it is currently ...