Apply template updates to existing instances
M
Modern Entities
When you update a template in any part of the hierarchy, have the option to update all existing instances that use that template.
Any concerns about data safety could be handled by having any fields that are removed simply be hidden from the list view, but still be accessible when clicking into the item. Therefore you could choose to reintroduce the hidden field and still have all the data there, because the data still exists.
Log In
Микита Морозов
I would also love something like this: could be realyl heplfull when you have 20-30 spaces which must be the same. It's especially important, if there was even a minor mistake when you created those originaly :-)
Caroline Ginty
Merged in a post:
Pushing Mass Updates
C
Caitlin Valerio
-editing a template and pushing all updates to the spaces using that template
-editing automations and pushing to all that has the same automation.
J
Joseph Dabalus
Posting comment for another user:
Template update for VIEWS and STATUSES templates, which will be pushed to update wherever the template is used.
I understand why list and folder template updates cannot be pushed, but there’s no reason for VIEWS not to be. Statuses. Templates are a bit more complicated but doable.
It would be best to be able to control the templates as the latest version allows control over custom fields -> where from the source (template), you can choose whether to update it or not and, as a result, go through the accepted changes or not (what tasks move form old statuses to the new ones in the updated template for example)
Beth Daniels
This would be helpful for us as we use templates for project management. If changes are made to the template the new projects setup with that template are covered, but it would be nice to apply the changes to existing instances that template has been used. Right now we have to manually update all existing instances with the changes and it is very time consuming.