Earn up to $250 in gift cards this summer. Find out how.

Why Aren't My Merge Fields Updating?


  • Merge fields are not populating when creating a new document from a template
  • Merge fields appear unchanged when creating a document from a template


  • Clio Manage

Additional Information:

  • For more information about Conditional Text Fields: Click Here


There are a few possible causes:

  1. The Custom Field type was changed
  2. The Microsoft Word document being used for the template contains content control fields. Word Document is using Conditional Fields

Resolution I:

If the matter/contact custom field type was changed, you would need to copy the merge field again and paste it into your template, because the merge field format would change.


Resolution II:

Content Control: Remove content control fields and paste all desired Merge Fields from Clio as plain text. Content control fields are not supported in Clio's Document Automation at this time. 


If you would like to submit this Feature Request, please contact us either through email support@clio.com, the in-app chat, or via our Clio Support Center at +1-888-858-2546 ext 2.


Conditional Text Fields:

Due to limitations in how MS Word updates fields, you may not see your conditional fields updated appropriately after generating a document through Clio. In most cases, you will have to open the newly generated Word document and manually update all fields in order to see the appropriate values of your conditional statements. To do so, select all content in your document (using Ctrl+a) then hit F9 on Windows (or fn+F9 on a Mac) on your keyboard to update all fields in your document. You will then have to save the document and re-upload it to Clio, unless you are editing the document using Clio Launcher.

If updating the fields in your generated Word document does not fix the problem, then you will need to determine if the conditional field has any errors. To do that, use your template to generate a PDF in Clio, then view the PDF. If the field appears correctly on the PDF, then you can be assured that your conditional field is working properly. If the field is not appearing correctly in the PDF, then you will need to go back to your template and look for problems in the field construction and syntax.



Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality