Ideas

In order to create a backup of a database one has to download and the upload the database. This should be possible with one step only. Like the duplicate function for Integrator projects.

Currently, in the PALO.DFILTER function, filtering based on a string value is limited to only one specific value at a time (e.g., = "Comment a"). This limitation restricts the ability to filter multiple values or patterns dynamically. It would be ...

Adding a description field to the Database would allow better documentation of the type of data in the database. Dimension and Cube descriptors are helpful, and this would enhance the documentation. Tags would also be useful (like Dimension "Type"...

In the modeler, if I select a cube or dimension, I would like to see where in my application they are used: In which workbook In which ETL step In which rule etc Currently, this is quite a manual exercise and practically impossible to gras...

Currently there are two options when you click on the "Export" button in the rules area of a cube: 1) Database Script / 2) Text File. It looks like these are two options for the same outcome. But actually it's not: 2) extracts the rules only / 1) ...

Posting Journal improvement: - Response time for the posting journal report is too high - Better data validation to upload journal - Carry forward jounarls- in Lucanet only values and link to original journal to drill down

this would be really helpful to have a locking mechanism when creating elements. The use case is the following: Application where users can create new elements (e.g. Capex or Projects), for instance using a macro or actions The elements should...

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