Ideas

Decimal symbols are currently linked to the user-locale. English setting will give a dot (.) as decimal symbol whereas the Dutch setting, for example, will give a comma (,) This feature works on the screens/reports, but this does not happen with ...

Today's subset editor only lets you sort elements by one criterion (element, alias, attribute, etc.). It is often necessary to sort on several criteria, for example first on an attribute and then on the name of the element. This is not possible wi...

It's necessary to add Planning Assistant to Datatable the same way as in the reports, because users don't know all the splashing commands.

Basic reporting functionalities like scaling factors, number format should be available at report level as a standard like zero suppression Users should be able to decide scaling factors on the fly if they wish to see numbers in absolute value or ...

As soon as I want to edit a view and open a specific dimension in the paste view panel, I can find the selected elements on the left hand side. I miss the information on the right hand side. This forces me to recreate the order of elements every t...

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...

It would be amazing to see a data preview on cubes in the modeler like a tabular view in the integrator with data preview and max rows. For testing and debuging I would really often use this - but now I have to download the cube each time if I wan...

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.