Template will not save, publish or render: a tag, expression or the HTML is wrong

Question 1

Why do I see "body_html: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 2

Why do I see "header_html: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 3

Why do I see "footer_html: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 4

Why do I see "title_template: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 5

Why do I see "subject: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 6

Why do I see "body: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 7

Why do I see "actions[].config.: (line )"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 8

Why do I see "The HTML exceeds 500 KB"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 9

Why do I see "Please correct the highlighted fields."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 10

Why do I see "Template could not be rendered: <error>"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 11

Why do I see "PDF could not be produced: <error>"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 12

Why do I see "Word document could not be produced: <error>"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 13

Why do I see "Choose what to repeat over."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 14

Why do I see "The row name may contain letters, digits and underscores."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 15

Why do I see "Put the cursor inside a table row first."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 16

Why do I see "Write a condition."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 17

Why do I see "Put the cursor inside the block to wrap."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 18

Why do I see "The extra context is not valid JSON."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 19

Why do I see "Choose an entity to preview the template against."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 20

Why do I see "Create the template first; it then renders here against any record."?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 21

Why do I see "Use at most 10 characters"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Question 22

Why do I see "Letters and digits only"?

Accepted Answer

Templates are checked twice. When you save or publish, every field that may carry merge tags is
parsed: an unclosed merge tag, a condition without its end tag, a stray brace or a typo in a tag
stops the save, with the field name and the line so you can find it. A template that would break
on every record is never allowed into use.

Parsing cannot know what a record will contain. Filling in happens at preview, generation and
sending, and that is where a valid tag can still fail: an amount filter applied to a field that
holds text, a comparison of a date with a number, a loop over something that is not a list. The
renderer stops with the underlying error rather than produce a wrong letter; missing values on
their own do not fail (they render blank).

The PDF and Word engines take the rendered HTML. CSS or nesting they cannot lay out (unusual
positioning, broken tables, unsupported fonts) fails there, after the merge succeeded. Word output
is a plain conversion of the body and keeps less of the layout than the PDF.

The si 1. Find the line. In the editor press View HTML (or read the merge tags in the body) and go
   to the line the message names; the count is over the stored HTML, so the line is approximate
   for long paragraphs. Fix the tag: close every merge tag with the same kind of brace it opened
   with, end every condition and every loop with its end tag (the Show when and Repeat row
   tools add both ends for you), and use only the fields listed under Merge fields. Then
   Save draft again. You need the Edit permission on Document Templates
   (for message templates, the Edit permission on Message Templates; for rules, the Edit
   permission on Workflow Rules).
2. For an empty body on Publish, write or paste the content first, Save draft, then
   Publish (the Publish permission on Document Templates).
3. For a rendering error, read the text after "Template could not be rendered:". It names the
   filter or operation that failed. Check the record you previewed against: use the
   Preview with a record that has the values
   filled, apply the amount filters listed under Formatting in Merge fields (inr,
   words) to amounts only and date to dates only, and guard optional parts with Show
   when.
4. For a PDF or Word failure, simplify the HTML around the place named after "PDF could not
   be produced:": remove pasted styling from other programs, keep tables regular (no cell that
   spans past the row), and use the fonts offered under Font. Re-run Preview, then
   Open PDF.
5. For the si

Template will not save, publish or render: a tag, expression or the HTML is wrong

Messages this explains

Template will not save, publish or render: a tag, expression or the HTML is wrong

What you see

Why it happens

How to fix it

Related