KB-1819 Word Doc from Template Smart Service fails to replace placeholders

Jordan Horwat — Wed, 06 Mar 2019 13:58:47 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 3/6/2019 1:58:47 PM

Symptoms

When using the Word Doc from Template Smart Service with a runtime template, some substitution keys (placeholders surrounded by three pound symbols, e.g. ###section###) are successfully recognized in the setup tab but are not replaced in the output document.

Cause

Microsoft Word is automatically formatting the text which creates extra XML tags in the template. If the XML formatting of the template and the runtime template do not match, then the substitution key will not be replaced.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-125621.

Action

To ensure that neither the base template nor the runtime template have malformed XML tags, perform the following steps for all templates:

Copy the entire contents of the template docx and paste it into a new docx.
Before saving the new document, disable spelling and grammar checks in Microsoft Word. These settings can be found at File > Options > Proofing > Check spelling as you type / Mark grammar as you type.
Save and upload the new document to Appian.

To determine if a template document has malformed XML, save the template docx as XML in Microsoft Word and investigate the XML. Properly formed XML will have contiguous substitution keys including the pound symbol delimiters. For example, the XML for substitution key "###sectionNumber###" may look like this:

<w:r><w:t>###sectionNumber###</w:t></w:r>

If the XML is malformed, the substitution key will be interrupted with extra XML tabs:

<w:r><w:t>###section</w:t></w:r><w:r w:rsidR="00CA73EC"><w:t>Num</w:t></w:r><w:bookmarkStart w:id="0" w:name="_GoBack"/><w:bookmarkEnd w:id="0"/><w:r w:rsidR="00CA73EC"><w:t>ber</w:t></w:r><w:r><w:t>###</w:t></w:r>

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2019

Tags: known issues, smart-service, documents, integration, open issues

KB-1819 Word Doc from Template Smart Service fails to replace placeholders

Jordan Horwat — Wed, 06 Mar 2019 13:57:35 GMT

Revision 20 posted to Appian Knowledge Base by Jordan Horwat on 3/6/2019 1:57:35 PM

Symptoms

Cause

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-125621.

Action

To ensure that neither the base template nor the runtime template have malformed XML tags, perform the following steps for all templates:

Copy the entire contents of the template docx and paste it into a new docx.
Before saving the new document, disable spelling and grammar checks in Microsoft Word. These settings can be found at File > Options > Proofing > Check spelling as you type / Mark grammar as you type.
Save and upload the new document to Appian.

<w:r><w:t>###sectionNumber###</w:t></w:r>

If the XML is malformed, the substitution key will be interrupted with extra XML tabs:

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2019

Tags: smart-service, documents, integration

KB-1819 Word Doc from Template Smart Service fails to replace placeholders

Parmida Borhani — Mon, 04 Mar 2019 21:31:08 GMT

Revision 19 posted to Appian Knowledge Base by Parmida Borhani on 3/4/2019 9:31:08 PM

Symptoms

Cause

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Workaround

To ensure that neither the base template nor the runtime template have malformed XML tags, perform the following steps for all templates:

Copy the entire contents of the template docx and paste it into a new docx.
Before saving the new document, disable spelling and grammar checks in Microsoft Word. These settings can be found at File > Options > Proofing > Check spelling as you type / Mark grammar as you type.
Save and upload the new document to Appian.

<w:r><w:t>###sectionNumber###</w:t></w:r>

If the XML is malformed, the substitution key will be interrupted with extra XML tabs:

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2019

Tags: smart-service, documents, integration

KB-1819 Word Doc from Template Smart Service fails to replace placeholders

Parmida Borhani — Mon, 04 Mar 2019 21:29:32 GMT

Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 3/4/2019 9:29:32 PM

Symptoms

Cause

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Workaround

To ensure that neither the base template nor the runtime template have malformed XML tags, perform the following steps for all templates:

Copy the entire contents of the template docx and paste it into a new docx.
Before saving the new document, disable spelling and grammar checks in Microsoft Word. These settings can be found at File > Options > Proofing > Check spelling as you type / Mark grammar as you type.
Save and upload the new document to Appian.

<w:r><w:t>###sectionNumber###</w:t></w:r>

If the XML is malformed, the substitution key will be interrupted with extra XML tabs:

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

KB-1819 Word Doc from Template Smart Service fails to replace placeholders

Jordan Horwat — Wed, 12 Dec 2018 19:42:50 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 12/12/2018 7:42:50 PM

Symptoms

When using the Word Doc from Template Smart Service, some substitution keys (placeholders surrounded by three pound symbols, e.g. ###section###) are successfully recognized in the setup tab but are not replaced in the output document.

When the template DOCX is saved as XML, XML tags are placed in the middle of the substitution key. For example, the XML for substitution key "###sectionNumber###" may incorrectly be split up as shown here:

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian. Confirm that the generated XML is properly formatted with the complete substitution keys uninterrupted by XML tags.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT KB-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Wed, 12 Dec 2018 09:34:35 GMT

Revision 16 posted to Appian Knowledge Base by Daniel DeVeau on 12/12/2018 9:34:35 AM

Symptoms

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Parmida Borhani — Wed, 12 Dec 2018 01:27:54 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 12/12/2018 1:27:54 AM

Symptoms

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Tue, 11 Dec 2018 16:47:45 GMT

Revision 14 posted to Appian Knowledge Base by Daniel DeVeau on 12/11/2018 4:47:45 PM

Symptoms

When using the Word Doc from Template Smart Service, some substitution keys (placeholders surrounded by three pound symbols, e.g. ###section###) are successfully recognized in the setup tab but are not replaced in the output document.

When the template DOCX is saved as XML, XML tags are placed in the middle of the substitution key. For example, the XML for substitution key "###sectionNumber###" may incorrectly be split up as shown here:

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Rebecca Jonas — Tue, 11 Dec 2018 12:28:41 GMT

Revision 13 posted to Appian Knowledge Base by Rebecca Jonas on 12/11/2018 12:28:41 PM

Symptoms

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Tue, 11 Dec 2018 11:29:09 GMT

Revision 12 posted to Appian Knowledge Base by Daniel DeVeau on 12/11/2018 11:29:09 AM

Symptoms

When the template DOCX is saved as XML, XML tags are placed in the middle of the susbstitution key. For example, the XML for substitution key "###sectionNumber###" may incorrectly be split up like so:

The correct XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Tue, 11 Dec 2018 11:21:52 GMT

Revision 11 posted to Appian Knowledge Base by Daniel DeVeau on 12/11/2018 11:21:52 AM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder. For example, the XML for substitution key ###sectionNumber### may incorrectly look like:

when the expected XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are automatically formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Tue, 11 Dec 2018 11:09:26 GMT

Revision 10 posted to Appian Knowledge Base by Daniel DeVeau on 12/11/2018 11:09:26 AM

Symptoms

when the expected XML is:

<w:r><w:t>###sectionNumber###</w:t></w:r>

Cause

Microsoft Word spelling/grammar checks are formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Wed, 05 Dec 2018 18:10:16 GMT

Revision 9 posted to Appian Knowledge Base by Daniel DeVeau on 12/5/2018 6:10:16 PM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

For example, the XML for substitution key ###sectionNumber###

Cause

Microsoft Word spelling/grammar checks are formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT INT-XXXX Word Doc from Template Smart Service fails to replace placeholders

Daniel DeVeau — Wed, 05 Dec 2018 16:36:27 GMT

Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 12/5/2018 4:36:27 PM

Symptoms

When using the Word Doc from Template Smart Service, some substitution keys (placeholders surrounded by three pound symbols) are successfully recognized in the setup tab but are not replaced in the output document.

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling or grammar errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service fails to replace placeholders

Rebecca Jonas — Wed, 05 Dec 2018 11:39:45 GMT

Revision 7 posted to Appian Knowledge Base by Rebecca Jonas on 12/5/2018 11:39:45 AM

Symptoms

When using the Word Doc from Template smart service, some substitution keys (placeholders surrounded by three pound symbols) are successfully recognized in the setup tab but are not replaced in the output document.

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word has not reported any spelling errors.

Action

Disable spelling and grammar checks before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service fails to replace placeholders

Daniel DeVeau — Tue, 04 Dec 2018 18:05:40 GMT

Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 6:05:40 PM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

This issue can occur even if Microsoft Word is not reported any spelling errors.

Action

Ensure any spelling and grammar checks are disabled before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service fails to replace placeholders

Daniel DeVeau — Tue, 04 Dec 2018 18:04:12 GMT

Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 6:04:12 PM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

Action

Ensure any spelling and grammar checks are disabled before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service fails to replace placeholders

Daniel DeVeau — Tue, 04 Dec 2018 18:03:44 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 6:03:44 PM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

Action

Ensure any spelling and grammar checks are disabled before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

This article applies to Microsoft Office 365.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service fails to replace placeholders

Daniel DeVeau — Tue, 04 Dec 2018 18:03:16 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 6:03:16 PM

Symptoms

When examining the XML of the template document (by saving the DOCX as XML), XML tags are placed in the middle of the placeholder.

Cause

Microsoft Word spelling/grammar checks are formatting the text, which creates XML tags in the template that render the substitution key unrecognizable.

Action

Ensure any spelling and grammar checks are disabled before saving the template document and uploading it to Appian.

For more information, review the Word Doc From Template documentation.

Affected Versions

This article applies to all versions of Appian.

This article applies to Microsoft Office 365.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service generates extra unexpected templates

Daniel DeVeau — Tue, 04 Dec 2018 17:48:01 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 5:48:01 PM

Symptoms

ate.

Cause

Action

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration

DRAFT-XXXX Word doc from template smart service generates extra unexpected templates

Daniel DeVeau — Tue, 04 Dec 2018 13:16:40 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 12/4/2018 1:16:40 PM

Symptoms

When using the Word Doc from Template smart service, unexpected merge fields are being generated that do not align with the merge template docx.

Cause

Action

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: smart-service, documents, integration