Comment on page
Manage and Build Templates
The Manage and Build Templates section is where you can upload your .docx templates for exporting. Click here for an overview of this feature.
To summarise, you can populate and export a word or pdf file with images, data lists and content and field values simply by referencing the field slug, e.g. a field called My First field would be filled as ${my_first_field} in the word doc.
By Clicking "Generate Mockup" you can get a .docx file that contains all your field slugs.
This is a feature that allows you to export the file straight from the Data results.
You can upload as many templates as you like and they will be available to choose from in the front end of the bloc.
Template files must be .docx files
Once your templates are uploaded, they will appear in the Template List where they can downloaded or deleted.
By using the field slug in this format on the document the value will replace this field: ${my_first_field}.
These fields contain html and this html will correctly convert and populate your word file.
Images will successfully appear in the word doc. You can also adjust the image size by adding numbers into the variable, for example: ${my_image_field:200:100} where 200 is the width and 100 is the height.
Digital Signatures will successfully populate into the file.
There is an advanced feature within this overall feature, where you can display lists of data in a table if the field is either a Sub Bloc or a Results Box. It displays the data from the these external blocs instead of the data in the main parent bloc that you are exporting the document from.
It works by using the filters you have set out in those fields as a means of finding the data to display.
You can see this in action in this How to Video from 18 minutes onwards.
Having a field in the child Sub Bloc that is the same name as a field in the parent bloc can cause the system to not understand which one to use, and a result either the table of data may not appear, or the parent field will be blank. It is possible to distinguish between the two by simply adding [parent] to the field slug in the doc file.
E.g. ${[parent]my_first_field}
By doing this the system will be able to distinguish between the two fields even if they have the same name.
There is also a second way these can be distinguished. You can add the field slug of the Results Box field itself before the field slug that you are loading.
E.g Supposing you have a Results Box field called Invoice Line Items and its slug is invoice_line_items.
You can be explicit about what field you are loading by adding this slug followed by a hyphen, in this example the Model Number might be model_number as part of a line item.
${invoice_line_items-model_number}
Last modified 7mo ago