Additional Templates

in addition to primary document templates, unaric reports provides specialized templates for pulling live salesforce data, integrating external analytics, and automating esignature workflows burst variables include variables from your burst report in your documents when you include a burst report in your solution, all fields from that report are available as variables the format for the variables is {{field api name}} for example, if you had a account name field, then the variable name would be {{account name}} to get a list of all variables, run the report and open the variables view data record variables when you include a data report in your solution, all the fields from that report are available as variables the format for the variables is {{alias field api name}} for example, if you had a name field and your alias was product, then the variable name would be {{product name}} to get a list of all variables, run your report and open the variables view images you can embed images into your documents the image url must be included in the burst or data report and the image must be publically accessible to add a mergeable image, add an image to your document template and set the id as the variable name from the burst or data record report for example, if you had a field opportunity test url c , then the variable name would be {{opportunity test url c}} and you would set that as the id on the image using the layout > selection pane in word as shown in the image esign add esign features into your documents autoplace fields you can add the following fields to your document templates field type signer 1 signer 2 signer 3 signer 4 signature \s1\ \s2\ \s3\ \s4\ initial \i1\ \i2\ \i3\ \i4\ optional initial \oi1\ \oi2\ \oi3\ \oi4\ date signed \d1\ \d2\ \d3\ \d4\\ for example, this solution and document template requires signatures from two people you will need to hide these variables so they don't show up on the final document to do that, you should set the text colour to white merge fields (if statements) in most cases, you don't need to use merge fields in word document templates, as you can just use the {{variable name}} syntax described in these helps docs however, if you need to add an if statement within word, you can do that using merge fields and populate them using your variables you can also use the metric header values as merge fields; you can do this, for example, to hide an entire section of a document if there are rows in the report setup turn on field code view in microsoft word, press alt + f9 you will now see field codes instead of merge field results insert the if field (do not type the braces!) place your cursor where the if should go and press ctrl + f9 word will insert special field braces { } (typing braces manually does not work) inside the braces type if (leave space after if ) insert the merge field inside the if statement press ctrl + f9 again to create nested braces { } inside braces type mergefield metric value1 leads complete the if statement so it looks like this (exact spacing) { if { mergefield metric value1 leads } <> "0" "" "" } insert the conditional content click between the first pair of quotes and press enter paste or type the entire block (paragraphs, tables, merge fields, etc ) everything between those first quotes is shown only when the condition is true update the field press alt + f9 again to return to normal view press ctrl + a , then f9 this will update all merge fields in the document html text by default, all salesforce text area (rich) fields are merged into word as html, preserving formatting all other fields are merged in as regular text if you have html in standard text fields and you want to preserve formatting, add this token anywhere in your document {{insert all text as html}} lists you can add output the data from a source report as simple list the syntax for list is {{tablelist\ alias\ field api name\ delimiter}} for example, say you want to burst an account report that included a list of each account's opportunity names separated by commas you would add a source report with a field opportunity name to the solution with an alias of opportunity then you would add the following token to the document template {{tablelist\ opportunity\ opportunity name ,}} the finalized document will look like this hyperlinks you can add dynamic hyperlinks to any text using variables from your report the syntax for the text that is displayed is {{field api name}} and for the url is field api name (no brackets) for example, say you wanted to have a hyperlink on the account name you would set it up as follows (note that id fields are special fields that contain the full salesforce url to the record this is why you can use just the id field below and it will be replaced with the full url to the record in salesforce) the output will look like this