I haven’t seen any feedback on this specific request yet. I apologize if I missed one.
I am interested in a toggle to allow the engine to leave behind a static copy of sections/fields/automations when removing a project/project template from the bundle.
I love using the bundle to update five projects at once. We often have 3-6 active monthly project at any given time. However, I worry about a continually growing list of projects as we finish monthly projects within the bundle. I don’t need to updating 30+ projects every time I update the bundle - probably only the last rolling 10 projects at most.
As some of the projects come to a close, I would love to start dropping them off the bundle, but the one time I did this it was a mess as the bundle removed all the fields/sections/automations that came from the bundle. I couldn’t even recognize the project anymore! How can I archive a project and roll it off the bundle without it loosing its structure? Our sections/fields/automations are complicated, so I don’t have time to add them back in manually every time I want to graduate a project off the bundle. I don’t need it to update along with the bundle anymore, but I can’t drop it from the bundle until there is a way to leave an imprint of the bundle sections/fields/automations as it was at the time of removing the project from the bundle.