Ideas

Allowing Actions on Labels were initially disallowed because strictly speaking Labels should just be a visual object. However, labels have a lot more formatting capabilities than buttons, combo boxes or lists. For example, vertical centering, word...

When we setup a security at dimension level, some users are set as N to prevent an access. In report spreadsheet, the element is displayed in a single cell (not using dynarange). But when non eligible user open the report, the particular element t...

When you mark a cell as Writable in a web report it by default shows the L bracket. This is ugly, especially on a large blank area. The work around is to change the format of the cell, but why force everyone to go change the format. It is also not...

For Excel Cell data, the "Read-only" setting restricts data submission rather than input at the UI level, meaning users can attempt to enter values but will receive an error upon submission. We request to improve usability by visually disabling in...

If there is a problem with data entries in Excel and this problem comes from the SVS Server, the respective error or warning message is not shown. Instead, a generic error message is presented to the user. It would make sense to actually show the ...

Based on a stylesheet the button color should be adjustable. Means if we create models for our customers with color code blue and the customer colors are red: it is a lot of work to adjust each button color on all reports manually instead to have ...

Description: Jedox currently does not support line‑item level granularity out‑of‑the‑box. When a user needs to enter multiple records on the same dimensional intersection (e.g., multiple transactions for the same Cost Center × Account), the only a...

For the moment, we can't have a scheduler action and then a download file action. (The download action is lauched before the end of the scheduler). It will be interresting to have the option "Wait for job to be done" (like with integrator action) ...

In-place editing of values in ODBCDATA cells should be possible (similar to editing values in PALO.DATA but for data from ODBC source). For this additional SQL UPDATE statement has to be defined when defining relational DynaRange #14001

If you need the same macro in different workbooks you currently have only 2 options: - copy & paste the macro into all relevant workbooks - use external PHP files. But external PHP files are not really handy when you want to provide deploymen...