Ideas

currently this is far too small, we need to login every time

What it is: Scale performance, while having more dimensions in the database/ cube. Challenge: While having more dimensions (14-17) to the cube, runtime for complex logics, especially consolidation rules are timing out. Use Case: Matrix Consolidati...

The goal is to separate Delete and Download the database from modeler to avoid accidental deletition of database.

Provide support for creating Box-and-Whisker Chart (aka “Box Plot”): a more generic and robust version of a Candlestick Chart meant to illustrate different dispersion ranges of data (e.g., quartiles, deciles) around a mean or median. Please review...

Currently the outcome leads to confusion

For Excel export (as is already the case with PDF export) it should be possible to export multiple frames at the same time. It should behave in the same way as PDF export with frames. So "use for export" should have the same effect on the Excel e...

Currently, the planning assistant is only enabled one selecting one cell and the undo capability is not part of the Planning Assistant. It will be really nice to include Undo capability to the Planning Assistant and allow users to apply it to mult...

For spot data checks, I find it long to switch from modeler to designer, create a spreadsheet, edit the spreadsheet, create a view. I would expect a direct view from Modeler.

We have lots of groups and folders and maintenance is heavy. Each time a new group is created, we have to review almost all secured folders. My suggestion would be to manage this through cube rules.

In the CubeSliceCopy load, if a single record fails, the whole process fails. There should be an additional option "Continue on error". This would still log an error in the log for that specific record, but it would allow the rest of the load to c...