Hi Team, We're trying to display the latest data l...
# gooddata-cloud
c
Hi Team, We're trying to display the latest data loading date in GD. We've created metrics for the year, month and day based on max_bus_date_state, as shown below. We can retrieve each component individually, but when we try to combine them into a YYYY-MM-DD format, GD doesn't return as expected. Does anyone know what might be causing this and how we can fix it? The link is below: 99. [INT] For Monthly Purpose - GoodData Cloud
k
Thinking completed Hi! Looking at your screenshots, I can see exactly what's happening and why. What You're Seeing Your rich text widget shows:
Copy code
2026
11
03

Latest data load date: {metric/max_bus_date_-year_state} - {metric/max_bus_date-month_state} - {metric/max_bus_date-_day_state}
The top three numbers (2026, 11, 03) are rendering correctly as separate values, but the combined line at the bottom is showing the raw variable syntax instead of resolved values — meaning those variable references are not resolving. Why This Is Happening This is a known GoodData behavior: if any single variable in a rich text widget fails to resolve, all variables in that widget display as unresolved (either showing raw syntax or
(Data could not be retrieved)
). [Rich Text Limitations] The most likely cause is a typo or mismatch in the metric IDs used in the combined line. Looking at your screenshots: • Your metric ID is
max_bus_date_-year_state
(with an underscore before the hyphen) • But the rich text shows
{metric/max_bus_date_-year_state}
,
{metric/max_bus_date-month_state}
,
{metric/max_bus_date-_day_state}
Notice the inconsistency — the year has
_-
(underscore-hyphen), the month has just
-
, and the day has
-_
(hyphen-underscore). Even a single character difference will cause the variable to fail. How to Fix It 1. Double-check each metric ID exactly against what's shown in the Metric Editor (e.g.,
max_bus_date_-year_state
as shown in your screenshot). 2. Ensure all three IDs in the combined rich text line match exactly — copy-paste them directly from the metric editor rather than typing them manually. 3. The corrected rich text line should look something like:Latest data load date: {metric/max_bus_date_-year_state} - {metric/max_bus_date_-month_state} - {metric/max_bus_date_-day_state}(adjust to match your exact metric IDs) Additional Limitation to Be Aware Of Even once the IDs are correct, note that MAQL metrics return numeric values — so
MAX(Year {label/BUS_DATE.year})
returns a number like
2026
, not a formatted date string. Your approach of splitting into three separate year/month/day metrics and concatenating them in rich text is actually a solid workaround for this limitation. [Rich Text Limitations] Fix the metric ID spelling in the combined line first — that should resolve the display issue. 👍 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.
y
Hi Cathy, Our AI assistant provided an accurate response, please let us know if you have any further questions.
c
Hi Yvonne, I can't see any difference between the individual metrics and the combined version using hyphens. I actually copied the metric IDs directly from the Metric Editor into the individual references, then copied those same references into the combined rich text, so the IDs should match exactly.
I also noticed that if we put each metric on a separate line, they resolve correctly. For example, the below works. However, when I use the exact same metric references together in a single text string, they don't work.
@kapa.ai please look above and find out how to fix the issue
k
Thinking completed Based on the screenshots you shared and the previous answer above, the fix is straightforward: The Problem The metric IDs in your combined rich text line have inconsistent hyphen/underscore patterns: The Fix Copy-paste the exact IDs from each metric's editor and update your rich text line to:
Copy code
Latest data load date: {metric/max_bus_date_-year_state} - {metric/max_bus_date_-month_state} - {metric/max_bus_date_-day_state}
> Important: Do not type the IDs manually — open each metric in the Metric Editor, copy the ID shown there (as you can see
max_bus_date_-year_state
in your screenshot), and paste it into the rich text widget. Do the same for the Month State and Day State metrics. Once all three IDs match exactly what's in the Metric Editor, the combined line will resolve correctly and display your date in
YYYY-MM-DD
format. [Rich Text Limitations] 👍 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., with interactive elements
c
@kapa.ai month metric is {metric/max_bus_date_-_month_state}, we use the same metric in both rich text, it contains underscore before hyphen.
k
Thinking completed Thank you for the clarification and the screenshots! Looking at your images carefully: • First screenshot (no blank lines): all three references are on consecutive lines — this works correctly. • Second screenshot (with blank lines between): the same references are separated by empty lines — and this is what you're using in the combined line. The metric IDs themselves appear correct (
max_bus_date_-_month_state
with underscore-hyphen-underscore). So the IDs are not the issue here. What's Actually Happening Looking at your second screenshot, the references are separated by empty lines, which in Markdown creates separate paragraphs. This means each metric is being rendered in its own block — which is why they resolve individually when on separate lines. The issue with the combined inline version (e.g.,
Latest data load date: {metric/...} - {metric/...} - {metric/...}
) may be related to how GoodData resolves multiple metric references on the same line in a single text string. What to Try 1. Make sure your combined line uses the exact IDs as confirmed:Latest data load date: {metric/max_bus_date_-_year_state} - {metric/max_bus_date_-_month_state} - {metric/max_bus_date_-_day_state} 2. Ensure there are no extra spaces, line breaks, or hidden characters around the
{}
references. 3. Try placing this combined line in a fresh rich text widget with no other content, to rule out interference from other references. The knowledge sources do not explicitly document a limitation around multiple metric references on the same line beyond the ID-matching requirement. [Rich Text Limitations] To help the Support team investigate further, please add the following details to this thread: • The exact raw Markdown content of the combined rich text widget (copy-pasted, not a screenshot) • Whether the issue persists in a brand new rich text widget • Your workspace/organization ID Community support (Startup & Professional): You're already in the right place — the GoodData Support team monitors this thread and will step in as needed. 24/7 Support (Enterprise plans): You can also submit a ticket at support.gooddata.com, email support@gooddata.com, or call +1 (415) 200-0194 if this is Severity 1 or your plan includes 24/7 support. 👍 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.
c
@kapa.ai 1. {metric/max_bus_date_-_year_state} {metric/max_bus_date_-_month_state} {metric/max_bus_date_-_day_state} 2. {metric/max_bus_date_-_year_state} {metric/max_bus_date_-_month_state} {metric/max_bus_date_-_day_state}
k
Thinking completed Thank you for sharing the exact raw content. This confirms the metric IDs are correct in both cases. The difference between the two versions is: 1. Version 1 — metrics separated by blank lines (separate Markdown paragraphs) → resolves correctly 2. Version 2 — metrics on consecutive lines with no blank lines → also resolves correctly (as your earlier screenshots showed) Since both of these work, but the combined inline version (all three on one line with
-
separators) does not, this points to a behavior that the knowledge sources do not explicitly document — specifically, whether multiple metric references combined inline in a single string are fully supported in the same way as separate-line references. To help the Support team investigate this specific inline combination behavior, please add the following details to this thread: • The exact raw Markdown of the combined inline line that is failing (e.g.,
Latest data load date: {metric/max_bus_date_-_year_state} - {metric/max_bus_date_-_month_state} - {metric/max_bus_date_-_day_state}
) • A screenshot of the rich text editor showing the failing combined line • Whether the issue occurs in a brand new widget with only that one line Community support (Startup & Professional): You're already in the right place — the GoodData Support team monitors this thread and will step in as needed. 24/7 Support (Enterprise plans): You can also submit a ticket at support.gooddata.com, email support@gooddata.com, or call +1 (415) 200-0194 if this is Severity 1 or your plan includes 24/7 support. 👍 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.
m
Hi Cathy, apologies for the confusion in the earlier replies. You’re right: the metric IDs are correct, and your tests show the references resolve on separate lines but not when combined on one line. We’ve noticed that the same combined format (year - month - day on one line) worked in your other workspace, as in your earlier thread about venues. So combining several references on one line is supported. What’s different here is that the references now show as raw text rather than resolving. One difference we’re looking into is the
_-_
in the new metric IDs (for example
max_bus_date_-_year_state
), since rich text uses Markdown, where underscores can have a special meaning. To help us confirm this, could you please: 1. Paste the exact text of the combined line that fails, as plain text rather than a screenshot. 2. Try a quick test: create a copy of one of the metrics with an ID without
_-_
(for example
max_bus_date_year
), and put it on one line together with another reference. Let us know whether that line resolves. We’re also checking this on our side and will follow up with what we find.
c
Thanks Michael, this works