Ideas

Currently if a dimension name is long, you cannot always see it in the PoV.

Currently, the weight of the elements will always be set to +1 after uploading an Excel file into the dimension, regardless if you set a different weight for those elements prior to uploading. This behaviour is encountered when using 'Full hierarc...

Currently only the filter criteria that are defined in the POV area are displayed. All preset filters that are not visible, such as the “Actual” in the example below, are not shown. The subtitle is not necessarily useful, since it only shows what ...

The Show menu would allow users to toggle to a different attribute displayed for the view. The menu would display the list of attributes (like the sort by attribute menu) that the user could choose from to change the displayed alias.

In Excel COM Add-in, there is the ability to 'keep' a single or multiple elements. This should be extended to the web as part of the view-filtering feature.

Implement a balance sheeet projection comparable within or compatible to the Integrated Financial Planning model. The projection should work as the Projected Balance Sheet model but should support the Partner Entity dimension.

Extend the storage to capture inventory from intercompany trades by products or product groups. Data should be captured from input screens. Capture percentage margin by a percentage margin by the legal entity, partner entity and product combinatio...

Processing speed for embedded palo.eprev or palo.enext functions within rules are very slow especially when more than one function exists in a rule. For demographic modelling where age in the current year depends on age(-1) in year(-1) the time to...

Currently we have a very complex model that is depending a lot on the SVS server. But we noticed that with the amount of interaction between the spreadsheet and SVS server sometimes the SVS server "freezes". In order to solve this we must restart ...

I would like to propose being able to make user defined queries for rule templates. I'm thinking exposing it from the integrator which could generate the query, and then expose the result to the rules engine. This would create a much more flexible...