Visualizations hidden based on a visibility parameter should not be executed

Federico Venturin

With the OAC November 2024 Update, you can show or hide visualizations based on the selected value of a parameter.

Currently, all visualizations in a workbook are created first and only then hidden based on the visibility parameter. This behavior may impact performance (as unnecessary queries are executed in the background) and could expose unwanted data to end users.

Visibility parameters should be evaluated first so that, if the condition is not met, the visualizations are not generated at all.

Francis Defilippis

This feels really important to improve performance.

Gabby Rubin-Oracle

Assuming we can prioritize the queries correctly (visible, active canvas, canvas viewport, etc.), not processing the currently hidden viz will impact the experience of the dashboard user, as the queries will only execute when the parameter is changed. You can take an approach using the same parameter to ensure that queries are not running unless the parameter is on the visible value. This way, you can control whether the hidden viz will execute based on your use case.