Clément Contamine
12/05/2025, 4:41 PMkapa.ai
12/05/2025, 4:41 PMtab.identifier, dashboard.activeTabId). [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] Fix (recommended): Update the dashboard metadata so that: - tab.identifier → tab.localIdentifier - dashboard.activeTabId → dashboard.activeTabLocalIdentifier [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] If you are deploying via VSCE and use VSCE 0.19.0+, deploying the YAML for that dashboard to the existing dashboard will automatically rename these properties. [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] Workaround: Disable tabs on that dashboard (remove tab configuration in metadata). The dashboard should then load again. [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] --- ### 2. If the dashboard was created/updated via API or code A malformed filter context or an empty insight can also make the dashboard page go white: - Filter context with an empty object in `filters`: json "filters": [ { } ] or an extra {} entry in the array will break the dashboard. [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] - Empty insights (no attribute/fact) included on a dashboard are a known bug and will crash the dashboard UI. [[Empty insight bug](https://gooddataconnect.slack.com/archives/C01UR5BGAHY/p1714044527657209?thread_ts=1714044527.657209&cid=C01UR5BGAHY)] Workarounds: 1. Fix filter context via API Ensure the dashboard’s filterContext has only valid filters (no bare {} objects). [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] 2. Fix empty insights Open the problematic insight directly in Analytical Designer (Analyze), add at least one attribute or fact, and save. This usually restores dashboard loading. [[Empty insight bug](https://gooddataconnect.slack.com/archives/C01UR5BGAHY/p1714044527657209?thread_ts=1714044527.657209&cid=C01UR5BGAHY)] 3. As a last resort, delete the broken dashboard via API If you just need to unblock users and can recreate the dashboard later, you can remove it with: http DELETE /api/v1/entities/workspaces/{workspaceId}/analyticalDashboards/{dashboardId} [[White page workaround](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] --- ### 3. Next steps to narrow it down 1. Confirm whether the dashboard **uses tabs**; if yes, start with the tab metadata fix. 2. Check if the dashboard was recently changed via API/CLI/VSCE (filters, tabs, or insights). 3. Open browser dev tools (Network/Console) on load and capture any error/TraceID – this is essential if you need to escalate to GoodData Support. [[White page cases](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] If you can share whether the dashboard has tabs and whether it was recently deployed/edited via code, I can suggest a more precise sequence of API edits.Simon Delolme
12/08/2025, 9:01 AMkapa.ai
12/08/2025, 9:01 AMkapa.ai
12/08/2025, 9:01 AMtab.identifier - dashboard.activeTabId If you find them, change to: - tab.identifier → tab.localIdentifier - dashboard.activeTabId → dashboard.activeTabLocalIdentifier [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] If you use VSCE 0.19.0+, redeploying the YAML of that existing dashboard should automatically rename these properties. [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] Quick workaround: If you need to just restore access, you can temporarily disable tabs by removing the tabs: configuration from the dashboard definition (so it behaves as a single-page dashboard). [[Tabs blank screen](https://www.gooddata.com/docs/cloud/create-dashboards/dashboard-tabs/#dashboards-with-tabs-show-a-blank-screen)] --- ### 2. Check for malformed filter context (common with API/metadata edits) Even if you didn’t recently change it via API, a malformed filter context in the dashboard metadata can cause a white screen. Typical pattern: json "filters": [ { } ] or an extra empty {} entry in the filters array. [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] Compare your dashboard’s filterContext with a known-good one and ensure: - Every filter object is a valid dateFilter or attributeFilter. - There are no bare {} objects in the filters array. [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] Fixing this via API (updating the filter context to a valid structure) restores the dashboard. --- ### 3. Check for empty insights on the dashboard If any insight on the dashboard has no attribute or fact (an “empty” insight), it is a known bug that this can break the whole dashboard UI. [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] Workaround: - Open each insight used on that dashboard directly in Analyze (Analytical Designer). - Ensure each has at least one attribute or fact, then save. [[Filter context issue](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1740723524361399?thread_ts=1740723524.361399&cid=C04S1MSLEAW)] --- ### 4. Last-resort unblock: delete the broken dashboard via API If you just need to unblock users and can recreate the dashboard later, you can remove it via API: http DELETE /api/v1/entities/workspaces/{workspaceId}/analyticalDashboards/{dashboardId} This is a known workaround for white-page dashboards. [[White page workaround](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] --- ### 5. What I’d suggest you do next 1. Export or fetch the dashboard definition (YAML or JSON). 2. Search for: - tabs: section and any tab.identifier / dashboard.activeTabId. - filterContext with any {} entries in filters. 3. If you find: - Legacy tab properties → rename as above or redeploy via VSCE 0.19.0+. - Malformed filters → correct them to valid filter objects only. 4. If nothing obvious appears, capture: - Browser console errors and any TraceID from Network tab when loading the dashboard, and share those with GoodData Support for deeper log analysis. [[White page cases](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] If you can paste (sanitized) snippets of the dashboard’s tabs and filterContext sections, I can help you pinpoint exactly what to change.Simon Delolme
12/08/2025, 10:19 AMJulius Kos
12/08/2025, 11:52 AMJulius Kos
12/08/2025, 11:56 AMGET /api/v1/entities/workspaces/{workspaceId}/analyticalDashboards/{dashboardId}
The full definition is in data.attributes.content.
You can edit it (e.g., fix tabs or filters) and push it back with a PUT to the same URL.
2) VS Code Extension (VSCE)
If you use Analytics-as-Code, open your VSCE project →
analytics/analyticalDashboards/ → open the YAML for this dashboard.
That file contains everything (tabs, filterContext, insights).
3) Python SDK
You can also fetch/update the dashboard via Python. Something like:
from gooddata_sdk import GoodDataSdk
sdk = GoodDataSdk(host, token)
dash = sdk.catalog_workspace_content.get_analytical_dashboard(ws, id)
sdk.catalog_workspace_content.update_analytical_dashboard(ws, dash)Joaquim Grilo
12/08/2025, 1:41 PMJoaquim Grilo
12/08/2025, 1:42 PMJoaquim Grilo
12/08/2025, 1:42 PMUncaught SyntaxError: The requested module '<https://xxx.cloud.gooddata.com/components/tigerBackend.js>' does not provide an export named 'default'