Error after upgrade :source/implicitly-joinable is missing join alias

Hi there,

Our instance have been upgraded to latest 0.58.8.

Some of questions are not working. Those questions have been created using Question Builder.

The error message is : Column with source :source/implicitly-joinable is missing join alias

The Data Connection is BigQuery.

I tried to : Discard saved field values, Sync database schema, Re-scan field values.

Do you have any clue?

Regards

{
  "browser-info": {
    "language": "fr-FR",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0",
    "vendor": ""
  },
  "metabase-info": {
    "databases": [
      "bigquery-cloud-sdk",
      "mysql"
    ],
    "run-mode": "prod",
    "plan-alias": "",
    "version": {
      "date": "2026-02-27",
      "tag": "v0.58.8",
      "hash": "c2b1490"
    },
    "settings": {
      "report-timezone": "Europe/Paris"
    },
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MySQL",
        "version": "8.0.42"
      },
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.7.10"
      }
    }
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "21.0.10+7-LTS",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "21.0.10",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "21.0.10+7-LTS",
    "os.name": "Linux",
    "os.version": "5.10.135-122.509.amzn2.x86_64",
    "user.language": "en",
    "user.timezone": "Europe/Paris"
  }
}

Can you share the definition of those questions? Are there models involved?

You upgraded from which version?

Hi TonyC.

After reading some of Github issues, I found a workaround :

  1. remove all “Display values” for foreign keys
  2. check that questions can render properly
  3. configure all “Display values” for foreign keys

That is working. weird, isn’t it?

Because it’s working, you can close the issue.

To answer your questions :

  • No model involved, only single MySQL connection.
  • Question created using Builder. Could not generate SQL because or unexpected error.
  • I don’t know the version I coming from. I guess ~6months ago.

Hm, so there is a problem with migrating the stored FieldValues. Just clearing the values would have solved it then (there’s a button for that in both the Database settings and Table Metadata in Admin).

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.