Datamodel keeps refreshing which makes editing impossible

Hi,

I've got a metabase setup with a client which contains about 8 databases.
These databases contains the same structure, but as there is no copy paste function in MB, i have to manually edit the datamodel for each database.

I already did 4 databases without any trouble, but now i'm starting to have issues with the 5th one.
Every time i try to edit a column with a different name it refreshes directly again to the original name.
It's just impossible to change it. Then i switched to another database and had no issues to do it there.
Then i switched back to the one where i had troubles, was able to change 2 values, and it was refreshing directly again.

So i thought it was an issue with that specific database in metabase, so i deleted it and readded it. But now i have the same issue with hiding the tables, i click on the hide button, it's gone, comes back, it's gone again..

So there is really an issue with the automatic refresh in one way or another.

I also restarted metabase to be sure, but no difference.
Also nothing to find in the logs.

What can i do ?

{
"browser-info": {
"language": "nl-NL",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "Cp1252",
"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 Client VM",
"java.vm.version": "11.0.13+8",
"os.name": "Windows 8.1",
"os.version": "6.3",
"user.language": "nl",
"user.timezone": "Europe/Paris"
},
"metabase-info": {
"databases": [
"postgres"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "14.2"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.23"
}
},
"run-mode": "prod",
"version": {
"date": "2022-02-17",
"tag": "v0.42.1",
"branch": "release-x.42.x",
"hash": "629f4de"
},
"settings": {
"report-timezone": "Europe/Brussels"
}
}
}

Hi @cobalt
There is a copy functionality with Serialization:
https://www.metabase.com/docs/latest/enterprise-guide/serialization.html
It sounds like you're seeing this issue:
https://github.com/metabase/metabase/issues/5558 - upvote by clicking :+1: on the first post

I'm not quite sure that it's the same thing.
When i'm typing to change the name it already refreshes the field while i'm typing.
In the issue you provided, they are just talking about it's not taking effect the change made.

Even tho, should it not be fixed after i readded the database? I have no issues with other databases in the system.

About serialization, it also does not seem to do exactly what i'm talking about. That sounds like a copy paste to another metabase instance and you have to be pretty experienced to execute it as well as you need a terminal to execute it. I was talking about a real "copy" button in the interface to copy a schema without IT knowledge :slight_smile:

@cobalt Okay, then perhaps it's this or the referenced issue:
https://github.com/metabase/metabase/issues/16780

You can use Serialization for a full instance copy, or just parts of it.

Seems more like that yes, but i don't have to click out of the field, it refreshes while i'm still trying to typ. (and because of that, impossible to change it)

So seems like i'm screwed than.
I just don't understand why other DB in the same MB instance have no issues :confused:

@cobalt I don't understand, but if it is that issue, then upvote it. And edit your display name directly in the application database table metabase_field

I hope it's more clear with this:

https://vimeo.com/manage/videos/682845040

edit: fyi, i'm able to change the titles if i first click on the cog icon to open the edit page of that specific column

@cobalt Hmm.... so you are definitely seeing the issue about the race-condition, but I think the way it's presenting to you has something to do with your browser/extensions or a load-balancer/reverse-proxy in front, which just makes it much worse.