Visualizer Pushdown
You can use for calculations at the Visualizer report level, evaluating queries at the database level instead of the Birst logical layer.
The report-level Pushdown setting supports a three-state switch:
- ON: Pushdown is explicitly enabled for the report.
- OFF: Pushdown is explicitly disabled for the report.
- INHERIT: The report follows the space-level Pushdown configuration.
This ensures that report-level settings can override or inherit space-level behavior in a controlled and transparent way.
This table shows the default Pushdown states:
| Report type | Default Pushdown state |
|---|---|
| New Report | INHERIT |
| Existing Report (Previously ON) | ON |
| Existing Report (Previously OFF) | INHERIT |
Existing Reports
To preserve current workflows and avoid unintended behavioral changes:
- If Pushdown was enabled at the report level, the new switch is by default set to ON.
- If Pushdown was disabled at the report level, the switch is by default set to INHERIT, that is it follows the space-level setting.
- If the space-level or report-level setting was ON previously, Pushdown continues to be treated as ON to maintain backward compatibility.
This ensures that no existing executions are disrupted by the updated configuration model.
New Reports
For all newly created reports:
- The default Pushdown setting is set to INHERIT, meaning the report respects the space-level configuration.
- If you explicitly set the Pushdown switch to ON or OFF, that selection overrides the space-level behavior.
This default approach allows new reports to stay aligned with broader workspace governance while giving authors the flexibility to override settings when needed.