Ideas

Users would benefit from an easy way to set up custom data validations, similar to the setup of consolidation rules. E.g. the amount on a PnL Account needs to match a movement on a BS Account.

It is not always required for an end user to see all the list elements in the columns. I will be helpful to have the ability to filter on list elements so that users can choose what they would like to see.

It would be handy to have a control over what alias we want to show in the pasteview edit screen. currently, it shows all the attributes of the dimension that exist in the data model. However, we create many such attributes for calculation/filteri...

Hi Team As per current functionality, if we want to create a filter on dimension elements in the rows, create filter dialogue shows only those dimension element which are already part of the rows. This does not help users if they want to filter di...

The System database is not accessible in the DynaRanges via the Subset Editor. The only way of accessing this database via Subsets is by manually typing the formula, which is more prone to errors. The other option here us using the "New view" func...

Currently when I plan an employee I sometimes don't understand why the numbers are not written. This could have several topics why it is not writing: - I enter FTE or salary increase before the employee startet: Employee startet 1. Oktober. But I ...

Clients often ask if we can highlight which cells can be entered into and which cannot. Of course we can work around this, but if there is a large table of details (say in a Dynarange) it adds a lot of workings to the sheet. It would really help i...

Sometimes, there are many Legal Entities at customers, paging function would be needed in reports: "Scope of consolidation", "Data collection", "Consolidation Manager", "Consolidated Financial Statement".

Please add the "User Management" report, logic and Integrator project to the BPA HR. The same as in the Foundation.

VIEWS: It would be going far beyond better analysis, if you could write back/splash input in a VIEW, even if POV Multiselect is being used with one or more dimensions. The selected elements of one dimension would temporarily be treated as siblings...