Template functions

Ten helpers are available in every command without an import.

_: Lodash

The complete Lodash . Often used: _.range, _.groupBy, _.sortBy, _.uniq.

{# FOR i IN _.range(0, eingang.length) #} … {# END-FOR i #}
{#! gruppen = _.groupBy(objects, o => o[`RaumNr`] ?? `ohne Raum`) #}

pluralize(language, value, forms)

Chooses the form that fits the number. Registered languages: de and en.

{#$o[`Anzahl Teile`]#} {#pluralize(`de`, $o[`Anzahl Teile`], { one: `Teil`, other: `Teile` })#}
{#objects.length#} {#pluralize(`de`, objects.length, { one: `Objekt`, other: `Objekte` })#}

imask(value, fieldDefinition?, customMask?)

Formats numbers and strings according to imask.js . For an empty value it returns null: a bare call then renders empty, never null or NaN in the document, and imask(…) ?? `-` applies.

The configuration is resolved in three levels:

{#imask($o[`Gewicht`], f[`Gewicht`]) ?? `-`#}
{#imask($o[`Breite`], false, { mask: Number, scale: 2, thousandsSeparator: `.`, radix: `,` })#}

Level 3 depends on the user who exports. For reproducible templates use level 1 or 2. A faulty field mask never breaks the export; it falls back to level 3.

combine(value, options?)

Wraps a string or joins an array. For empty input it returns def.

{#combine($o[`Inventarbemerkung`], { pre: `(`, post: `)`, def: `k. A.` })#}
{#combine([$o[`Künstler`], $o[`Datierung`]], { sep: `, `, filterEmpty: true })#}
{#combine([parseFloat($o[`Höhe`]), parseFloat($o[`Breite`])].filter(Boolean).join(` x `), { post: ` cm` })#}

The benefit: brackets and units disappear when there is no value, instead of a lonely ( ) or cm in the document.

combine handles only strings. A number gives def, even inside an array. That is why the third example does join first and then combine. To wrap a single number, write combine(String(value), …). The option is called def, not default: an unknown option is silently ignored.

img(file, config)

Used in IMAGE commands; it produces an image for Word. file is a file object from $f or files, an image field value ($o[`Titelbild`]) or a file ID as a string.

So the default is the edited image, not the original:

{# IMAGE img($file, { width: 6 }) #}
{# IMAGE img($file, { width: 6, render: { crop: false, overlay: false } }) #}
{#IMAGE img(($o[`Titelbild`] ?? null), { width: 8, height: 6 })#}

The ?? null on an image field makes sure that objects without an image get a placeholder instead of an error. If loading fails, a placeholder image appears as well. Moliri loads identical image requests only once per export run.

Filter files before img()

$f contains all files of the object, including PDFs and documents. Files that cannot be shown directly get placeholders or generated previews, so a filter is not strictly necessary. If you want images only, filter:

{# FOR file IN $f #}
{# IF [`image`, `image_other`, `svg`].includes($file.kind) #}
{# IMAGE img($file, { width: 6 }) #}
{# END-IF #}
{# END-FOR file #}

The valid values for kind are listed under Supported formats .

fdate(value, format?)

Formats ISO date values, including those with a time. The format is in the command, so the result is the same for all users.

Behaviour at the edges:

• Empty values and 0000-00-00 give null. That renders empty, and ?? applies.
• Incomplete dates are shortened: 2025-00-00 becomes 2025, 2025-03-00 becomes 03.2025 or März 2025.
• Values that do not start with an ISO date (free text such as um 1900, “around 1900”) come back unchanged.
• An unknown format counts as TT.MM.JJJJ.

{#fdate($o[`Eingangsdatum`])#} bis {#fdate($o[`Rückgabedatum`])#}
{#fdate($o[`Datierung`], `JJJJ`) ?? `o. J.`#}
{#fdate(p.start_date, `T. Monat JJJJ`)#}

fcheck(value, yes?, no?)

Outputs a switch field as text. An empty value counts as “no”, as does anything that looks like a negation: 0, nein, no, false, aus, off, ❌ and similar. Everything else counts as “yes”. This way fcheck also reads switches with custom stored values correctly.

Without further arguments, the labels come from the view settings of the person exporting:

{#fcheck($o[`Kurierbegleitung`])#}                → view settings
{#fcheck($o[`Kurierbegleitung`], `Ja`, `Nein`)#}  → fixed label

ffmt(record, key)

Outputs the value of a field as its output formatter formats it. The first parameter is the record, $o or the loop variable of a loop:

{#ffmt($o, `Maße`) ?? ``#}
{#ffmt($o, `Maße.Objekt`)#}
{#ffmt($o, `Leihgeber`) ?? `-`#}
{# FOR obj IN objects #}{#ffmt($obj, `Maße`)#}{# END-FOR obj #}

Without a formatted value it returns null, and ?? applies. Keys with an entry (.) and a variant (#), and the built-in formatting for each field type, are described under Output formatters in templates .

ui: view settings

Not a call, an object. Keys and the warning are under Template variables .

{#$o[`Datierung`] ?? ui.null_replacement#}
{#fdate($o[`Eingangsdatum`], `auto`)#}

deco(annotations, config)

Carries field annotations over into the report: a field’s colour marking as the background of the building block, comment and source as a Word comment.

You set this up in the template editor, not by hand. In the panel Moliri · Insert & edit, every field you insert and every building block you click has the section Additional details with the rows Colour, Comment and Source. There you choose which field provides the colour and which fields contribute comments and sources. Moliri saves the choice on the building block’s content control and inserts the matching call itself on export, in loops with the annotations of each object.

The generated call looks like this:

{# deco($m, { color: `RegNr`, comments: [`RegNr`], sources: [] }) #}

Without an annotation the call gives an empty string; no empty marking is created.

JavaScript in the command

Besides the helpers, simple expressions work directly:

{# INS [$o[`Feld A`], $o[`Feld B`]].filter(Boolean).join(`, `) #}

For more involved logic, a preparatory EXEC step at the start of the document is easier to follow than nested one-liners. See Recipes .

Helpers and expressions run in isolation. They see only the helpers on this page and the data Moliri has loaded for the export. They cannot reach the network (fetch, WebSocket, outside scripts), nor the browser storage with the login; the check reports such a call as Not allowed: …. A run may take 60 seconds, not counting the time for loading images. The details are under Execution and errors .

Further reading

• Template syntax : the commands
• Template variables : the data context
• Output formatters in templates : ffmt and $fmt in detail
• Recipes : patterns to copy