ETL: Initialize variables via PALO.Data / OLAPData function
Thanks for extending the definition of variable default values
by groovy script and Jedox settings.
But it would be much more helpful to initialize variables directly via a cube lookup (PALO.Data / OlapData function).
We have several configuration cubes where settings are maintained.
It is currently very clumsy and annoying to initialize the variables based on the confiuration cubes.
You need a LoopJob or TableLoop, a ConstantTable Extract, and a Field Transform with OLAPData to simply set one value. (see attached example)
The structures you need to build for variable initialization are sometimes more complex than the process itself.
This is bloating the flow chart and reduces maintainability and transparency.
Starting with 2019.1, Groovy Origin variables can reference values from a Global Connection, such as Jedox Cube or relational connection. This is useful if you need to retrieve stored connection variables, such as tokens, when you connect via REST.