What if when a document was generated from a template instead of replacing the Tag with the data have the data replace the Tag friendly name. Then the generated document could be passed around modified and when all the changes are agreed upon then run the template again to get the latest values from the data source.
Recently I've had several prospects ask for this kind of functionality and this is the only idea that I could think of that might allow users to refresh their data in generated documents.
We have reviewed this idea internally but have decided to decline it for development. The reason is that this functionality would be non-trivial and risky to implement as well as it is not in the same direction as our current development efforts. Thank you very much for the suggestion, and please submit any other ideas you have to improve our products.
Basil Dobek commented
My client has asked for this same capability. It's quite an issue because we are trying to replace a system involving word macros which does have this exact capability.
Rod Potter commented
Could you hide the original AutoTag tags and wrap the generated output in new "hidden tags" ... allowing for the contents to be replaced under subsequent refreshes? A toggle button on the AutoTag menu might allow you to flip back to the original tags if they need adjustment. I see it working like a live preview mode. Our client has a desire for this functionality as well.
AdminDavid Thielen (Admin, Windward) commented
Under this model when they have a forEach loop and that expands out to 20 rows in a table, which set of data do we display in the tag? Or if we render all 20 rows, which row's formatting edits do we take back to the template?