Ideas

Currently I used several checkboxes and macro for disable checkboxes and guarantee than only one checkbox is selected when one checkbox is selected.

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

In the COM add-in we already support multiple languages - predefined in the modeller.This will be needed for the Microsoft 365 add-ins as well - elements, dimensions, cubes etc. should be automatically translated due to the Internalization section...

After an action is executed, there should be a possibility to send an email. The email parameters should include: To email address (or @jedoxUserName if the user is a jedox user). From/Send email address should use system settings. Subject line Me...

In most BI Solutions there is a monitoring implemented that enables administrators to see the usage (e.g. clicks) on reports, starts of ETL-Jobs etc. It is highly suggested by BARC to do BI on BI by identifying unused reports to eliminate/hide the...

As a report designer I want to be able to duplicate a report/frameset/(folder)/etc to achieve copy and paste with less effort. Reports/framesets are often copied and pasted and then adjusted to create similar reports/framesets. It would help if th...

Please increase the size of some ETL- input fields, where many characters can be entered.For instance: logical expression fields; json template in JSON connections, etc.The current size is error-prone and inconvenient.

When having a few Where clauses in the sql statement, it would be helpful to see the ordinal number of the row above. Sometimes there are either quite a few lines or combined AND/ OR.

When using the flow graph, there are 2 major issues with the display: names of steps are cut at char position 20 or so, which doesn't allow me to read the full name. This would be helpful though, at least when hovering when switiching between ...

Use case: I display all base-level elements (e.g., products) in rows of a Dynatable. Current situation: When a new child element (e.g., a new product) is added to the underlying hierarchy: The row does not include the new element As a result, ...