Bases: Renaming (or deleting) a property in properties view should update all affected bases

After a property is renamed in the “properties view” sidebar tab, the bases that used that property still refer to the old name (now empty).

It would be preferable when a property is renamed, that all bases that use that property are automatically updated to use the new name.

23 Likes

I agree with the request.

Additionalyy I suggest that the setting Automatically update internal links should also apply to bases.

1 Like

I do not like that, I can think in scenarios where this is not desired.

That said, there is also the option to let the user decide to “rename/delete globally or not” .

1 Like

Agreed.
Just migrating back from AnyType.
The one experience that I definitely miss in Obsidian is “edit once, edit everywhere.”

Properties remain consistent between all notes and bases that use them.

Hi! I completely agree that having properties automatically update in all affected bases when renamed in the properties view would be a huge time-saver. It’s frustrating when bases still reference the old property name and show empty data. As a workaround, I’ve been manually updating the property in each base’s settings, but an automatic sync would streamline things a lot. This could also apply to deleting properties to avoid broken references

Agreed. This should be an option in Settings > Core plugins > Bases. Perhaps conservatively disabled by default.

Definitely, this feature is important; I’m eagerly waiting for it here. Recently, I reported the lack of updating the name of a property in the databases when the name of a property was modified in the properties view.

Agreed! Ran into the same issue as described by others above of trying to change a property in the base but then having to change it manually for all notes in the base :’) I feel like changing the property names should work more like editing a database schema but agreed that it should be an option that users can toggle!

Any update from the team on whether this is on the roadmap?

The roadmap is publicly available here

+1 on this, just encountered it