Hello, we are facing an issue when customer sees less data than expected to be seen (embedded dashboard). Nothing changed on our side. In GD I can see all the data for this customer. But in embedded dashboard - just a part of it. I’d appreciate any idea what I can check to understand the issue. Thank you!

Here are some things you can check to investigate why the embedded dashboard shows less data than the GoodData UI: 1. Check User Permissions and Workspace Data Filters A common cause is that the embedded user has different permissions or workspace data filters applied compared to what you see in the GoodData UI. One known scenario is when a user has access to multiple workspaces — the workspace data filters may not be loading correctly for one of them, resulting in a "No data for your filter selection" message or missing records. [Multi-workspace data issue] 2. Verify the Embedding Setup • Confirm how you are embedding (iframe, Web Components, React SDK). • Check for any authentication/token issues (e.g., expired JWT tokens or session errors), which can cause partial or failed data loads. [Auth/token issue] • If using Web Components, ensure

setContext

is being called correctly and that the backend/workspace context is fully initialized before data is requested. [Web Components issue] 3. Check Filters on the Dashboard After adding or modifying filters, embedded dashboards can sometimes fail to load all data unless refreshed or resized. Check whether the filters in the embedded context are loading their values correctly — if filter values are empty, the user may see no or partial data. [Filter loading issue] 4. Check Cache Try reloading the cached data for the workspace and see if the issue persists. [Cache reload suggestion] 5. Capture Diagnostic Information If the above checks don't resolve it, gather the following and share with GoodData Support: • TraceIDs from the browser Network tab when loading the dashboard • A HAR file captured while reproducing the issue in the embedded environment • The failing

/executionResults

request payload and response from the browser network tab [HAR file request] This will allow GoodData Support to compare the embedded execution with the one running in the GoodData UI and pinpoint the difference. 👍 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.

Hi Andrey. Please check these potential root causes advised by our AI, and if the issue persists, provide us more details such as traceId, HAR file, and

/executionResults

request payload and response. Thank you!

Thank you, this one is solved on our end.

Happy to hear that. If you have any other questions, don't hesitate to let us know.