Custom mapping is reset while editing unrelated settings in column metadata about metabase

[calherries]

This is a FE issue so I'm redirecting this to Team/AdminWebApp. The request to update the field values (POST /api/field/:id/values) does the job, so this is a FE issue. After refreshing the page, the updated settings are persisted. But if you do any of the above in step 2 the FE is incorrectly using cached settings that should have been updated or invalidated.

So the title of the issue is a little misleading, because the changes to the custom mapping is only reset on the FE, but the custom mapping is actually saved correctly on the BE. Because of this, I'd say this is more like a P3 than P2. It's not blocking any functionality but it is certainly showing incorrect information to users.

[zbodi74]

I just noticed, editing the name or description of the column at the table level page also persists the change. So I'd vote for P2 as the mapping might be cleared out even without a visible change on the UI.