Hey I am trying to export a dashboard as xlsx from one works GoodData #gooddata-cloud

Hey, I am trying to export a dashboard as .xlsx fr...

Nelly Harb

10/20/2025, 9:19 PM

Hey, I am trying to export a dashboard as .xlsx from one workspace but it is failing. However, it works when I export a dashboard from a different workspace. Is there a way to fix this or have the data from that dashboard exported? The status page is stating that all should be good, but it is not the case. Thanks

Screen Recording 2025-10-20 at 5.17.18 PM.mov

Xavier Drdak

10/20/2025, 9:47 PM

Adding some deets to this. We have an embedded iframe for good data in our app. In regular circumstances, we get an export back. However, checking real quick as to why its failing, we're getting back

Copy code

{
  "detail": "Server-side problem. Contact support.",
  "status": 500,
  "title": "Internal Server Error",
  "traceId": "713b3b6055f12e4e19f964c605fe1012"
}

Michael Ullock

10/20/2025, 11:07 PM

Sorry for the delay in getting back to you here - We are currently looking into this and will get back to you soon with more details

👍 1

Michael Ullock

10/21/2025, 12:15 AM

The error message you are encountering

INTERNAL: Sheetname 'CUSTOMERS', with case ignored, is already in use

. I have not come across this error in the past, but this seems to indicate that there is a conflict with the worksheet names during the dashboard export to XLSX. Could you please send us a direct link to your dashboard so we can review this for you? Or you can review the titles of the reports or insights on your dashboard and ensure that each one is unique (even when ignoring case). Renaming any duplicates could resolve the export issue.

Xavier Drdak

10/21/2025, 12:43 AM

I've reviewed the titles and we do indeed have duplicates. Changing the string to something more unique unblocked the exports functionality pretty much instantaneously. In case you still need it, the id

f388492b-40ca-4dc4-8a7b-aedc73b5fc88

should ™️ be the dashboard. Curious, is this a sort of error that could be bubbled at least to the console? Alternatively, how can we catch these types of internal errors that are pretty easy to correct on the client?

Joseph Heun

10/21/2025, 7:25 AM

Hello Xavier, Regarding error handling and surfacing these issues: GoodData API server-side errors (HTTP 500) typically return a generic error message with a

traceId

for support investigation, but do not always provide detailed, actionable feedback to the client. We can make a note for a product team to provide error messaging for the client side in regards to a case like this.

👍 1

Xavier Drdak

10/21/2025, 12:32 PM

Understood. Thanks for the help folks!

Productboard

10/21/2025, 12:37 PM

🎉 New note created.

7 Views

Open in Slack

Previous Next