Office Compatibility Issues

Fix Word Mail Merge INCLUDETEXT Fields Failing After Office Update

Rana GarciaRana Garcia Oct 26, 2026 868 views

Question details

Users need to resolve an issue where Word Mail Merge documents utilizing INCLUDETEXT fields show security warnings and fail to process after an Office update.

Fix Word Mail Merge INCLUDETEXT Fields Failing After Office Update
Product
Microsoft Word
Device & OS
not provided
Scenario
Executing a mail merge operation using documents that contain chained INCLUDETEXT fields linked to read-only templates.
Observed behavior
The INCLUDETEXT fields fail to pull in the linked documents and display security warnings, despite the linked files residing in trusted network or local locations.
Before you start

Ensure you have file management permissions to modify the properties of your linked Word templates, and check your current Microsoft Office version number (specifically if it is version 2207 or newer).

Solution 1Recommended

Make Linked Templates Writable

Changing the read-only status of your linked Word templates to writable can bypass the newly introduced security blocks and allow INCLUDETEXT fields to process correctly.

Testing indicates that the failure primarily triggers when linked Word templates are set to read-only, especially when those templates contain chained INCLUDETEXT fields. Making these files writable acts as an immediate workaround.

1
Locate the Template

Open File Explorer and navigate to the folder containing your linked Word templates.

2
Modify File Properties

Right-click the template file and select 'Properties' from the context menu.

3
Disable Read-only

Under the General tab, uncheck the 'Read-only' attribute box, click 'Apply', and then click 'OK'. Repeat this for all templates in the chain.

Make Linked Templates Writable
Multi-Client Environments: If you are working in a multi-client environment where templates must remain read-only to prevent unauthorized edits, this workaround may not be suitable, and you should consider rolling back your Office version.
Free Microsoft Office alternative

Try WPS Office for Seamless Mail Merge Processing

If recent Microsoft Office updates have broken your automated mail merge workflows with INCLUDETEXT fields, consider switching to WPS Office. WPS Office is a free, lightweight alternative that provides excellent compatibility with Microsoft Word formats and reliable mail merge capabilities without these specific update-related security blocks.

  1. 1. Download WPS Office: Visit the official WPS Office website to download and install the free software suite.
  2. 2. Open Your Documents: Launch WPS Writer and open your primary Word document along with your data source.
  3. 3. Execute Mail Merge: Navigate to the Mailings tab in WPS Writer to manage your merge fields and complete the mail merge process seamlessly.
Highly compatible with Microsoft Word (.docx, .doc, .dotx) formatsReliable and straightforward Mail Merge functionalityFree, lightweight, and fast to installFamiliar user interface requires no learning curve
microsoft office alternative - wps office

Frequently Asked Questions

What causes the INCLUDETEXT failure in recent Office updates?

The failure is primarily triggered by security changes introduced in Office version 2207 and later when dealing with chained INCLUDETEXT fields that are linked to read-only templates.

Do Trusted Locations bypass this INCLUDETEXT error?

No, user testing indicates that the error and security warnings persist even when the linked files and templates are placed in designated Microsoft Office Trusted Locations.

Is the macro-blocking update in Office 2209 responsible for this?

No, testing and documentation indicate that the macro-blocking changes introduced in version 2209 are likely unrelated to this specific INCLUDETEXT field failure.

Can I keep my templates read-only for multiple clients while fixing this?

If the templates must remain read-only to support multiple clients safely, the current writable-file workaround will not suffice. You will need to roll back to an earlier Office version (like 2206) or escalate the bug to Microsoft Support.