Autocomplete Doesn't Work for Foreign Key Column Type

Greeting

For a Foreign Key Column Type the Autocomplete shows no Match Found.
If I change the Column type to something else like Category / No Semantic Type it's starts working.

But then if I change column type to other than Foreign Key, it's switch back to Foreign Key automatically.
Whereas like I changed the Entity Key to Category, it's stays Category.

So 2 Problem:

  1. Foreign Key Column Autocomplete Not Working
  2. Changing Foreign Key type to something else, switch backs to Foreign Key

Any help / Alternate Solution?

Hi @spanda

Post "Diagnostic Info" from Admin > Troubleshooting, and which database type you're using.

Have you read this? https://www.metabase.com/docs/latest/troubleshooting-guide/filters.html

1 Like

Database is MS SQL Server 2008R2

{
"browser-info": {
"language": "en-US",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.13+8",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "11.0.13",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.13+8",
"os.name": "Linux",
"os.version": "5.11.0-1022-aws",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"sqlserver",
"h2"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "14.0 (Ubuntu 14.0-1.pgdg20.04+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.23"
}
},
"run-mode": "prod",
"version": {
"date": "2021-11-09",
"tag": "v0.41.2",
"branch": "release-x.41.x",
"hash": "ad599fd"
},
"settings": {
"report-timezone": null
}
}
}

@spanda Okay, Metabase does not support MSSQL 2008R2 anymore. It would become an impossible task if we had to support every legacy version of all the database types we're supporting.
It might still work, but certain things might not.

1 Like

Ya Understand. We are moving to 2019 soon, so will see at the time.

@spanda A lot of things will be much faster - I remember upgrading a 2008 to 2016 (or something like that) and it was a great speed improvement for the many hundred people using it every day.
Though it was a big task and took me a month to get right, so I could do the upgrade in one night.