Overview:
A user checks-out a document that contains Merge Fields. The user edits the document and checks it back into Vault. The Merge Fields tokens are not populated in the Vault.
Root Cause:
The issue occurs during this scenario. The user:
- Creates a new additional document file in the local.
- Copies the Merge Fields tokens from the downloaded source document to the newly created one
- Checks-in the newly created document back to the Vault.
Solution:
Some metadata in the Word file can be lost when the user copies and pastes from one document to another.
A best practice is to check-in the same document instead of creating a new one and copying the content over.
Related Documentation:
Vault Help Documentation: Troubleshooting Renditions