Hi Everyone,
I’m facing an issue while generating a PDF from a dynamically generated Word document.
Requirement:
Issue:
What I’ve tried so far:
char(10)
(Links referenced below) Link 1: https://community.appian.com/discussions/f/plug-ins/28870/line-break-docx-from-dynamic-template Link 2: https://community.appian.com/discussions/f/plug-ins/28812/next-line-not-working-when-converting-from-docx-to-pdf Link 3: https://community.appian.com/discussions/f/general/8837/rendering-line-breaks-in-pdf
Has anyone faced a similar issue or found a reliable way to preserve line breaks when converting DOCX to PDF using this plugin?
Any help or guidance would be greatly appreciated.
Thanks in advance!
Discussion posts and replies are publicly visible
We have faced the same issue recently after updating Advanced Document Templating from version 1.1.0 to 3.2.0. As per investigation the latest plugin version has some issues and is affecting the font styling as well as formatting of pdf while docx is as per expectation. Reverting it back to the 1.x.x version resolved it. Try doing the same and check.
Harsha Sharma Thanks for the suggestion, unfortunately we don't have option to revert as the plugin with higher version (3.x) has been installed first.However, I'm able to fix the issue using new smart service "DOCX From Dynamic HTML" available in latest version.Steps followed:
Great! Good to know
This is a classic problem with dynamic document generation, especially when dealing with line breaks. It sounds like the DOCX to PDF converter within the Advanced Document Templating plugin might be interpreting the line break character differently than how the DOCX itself renders it. Have you tried using a different method for populating the DOCX, perhaps one that specifically handles rich text or markdown? Sometimes the issue lies in how the initial data is formatted before it even hits the DOCX template. It reminds me of the unpredictable physics in Ragdoll Archers ; sometimes the simplest actions have unexpected outcomes. Exploring alternative character encodings beyond just XML entities could also be a path.