Let us know how we can make Jedox even better!
I have several clients who have large Jedox databases, and so are active users of the Zero Suppression upon report generation.
However, when they are trying to change a POV (such as Version) on the report, there is a performance hit as the Zero Suppression is running in background to filter out any Version that doesn't have data. My clients may have 20 Version elements (several per month), so the background query doing the Zero Suppression across all of them causes a performance report hit simply to change 1 Version.
The workaround for the client is to (1) first disable the Zero Suppression, (2) change the POV to the Version they would like, then (3) re-enable the Zero Suppression. Obviously, this isn't a good use case, and if they forget these steps, then they have the performance hit.
Thank you for clarifying your idea. We have now made your idea public in our ideas Portal, while we cannot commit to a specific target version, we will consider adding it to our future internal backlog
Yes your use case is correct. Most times the end user is simply changing the POV but that results in delays due to Jedox in the background running queries (likely subsets) to only show POV elements with data. The Version dimension is the most frequent use case that is typically in the POV.