Document Editing Problems

Prevent Custom XML Changes From Being Replaced in Word Co-Authoring

Tauseeq MagsiTauseeq Magsi Nov 22, 2026 868 views

Question details

The user needs to prevent concurrent changes to mapped custom XML from replacing one another in a Word document.

Prevent Custom XML Changes From Being Replaced in Word Co-Authoring
Product
Microsoft Word and SharePoint
Device & OS
not provided
Scenario
Two users co-author a Word document containing content controls mapped to custom XML.
Observed behavior
The latest custom XML change replaces an earlier change instead of merging with it, while plain-text edits continue to co-author normally.
Before you start

Confirm that the affected content controls are mapped to custom XML and identify the SharePoint library where the document is stored. Changing library checkout settings requires appropriate SharePoint permissions.

Solution 1Recommended

Require checkout in a separate SharePoint library

Use this workflow when mapped XML must be edited without simultaneous changes from another user.

Requiring checkout prevents simultaneous editing of documents in that library. It does not merge custom XML changes, so coordinate who edits and checks in the document.

1
Prepare a separate library

In SharePoint, create or choose a document library for files that require controlled XML editing, then place the document in that library.

2
Require checkout

Open the library's Settings, select Library settings, and open Versioning settings. Under Require Check Out, select Yes and save the setting.

3
Edit and check in

In the library, select the document and use the three-dot menu to choose More > Check out. Open and edit it in Word, save your changes, then return to the library and choose More > Check in.

4
Notify the next editor

After check-in, ask the next user to check out the document before making further changes to mapped content.

Checkout affects the whole library: Documents in a library that requires checkout cannot be co-authored simultaneously. A separate library helps preserve normal co-authoring elsewhere.
Free Microsoft Office alternative

Edit Word Documents With WPS Writer

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Word format compatibility, making it easy to move everyday document editing workflows. It does not fix Word's custom XML co-authoring behavior.

Edit everyday documents in a familiar word-processing interfaceOpen and save Microsoft Word formats such as DOCXUse a free, lightweight alternative for routine document workReview shared document content without relying on Word for every editing task
microsoft office alternative - wps office

Frequently Asked Questions

Why do plain-text edits merge when custom XML changes do not?

Word supports co-authoring for ordinary document text, but mapped content controls and their custom XML do not fully support real-time merging. Concurrent changes to the XML can overwrite one another.

Can I allow co-authoring and require checkout in the same SharePoint library?

Requiring checkout prevents simultaneous editing of documents in that library. Use a separate library for documents that need controlled XML editing and another library for normal co-authoring.

How can I find an earlier version after a change is overwritten?

In the SharePoint document library, select the file, open its three-dot menu, and choose Version history. Review an earlier version and recover the needed content as appropriate; restoring a version replaces the current file with that earlier version.

Will an unmapped content control update my custom XML?

No. A content control that is not mapped to custom XML will not automatically update it. Review any dependent integrations before replacing mapped controls.

How can I request better custom XML co-authoring support?

In Word, use Help > Feedback to describe the mapped content controls, the concurrent editing steps, and the overwrite behavior. Avoid including sensitive document content in your report.