Template Syntax

1. Fields

{{customer.name}}
{{customer.address.city}}
{{lines[0].item}}

• Dots walk into nested objects: {{customer.address.city}}.
• Array indexes are zero-based and can repeat: {{lines[0].item}}, {{a[0][1]}}.
• Field names must look like identifiers — a letter or underscore, then letters, digits or underscores.

2. Formatters

{{total:N2}}                 1234.5    ->  1,234.50
{{invoiceDate:yyyy-MM-dd}}   a date    ->  2026-08-13
{{startTime:HH:mm:ss}}       a time    ->  09:30:00

Append :format to a field to format it. Formats are standard .NET format strings, applied using the culture you pass in Options.culture (for example "en-GB"); leave it unset for invariant culture.

Which rule applies is decided by the value’s own type, not by the format string:

Without a formatter, a value renders as its raw text: numbers keep exactly the digits the data had (so 30.00 stays 30.00, not 30), booleans render true/false, and null renders empty.

3. Loops — Word

{{#each lines}}
  {{item}}: {{qty}} x {{price:N2}}
{{/each}}

Inside the block, the current context becomes each array element in turn, so bare tokens like {{item}} resolve against that element.

The target must be an array. Anything else is TEMPLATE_EACH_TARGET_NOT_ARRAY; a missing path is TEMPLATE_FIELD_MISSING unless onMissing is blank, in which case the block simply renders nothing.

4. Conditionals — Word

{{#if poNumber}}PO: {{poNumber}}{{/if}}
{{#unless poNumber}}No purchase order on file.{{/unless}}

{{#if}} keeps its content when the value is truthy; {{#unless}} keeps its content when it is falsy.

Which region gets kept or removed follows the same row / row-group / paragraph rules as loops above.

4b. Totals and counts

A template can add up its own line items, so an invoice does not need its Subtotal, VAT and Total calculated somewhere else and stored on the record first.

{{#each lineitems}}{{name}}  {{qty}}  {{price}}
{{/each}}
Lines:    {{count:lineitems}}
Subtotal: {{sum:lineitems.price:N2}}
Cheapest: {{min:lineitems.price}}

The last segment is the field, everything before it is the collection. So {{sum:account.lineitems.amount}} totals amount across account.lineitems. Formatters apply to the result: {{sum:lineitems.price:N2}}. Inside a loop, the path resolves against the current item, so {{sum:items.value}} within {{#each groups}} totals each group separately.

{{rows.length}} is not supported — use {{count:rows}}.

Format money with :N2 and a literal symbol — Total: £{{sum:lineitems.price:N2}}. The :C formatter currently renders the generic currency sign ¤ rather than your own, because the render culture is invariant.

5. Images — Word

{{image:logo width=40mm}}
{{image:signature height=15mm}}
{{image:stamp width=25mm height=25mm}}

The name after image: is looked up in the images map you pass in the call’s options — a name to image-bytes map. PNG and JPEG are supported, and the format is detected from the bytes rather than from any file name.

6. Built-in tokens

A few ambient values are merged in automatically, so a template can say “when was this generated” without anyone supplying it:

{{date:yyyy-MM-dd}}   ->  2026-08-13
{{now:HH:mm}}         ->  14:23
{{user.name}}         ->  Alex Admin

• Real data always wins. If your data already has a top-level field with one of these names, yours is used.
• Time zone. Dates are converted into the calling user’s own Dataverse time zone, using Dataverse’s own conversion, so daylight saving is handled correctly. In a flow, the “calling user” is the account the flow runs as — set that account’s time zone deliberately.
• Never a failure. If the time zone cannot be resolved for any reason, the value falls back to UTC and the document still renders. A time zone lookup will never be the reason a generation fails.
• user.name and user.email are best-effort. They are resolved on the row-bound path. When generating from JSON you supply, they are not resolved, and referencing them behaves like any other missing field.

7. Generating from a Dataverse row

When a document is generated from a record — the Generate document button, or the row-bound actions — the data is built for you from the template’s binding. Everything above still applies; this section describes the shape your tokens walk.

{{account.statuscode}}        ->  Active      (formatted — what a user would see)
{{account._raw.statuscode}}   ->  1           (raw — the underlying value)

{{#each account.contacts}}
  {{fullname}} — {{jobtitle}}
  {{#each activities}}
    Task: {{subject}}
  {{/each}}
{{/each}}

{{#each account.primarycontact}}Primary contact: {{fullname}}{{/each}}
{{account.primarycontact[0].fullname}}     equivalent, if you know there is exactly one

8. Why tokens survive Word's editing

Word routinely stores what you typed as one token across several internal fragments — {{cus / tomer. / name}} — after a spellcheck pass, a copy-paste, or simply a second editing session. It is invisible in the UI and very real in the file.

VerseDocs handles this transparently: it reads each paragraph as one continuous string, finds tokens there, and writes the value into the first fragment the token touched, keeping that fragment’s formatting. Text and formatting outside the token are never disturbed. PowerPoint gets the identical treatment.

9. Headers and footers

Tokens in headers and footers render exactly like tokens in the body — same engine, same rules. Footnotes and endnotes are not rendered.

10. Excel templates

Put {{path}} in any cell on any worksheet. Fields and formatters behave exactly as in sections 1 and 2.

• Formulas are never touched. A cell starting = is left exactly as authored.
• A cell containing only one plain token keeps its type. A cell whose entire content is {{price}} — no surrounding text, no formatter — becomes a real Excel number, so formulas referencing it still compute. Any other shape produces a text cell.

11. PowerPoint templates

Fields, formatters, loops and conditionals all work in decks, using the same grammar and the same scoping rules as Word — plus one rule decks have and documents cannot.

Tokens work anywhere text goes: titles, body placeholders, any text box, and table cells, which need no special syntax. Slide content is rendered; slide masters and layouts are not.

Slide 1:  Catalogue {{#each products}}
Slide 2:  Product: {{name}}      <- repeats per product
Slide 3:  End {{/each}}

12. Template error codes