Skip to main content
M
mathewl
May 22, 2026
Solved

Formatting for MS 2007 Word Doc from Template no longer working under Appian Version 26.3

  • May 22, 2026
  • 6 replies
  • 0 views

The organization I'm working with recently had their Appian environments upgraded to 26.3 and it appears that the documented method for passing formatted text to the MS Word template using the MS 2007 Word Doc from Template smart service no longer works. Before the upgrade, when passing text to the template via the smart service, all newlines (char(10)) were replaced with the Word ML tag <w:br />, which would allow the formatting in the replacement text to be preserved. However since the upgrade, the formatting is lost and the <w:br /> tag is visible in the generated document. Using other formatting characters like <br/> or char(10), char(13) doesn't seem to fix this, how to we proceed from here?

Best answer by jesush905075

Please open a ticket in myAppian. Support can fix the issue without needing a restart. The issue is well known and has already been addressed and resolved

6 replies

J
jesush905075Answer
May 22, 2026

Please open a ticket in myAppian. Support can fix the issue without needing a restart. The issue is well known and has already been addressed and resolved

    M
    mathewlAuthor
    May 26, 2026

    Would you be able to post a screenshot of where the toggle option is located? Our organization's Appian instances have all been upgraded to the latest Hotfix for 26.3 and I'm unable to locate the XML characters escape toggle option described in the release notes.

    J
    jesush905075
    May 27, 2026
    I don't know that info so I would suggest asking about it in the ticket, especially if you're working on on-premise instances. We're working in the cloud, so the Appian Support team changed it directly after we opened a support case raising this issue.

    shubhama926776
    shubhama926776
    May 23, 2026

    Known 26.3 regression with the legacy MS 2007 smart service. <w:br/> is being escaped instead of rendered.
    Log a case with Appian Support.

    S
    saideepanr5815
    May 28, 2026

    Facing similar issue after 26.3 upgrade. We are on cloud and have the latest hotfix 26.3.240.0 applied to our environment. What reference can I provide to Appian Support to address this?

    Terms & ConditionsAccessibility statement