Because of performance degrades fast in jedox web, on rather small input templates, I would like to propose "Non-Volatile" function.
Consider a function that makes other functions non-volatile, or at least does not update when user input plan data.
Example:
Consider a PALO.DATA() that simply returns an attribute like Name from the attribute cube of a dimension.
I have no need for that to recalculate (in most cases) when the user is using the input template.
Hence, if we could tell Jedox not to recalculate the result, saving a query (maybe many).
Lets call it "NVol()" for non-volatile. For me non-volatile means that it is calculated when the report is initially loaded, but not for any later updates.
= NV(PALO.DATA(...))
And this would then make Jedox remember that it has already calculated this one, so no need to update the content.
I don't know if this makes sense the way Jedox is coded.
But, in short, I really want performance boost to Jedox UI experience, and having Jedox do less logic for each user input would help.
If implemented, a possibility to force full recalculation could be nice in like a macro. Just for those cases where you do not need it to recalculate, but there is that one exception, so a workaround could exist.
