Ideas

We want a "Time Dimension" not a generic one. It is important to have functionality for planning on rules like aggregates YTD, MTD or Day plus n days, Month + n months. Currently the Time Dimension requires a lot of work and in every singular case...

Possibility to add the separator for aggregation type -> group concatenation. It could be ,.;[]#XX!, etc. Currently, the separator by default is coma ",". Sometimes we need to do a step after where we split things in columns based on the separa...

Allow rules to be defined for a static list of elements in a dimension. {'Element1', 'Element2'}

In case of a lot of if's a case statement makes rules a lot easier to understand and to modify.

Displaying big and complex reports is too slow. Unfortunately almost all customers wants to have a reports showing maximum details... Bottleneck seems to be core.exe, not palo.exe

We have a Folder that includes 30 ETLs. Two Times a Year we export ETL by ETL and Load it in a New Folder. Meaning we extract 30 times and upload 30 times. It would save time if it is possible to export multiple ETLs and also Import Multiple ETLs ...

In the past, we had to implement client certificate authentication for several corporate clients when we wanted to query REST APIs. It would be much more efficient and less complex not to use Groovy jobs for this, but to be able to add this certif...

PALO.EPARENT and PALO.ELEVEL work well if you have only 1 hierarchy within a dimension. But if you have more than one hierarchy it would be great to give a certain root element as parameter and get the parent and or the level in exactly this spec...

The idea is to implement a button that gives you the possibility to expand all the sections for all Integrator Projects with one click.

A lot of our data processing requires us to do a step in ETL, then in SSIS and then in ETL because ETL can't do things like trigger stored procedures, etc. It would make dataprocessing a lot smoother and easier to automate if ETL could trigger th...