Self-Hosted, Avante, Windows Client, Web Client

We have a use case where a page from an existing document with Template A is copied and used to create a new document with the template being changed to Template B.  Field1 exists in both templates and Field2 exists only in Template B.  Field1 is dynamic in both templates with no parent.  Field2 in Template B is dynamic, with Field1 being the parent.  When the new document is created from the copied page, the user changes the template during the creation to Template B; however, the dynamic Field2 does not fill unless they manually change Field1 to a different value (from its dynamic dropdown list).  They then must change it back again to its original value (from its dynamic dropdown list) so that both fields are accurate. This occurs both in the Windows client (our currently preferred interface) and the web client.  I'm working around this now using an activity in the workflow that runs on new documents created with Template B, looking for an empty value in Field2 and filling it from the same SQL table as the external table in the template, but I could see this also being an issue in other processes.  I discovered this by accident, as it is a field that is used only at the end of a process for determining filing structure of a created shortcut, and I noticed something in the wrong place while browsing deep in the repository .

Since dynamic field lookups do not appear to trigger when a template is changed, only when a field is changed, is the recommended best practice to make this field required for the template? I could take this approach rather than the workflow approach, but I hate to force a user to make two extra clicks just to get the lookup to run, as they are not always aware that a field is dynamic and might not understand why a field isn't being auto-filled.

For clarification, we are running Laserfiche 12 server and web client, but are using Laserfiche 11 for the Windows client.