```detail": "Source column should not be empty for...
# gooddata-cloud
k
Copy code
detail": "Source column should not be empty for 'attribute/mv_product_tag_lookup.region/
This is error I am getting. I know region is empty in some cases. How to fix this
k
Thinking completed The error message
"Source column should not be empty for 'attribute/mv_product_tag_lookup.region/...'"
indicates that the
region
attribute in your dataset has no data (all empty/null values)
. [Bad Request error] This is a known behavior in GoodData — even if a column is sometimes empty, if the attribute resolves to having no data at all in the context of the query, this error can occur. [Attribute empty values] Here are the steps to investigate and fix this: 1. Verify the data in your source table — Check whether the
region
column in the
mv_product_tag_lookup
table actually contains any non-null, non-empty values. If the column is entirely empty, the attribute cannot be used. 2. Check the
isNullable
setting
— In your Logical Data Model (LDM), ensure the attribute is marked as
isNullable: true
if the column can contain null values. This won't fix missing data, but it correctly reflects the column's nature. 3. Populate the source data — If
region
is legitimately empty for all rows, you'll need to populate it with actual data in your data source before GoodData can use it as an attribute. 4. Avoid using the attribute in reports until data exists — If only some rows are empty but the column does have data overall, try re-running the report or checking if a filter is inadvertently excluding all rows with data. The knowledge sources do not contain specific documentation on a configuration workaround for this error beyond ensuring the underlying data is populated. If the issue persists after verifying your data, please add the following details to this thread so the Support team can investigate further: • The trace ID from the error • Details about how the
mv_product_tag_lookup
dataset is defined (SQL dataset or table?) • Whether this is a child workspace or parent workspace dataset • Any filters applied to the report triggering the error Community support (Startup & Professional) You're already in the right place — the GoodData Support team monitors this Slack and a team member will join the conversation when human review is needed. You can also visit the Community Forums for additional help. 24/7 Support (Enterprise plans) If your account includes 24/7 Support or this is a Severity 1 (L1) critical issue, you can also: • Submit a ticket: support.gooddata.com • Email: support@gooddata.com • Call: +1 (415) 200-0194 👍 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.
k
@kapa.ai
Copy code
{
  "type": "about:blank",
  "title": "Bad Request",
  "status": 400,
  "detail": "Source column should not be empty for 'attribute/mv_product_tag_lookup.region/elastic_order_EBA-8308' in dataset 'dataset/elastic_events/elastic_order_EBA-8308'.",
  "traceId": "c3ceac5428b16a57e75df51fec8214f8"
}
Source column has null values only in few rows
k
Thinking completed The error
"Source column should not be empty"
in this context does not mean the column has no data at all — it means the
sourceColumn
field for the attribute in your LDM definition is empty/missing
, i.e., the attribute
mv_product_tag_lookup.region
in the
elastic_events
dataset has no source column mapped to it in the model. [Bad Request error] The null values in a few rows of your actual data are not the cause of this error. Here is how to fix it: 1. Check the LDM attribute definition — Open the Logical Data Model for the
elastic_events
dataset and locate the
mv_product_tag_lookup.region
attribute. Verify that its
sourceColumn
field is populated and points to the correct physical column name in your data source. 2. Correct the mapping — If the
sourceColumn
is blank, set it to the correct column name (e.g.,
"region"
):{ "id": "mv_product_tag_lookup.region", "type": "attribute", "sourceColumn": "region" } 3. Handle nulls in data (separately) — If you want null values in the
region
column to be handled gracefully in joins, you can enable Null-safe joins in Settings > SQL generation > Null-safe joins and set
isNullable: true
on the attribute. However, this is a separate concern from the error you are seeing. [NULL Joins docs] The root fix is ensuring the
sourceColumn
is correctly defined in the LDM — the null rows in your data are not causing this specific error. If after checking the LDM the
sourceColumn
is already set correctly and the error persists, please add the following to this thread so the Support team can investigate: • The trace ID:
c3ceac5428b16a57e75df51fec8214f8
• Your LDM definition for the
elastic_events
dataset (or the relevant attribute) • How the dataset is defined (physical table or SQL dataset?) Community support (Startup & Professional) You're already in the right place — the GoodData Support team monitors this Slack and will join when human review is needed. You can also visit the Community Forums. 24/7 Support (Enterprise plans) • Submit a ticket: support.gooddata.com • Email: support@gooddata.com • Call: +1 (415) 200-0194 👍 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.
k
great thanks @kapa.ai
🙌 1
k
Thinking completed You're welcome! Feel free to ask if you run into anything else. 😊 👍 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.