Ideas

Extending the splashing command ! to splash only on base cells that are populated would allow further flexibility to jedox splashing features.

This is helpful with large/deep hierarchies to establish relationships within rules

In Olap Lists, if you want to retrieve an attribute for a List block which uses a dynamic expression (e.g. reference to dimension in the View "POV"), you have to enter a formula-like expression which requires escaping quotes etc. To simplify this ...

Add a demo dashboard to the starter kit IFP.

Create new In-Memory DB database script commands to maintain parent child relations. The scenarios below cannot not be handled with the existing ELEMENT_APPEND script function at the moment. Use cases: 1. Remove one particular parent-child relatio...

OLAP Server contains storage for persisting cell properties (e.g. number format, foreground color, note,...). This can be used to centrally define and store properties of the cell and then later be shared on different frontends e.g. define rule th...

A way to analyze a cube from the perspective of data volumes in particular areas of a model. If a client splashes into an empty area of a cube and causes data explosion (huge populated cells, slowdown, etc,etc) , we require a way from an admin per...

it would ease audit process when e.g. users turn accidentally base elements to consolidated ones (what provokes data losses)

When I close the rule editor without saving changed, the dialog asks "Do you want to save this rule" with 2 options "Yes" and "No". It would be very useful to have the option "Cancel" to continue rule editing.

For this right object you should be able to create, edit and delete private stored views, without having the ability to delete global views. For example, this new right would be able to do what W-right can currently do and, in addition to this, al...