Hi Team, when exporting dashboard to PDF, PPT or xlsx file getting 400 error with following message - {"detail":"Dashboard content is malformed and cannot be parsed.","status":400,"title":"Bad Request","traceId":"de1748cbcd9b455ce4f6f89122ec1878"}. How to fix it?

The exact error you're seeing —

"Dashboard content is malformed and cannot be parsed."

with a 400 status — has been reported before in the GoodData community. [Bad Request export] Here are the known causes and fixes: 1. Broken references in the visualization/dashboard definition A 400 error can occur when the dashboard or a visualization references a label, attribute, or dataset that no longer exists in the Logical Data Model (e.g., it was removed, renamed, or its dataset was changed). Review your dashboard's visualizations and ensure all referenced attributes/labels still exist in your current LDM. [Broken LDM reference] 2. Malformed dashboard content (API-built dashboards) If the dashboard was constructed via API or embedding, the structure may be malformed. In the documented case, GoodData's L2 support was able to fix this directly. If your dashboard was built or modified via API, check the

tabs

and

filterContext

sections for any invalid or malformed filter objects. [Bad Request export] 3. Linked filters issue (XLSX-specific) For XLSX exports specifically, linked filters on the dashboard have been identified as a cause of export failures. Try removing or recreating the linked filters on your dashboard and attempt the export again. [Linked filters issue] Recommended next steps 1. Share your

traceId

(

de1748cbcd9b455ce4f6f89122ec1878

) with GoodData Support — they can look up the internal logs to identify the exact root cause, as end-users cannot access internal logs directly. [Broken LDM reference] 2. Check browser DevTools (Network/Console tabs) when reproducing the export failure for additional error details. 3. Review your dashboard for malformed filters, broken attribute references, or any content added via API that may be invalid. Since the fix in the documented case was handled directly by GoodData's L2 support team, I'd recommend opening a support ticket and providing the

traceId

along with a direct link to the affected dashboard. 👍 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.

Can I get exact details of what causing it malformed based on traceId? @kapa.ai

Unfortunately, end-users cannot access GoodData's internal logs directly to decode the exact root cause from a

traceId

. [Broken LDM reference] The

traceId

is uniquely bound to the problematic request in GoodData's internal application logs, which only GoodData support staff can access. [API Errors] What you can do: 1. Contact GoodData Support and provide your

traceId

(

de1748cbcd9b455ce4f6f89122ec1878

) along with your workspace ID and a direct link to the affected dashboard. Support staff can look it up in internal logs and tell you the exact cause — as seen in similar cases where staff identified specific broken label references or other root causes from a traceId. [Broken LDM reference] 2. Check browser DevTools (Network/Console tabs) while reproducing the error — sometimes additional error details are surfaced there that aren't in the generic API response. [Broken LDM reference] In short, the

traceId

is your key to getting the exact details — but only GoodData's support team can use it to retrieve those details from their logs. 👍 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.

any slack channel available to contact GoodData Support? @kapa.ai

Based on the knowledge sources, there is a GoodData Community Slack where users can reach out for support. Community members and GoodData support staff actively participate in discussions there. From the conversations referenced, GoodData support staff can look up `traceId`s and investigate issues directly when you post in the community Slack. [Broken LDM reference] The knowledge sources also reference a dedicated GoodData Support portal at **https://support.gooddata.com** for opening formal support tickets. [Urgent dashboard issue] For your specific export issue, I'd recommend: 1. Posting in the GoodData Community Slack with your

traceId

(

de1748cbcd9b455ce4f6f89122ec1878

), workspace ID, and a direct link to the affected dashboard. 2. Alternatively, opening a ticket at **https://support.gooddata.com**. The knowledge sources do not contain the exact invite link or full URL to the Community Slack workspace, so I'd suggest checking GoodData's official website or documentation for the direct link to join. 👍 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.

GoodData support team can you please help here based on

traceId

(

de1748cbcd9b455ce4f6f89122ec1878

Hi Arif, I’m going to have a look into this for you and get back to you shortly 🙂

https://atheerair.cloud.gooddata.com/dashboards/#/workspace/oilgasenergydemo-525/dashboard/688b3b43ca9af73a86676f77 There was issue that title was missing in dashboard when created using API. After updating title from gooddata cloud, it started working now, able export dashboards now.

That’s great news Arif - I’m glad that you were able to resolve this issue. I hope you have a great weekend ahead 🙂