https://www.gooddata.ai/ logo
Join Slack
Powered by
Help me with this error.
# gooddata-cloud
a
Help me with this error.
k
Looking at your screenshot, I can see two types of errors on the NEW_DASH_VEN1 dashboard: 1. Warning triangles (⚠️*)* on the "Count of Started/Submitted/Selected Applications" widgets — these indicate visualization errors. 2. "SORRY, WE CAN'T DISPLAY THIS VISUALIZATION — Contact your administrator." on the "Application Status" chart — this typically indicates the visualization is restricted by access rules. Here are the most likely causes and steps to investigate: ------------------------- 1. "Contact your administrator" error This message specifically means the visualization is restricted by access rules (a 
ProtectedReportSdkError
). [ProtectedReportSdkError] Check with your workspace admin whether data access/security filters are preventing your user from viewing that insight. ------------------------- 2. Warning triangles on the other visualizations These could be caused by several things: • LDM/mapping issues: If recent changes were made to the data model (renamed attributes, changed mappings, or reverted changes), visualizations can break. Check the LDM for any warnings in the mapping tab for the attributes used in these insights. [Dashboards failing – LDM label issue] • Incorrect or non-existent identifiers in the insight definition: If the visualization references attributes or filters that no longer exist, it will fail. Check the visualization object via the API endpoint:
Copy code
GET /api/v1/entities/workspaces/{workspaceId}/visualizationObjects/{insightId}
and verify all identifiers are valid. [Cannot find visualization] • Data limits exceeded: If a visualization uses too many datapoints (e.g., over 100,000 rows without a metric), it will error. [Limits hit] ------------------------- Recommended next steps 1. Open browser DevTools (Network or Console tab) while loading the dashboard and capture any Trace IDs from failing requests — these are essential for Support to investigate. 2. Check if the same visualizations work when opened directly in Analyze. 3. Review the LDM for any warnings or unmapped attributes. 4. If the issue persists, open a support ticket at support.gooddata.com with the Trace IDs, workspace/dashboard links, and a description of any recent changes. [Support guidance] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
The Data mapping tab is found within the Dataset details dialog in the LDM Modeler. Here's how to get there: 1. Go to the Data tab in your workspace. 2. Switch to Edit mode. 3. Locate the dataset whose attributes are used in the failing visualizations. 4. Hover over the dataset and click Details (or More … → View details). 5. In the dialog that opens, click the Data mapping tab. From there, you can see how each field in the dataset is mapped to a source column in your database. Fields with a red or warning icon indicate mapping issues that need to be corrected. [Map LDM to Database] Once you identify any incorrectly mapped or unmapped fields, update the mapping to point to the correct source column and click Save changes. Repeat this for every dataset involved in the broken visualizations. [Convert Facts and Attributes] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
j
Hi @Anuj Sahu, we can check this for you in GoodData Support using the admin account and accessing the workspace. Give me a moment to review it, and I will follow up with you.
👍 1
Hi @Anuj Sahu, I'm in the org, but cannot find that workspace/dashboard from your screenshot. Could you please send a direct link? You can do so via DM as well
a
j
Thanks... I will have a look
It looks like there is an attribute used but not found in any of the datasets. Have any changes been made to the LDM recently? if so, you will want to clear the cache in the data source. Based on the error in logs, I would suggest: 1. Verify the attribute ID — Check whether 
progressreportid
is the correct identifier for the attribute in the 
zengine_master
datasource, particularly if there are separate dev/prod environments with different IDs. 2. Check the LDM — Confirm that the attribute is properly defined and mapped in the workspace's Logical Data Model. 3. Invalidate/clear the cache — After making any corrections, clear the cache to ensure stale references are not causing the issue. If you are still facing issues after checking these points please let us know.
👍 1
a
I have cleared cache, verified 
progressreportid
and checked LDM, still facing issues.
j
Hi Anuj, Have you done any recent changes within your data source, LDM / SQL datasets? The issue is quite strange as it looks like using any fact or attribute triggers the below error:
Copy code
The attribute='attribute/progressreportid/zengine_master' was not found in any dataset.
However, everything appears to work correctly in parent workspace. So looks like only the child workspace is somehow broken. Please let us check on this internally.
I have found a slack thread where you were facing the same error actually ..can you please double-check on that? https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1761216258017049 Looks like you were able to fix the situation by changing some ID.
5 Views
Open in Slack
PreviousNext
Powered by