I wanted to bring to our collective attention challenge that I have faced with developing a complex Christ document The document contains multiple tables, tens of pages and and custom widgets and it is used in a daily basis by users adding data to the tables and there are improvements that need to be done in the document every now and then that require to change its data structure.
My concern is that because in the Grist model data and structure are mixed in one single document, that and doing changes in production might mean that I fill with production data as I do the changes, then having a sandbox where doing those is desired, but there is no easy workflow for that to happen.
Has anyone come up with a strategy to approach this that is replicable or at least that you can describe in order to start thinking about how to approach this in a well-structured way my current setup strategy is to export as a template work on the changes and then re implement the changes manually.
But I don’t think it is sustainable as changes sometimes imply doing multiple steps but I don’t see a way around it. Any guidance would be appreciated. Thanks.