Field filter mapping is gone after alter

I have Questions and Dashboards based on MySql view table.
Each question has variables parameters mapping to field filter to specific table columns like date to a date column in a table, and so on.

But when I altered the view using below illustration code, all the mapping is gone. And I must repeat all the mappings again for each question?

ALTER VIEW my_existing_view_name AS
SELECT existing_columns
FROM existing_tables
WHERE existing_parameters in ('existing_values','new_value')

Is there solution or rollback to this scenario?
I just change very minor (add new value in parameters like above)


Hi @eric.halim
I don't think I follow. If you rename a table (or view) or column, then Metabase has no knowledge of that rename, so when Metabase does a sync, then it will deactivate the old table/column and create the new table/column.

Exactly, I didn't change the view name. I just change value in one of the parameters in the view table. So I didn't expect I will loose all the field mappings.

@eric.halim That should not happen.
Post "Diagnostic Info" from Admin > Troubleshooting, and the database you're querying.

  "browser-info": {
    "language": "en-US",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36 Edg/93.0.961.52",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.11+9",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "",
    "java.version": "11.0.11",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.11+9",
    "": "Linux",
    "os.version": "4.15.0-106-generic",
    "user.language": "en",
    "user.timezone": "Asia/Jakarta"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MySQL",
        "version": "8.0.16"
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.6.2"
    "run-mode": "prod",
    "version": {
      "date": "2021-08-03",
      "tag": "v0.40.2",
      "branch": "release-x.40.x",
      "hash": "b884d29"
    "settings": {
      "report-timezone": "Asia/Bangkok"

@eric.halim Upgrade to 0.40.5, and then I'll try to reproduce this.

It will require time to request an update, not so fast. Do you have any idea or workaround to this situation?

@eric.halim I cannot reproduce. You have to create exact steps-to-reproduce.