My ideas

In planning reports I want to compare my budget with the Actuals of last year. I do not want to view the budget of last year as it is outdated. Please introduce the possibility to show in dynatables different versions and years. So Actual 2023 and...

This idea is more in regards to the infrastructure, not Platform, but there's no feature request category for infrastructure. The customer wants to limit crashes to a report instead of the entire instance. That may not be possible. But, an idea co...

current description of logs are very technical which is not easily understandable by users. To enable self-sufficient to customers by having logs description to be more user friendly.

The Drill By feature is very useful, but it only reports accurately on filtered Dimensions. If you have filtered on a Virtual Dimension, it is ignored, hence Drill By does not report the correct filtered value.

It would be pretty cool if the confirmation dialog in an action button could process html. This would make the dialog much more user-friendly, instead of just a flat text as it is now.

Lists are a great way to make better use of views accross the system. However, in planning situations it is most often necessaary to compute whether or not a cell is open for data entry. The style/format of the modeler is not sufficient there. For...

Currently there are only the element codes available for dynatables aka views. Would be nice to also have the option to show attributes or aliases instead.

Please review the created User Access Management by some Consulting members and discuss which features should be added. Like ETL loads to upload the dimension rights, etc.

An example cube with rules (currency conversion, version blending, hr headcount rule, etc) would be great.

When you have created an input template, you cannot use trace cell on non input cells. It works find on input ready cells. I do however often find it more relevant to trace the calculated cells, which is typically not input relevant.