Line break Docx From Dynamic Template

RE: Line break Docx From Dynamic Template

Mike Schmitt — Tue, 07 Apr 2026 14:48:09 GMT

[quote userid="238566" url="~/discussions/f/plug-ins/28870/line-break-docx-from-dynamic-template/154161"]

Generated docs has this:

</w:t><w:br/><w:t>Text Data </w:t><w:br/><w:t>

[/quote]

Your generated doc is receiving sanitized text (instead of the literal "<" and ">" symbols), which will not work. To get the wordML trick to work, the literal symbols must be passed in.

RE: Line break Docx From Dynamic Template

keerthik0010 — Tue, 07 Apr 2026 12:18:58 GMT

Hi Cugino95,

How did you solve it?

Could you help with exact expression to solve this problem?

My issue is:

Text entered in a paragraph field on UI.
Generated DOCX from dynamic template shows the new lines entered in the paragraph field fine.
PDF from DOCX(generated docx) is not showing the new line but in same line.

Tried below snip:

substitute(
  ri!multiLineText,
  char(10),
  "</w:t><w:br/><w:t>"
)

Generated docs has this:

</w:t><w:br/><w:t>Text Data </w:t><w:br/><w:t>

Thanks

RE: Line break Docx From Dynamic Template

cugino95 — Thu, 15 Jun 2023 20:54:56 GMT

thx Mike, I resolved with "
" as line break using advanced document templat

RE: Line break Docx From Dynamic Template

Mathieu Drouin — Tue, 06 Jun 2023 00:11:01 GMT

Did you try the solution in this thread? community.appian.com/.../rendering-line-breaks-in-pdf

RE: Line break Docx From Dynamic Template

Mike Schmitt — Mon, 05 Jun 2023 20:26:39 GMT

"<br>" is HTML - to do manual trickery with Word files, you need to use the Word-flavored XML codes (not HTML), aka WordML. I'm not exactly sure what syntax you'd need to use to do this within the Docx from Dynamic Template smart service, but the WordML carriage return is: <w:br/>

In the "word document from template" (older) smart service, it's possible to use the above by passing it in after a "text breakout" flag ("</w:t>") and then following it with another "text start" flag ("<w:t>"). Without doing these first it just tries to render as plaintext (though also the "<" and ">" characters cause issues if not sanitized first). Again, it's all liable to be different in the "...Dynamic Template" smart service, so you'll need to experiment.