Ideas

Setting of a language should automatically be recognized in the views set-up panel and pre-populate/re-select the correct element name if a translation alias is avaiable: Make the alias a variable and related to the system languages, so dimensions...

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

Add data validation to the attributes listed in the Add Element form when popup form is selected. It should be activated when using "cell range" as the target to populate the form. If there is data validation on that cell, it should use that data ...

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

Perhaps use a different Icon and use the name of the subset in the text of the selection

1. With a Parse Error in RULE you get an errormessage referring to a position number in the rule's string. But the editor never displayes the current position as a number, which would help locate the error. Or highlight the error position! E.g: u...

in #_GROUP_DIMENSION_ cube this is really complex to know what is the right for a certain group since it can be inherited from upper levels, for instance: Europe N West France R this would be great to be able to see that, say using a "flag" t...

Currently rules are calculated in the moment when the user queries the data. It would be great to have the option to shift the timing to the point when the user changes data. So the result of the calculation would be stored/persisted when the use...