Ideas

In Views, rows can be filtered by an attribute value (or Alias). However, if the user picked a Alias format (such as "Element name (Alias"), this can lead to result which might be unexpected. For example, when filtering for "start with" + some cha...

This functionality would be very useful for iterative calculations over the same cube rules, or for Monte Carlo scenario simulations with randomly-generated changes in specified input parameters. It could also be quite useful for AI functionality ...

In a time dimension, there are month and day value attributes, which are super helpful for retrieving a date range with an attribute filter etc. However, these are currently strings and therefore may not work with some comparisons and mathematical...

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

A virtual dimension always has a certain structure. - <attribute name>-- Total <attribute name>--- <attribute value>---- <base element>-- No <attribute name>--- <base element> While this is good enough for data ...

In Modeler in dimension attribut e.g. "Name" should be shown for multiple languages by default or based on selection & activate search functionality. Use case: Currently as a user I need to select each time I open the dimension the Name German...

Right clicking on a cube in Modeler should have and additional option: Browse. This merely brings up the same dialog/action as clicking on 'View' on the start menu. A new spreadsheet opens with the paste view dialog in edit mode. This makes it con...

Optionally adding related dimensions to the cube database script (as another check box) would greatly simplify exporting cube, particularly when transporting to other environments

In the form "New cube" the "Available dimensions" box the current cubes order is by creation date, earliest to latest (see the att. file New cube.png). In other forms the cubes' lists are ordered alphabetically (e.g. Modeler/<database>/Cubes...

Recently I have seen a lot more requirements for traceability of calculations for users. i.e. easy abiliy to understand how a value was calculated. This is coming up as a 'critical' requirement in functional requirements quite often. I know we hav...