noticed that before you choose a visual type there...
# gooddata-cloud
c
noticed that before you choose a visual type there seems to be an error with the names of the values as shown below. not sure if its a bug or not
k
Looking at your screenshot, the bucket labels are showing raw translation keys like
DASHBOARD.BUCKET.MEASURE...
,
DASHBOARD.BUCKET.ATTRIBUT...
, and
DASHBOARD.BUCKET.COLUMN...
instead of their proper display names. This does appear to be a display/localization issue. This looks similar to a known category of bugs in GoodData where internal keys or names are shown instead of the expected display labels. There is a known bug reported in the community where metric titles in tables show the internal name instead of the title [Community Slack], which suggests there can be localization/display name resolution issues in certain contexts. However, the knowledge sources do not contain specific information about this exact issue (bucket labels showing raw translation keys before a visual type is selected). Here are my suggestions: 1. Check your SDK/UI version — a similar filter label display bug was confirmed to be version-specific and was resolved by upgrading to a newer SDK version. [Community Slack] 2. Check your CSS import — if you're using the Dashboard component, ensure you have
import '@gooddata/sdk-ui-dashboard/styles/css/main.css'
included, as missing this import has caused display issues in the past. 3. Report it to GoodData support — if the issue persists, it's worth raising with the GoodData team, as this does not appear to be expected behavior. I'd recommend reaching out to GoodData support directly for a definitive answer on whether this is a known bug and if there's a fix available. 👍 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.
s
Hi Chris, thanks for flagging this! To help us look into it, could you share a few more details: 1. Are you seeing this in the native GoodData Cloud UI (e.g. yourorg.cloud.gooddata.com), or in an app that embeds GoodData via the React SDK? 2. Could you walk us through the exact steps to reproduce it? For example: did you open a new visualization or an existing one, and had you selected a chart type at the point when the screenshot was taken? 3. Have any of your colleagues seen the same issue, or is it specific to your account? 4. When did this first appear — was it sudden, or have you always seen it? Thank you in advance.
c
I am seeing this in the native cloud ui it is only visible when you click on the Analyze tab but before you clock on a visual type I believe some of my colleagues are seeing it but i would have to check I only noticed it recently after i had to reload when gooddata prompted me
s
Thanks for the details, Chris. When I tried to reproduce it on my end, the table chart type gets selected automatically as soon as the Analyze tab loads. So by the time I can see the bucket panel, a chart type is already active and I can't catch the initial state you described. It's possible what you're seeing happens during a brief moment before that auto-selection kicks in. Maybe due to a slow load or a slight lag on your end. To help me nail down the repro and report it to our developers, could you record a short screen recording the next time it happens? If your colleagues are seeing it too, a recording from their side would also be useful. The more consistent I can make the repro, the faster I can get this in front of the right team. Thanks.
c
Recording 2026-06-26 161407.mp4
👀 1
mine shows table as selected but only change to the proper options when i select another type and then click back on table
s
I'm going to check your workspace internally using our admin user. Could you please share the link? Feel free to use DM.
Hi Chris. I've found the root cause. The issue is tied to the language setting on the project. I was testing with American English, which is why I couldn't reproduce it — but when I switched to British English (which you're using), the raw keys appeared straight away. As a temporary workaround, switching your project language to American English should make it go away. I'll report this as a bug to our developers so it gets properly fixed. Thanks for reporting this.
✅ 1
c
great thank you I will take a look
👍 1
s
Hi Chris, Good news — this has been fixed! Please give it a try and let me know if everything looks correct on your end now. Thanks for reporting it!
c
Yes that has worked thanks
👍 1