'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Word Opening the Wrong SharePoint File After Copying
Question details
The user needs to resolve an issue where the Microsoft Word desktop client opens an incorrect, renamed Live version of a SharePoint file instead of the intended Draft version after a Power Automate workflow runs.
- Product
- Microsoft Word, SharePoint, Power Automate
- Device & OS
- not provided
- Scenario
- Opening a SharePoint document in the Word desktop app after it was moved between Draft and Live libraries and copied back by Power Automate.
- Observed behavior
- Word opens the renamed Live version of the document instead of the selected Draft version on the first attempt, despite OneDrive showing no synchronization errors.
Ensure that your OneDrive synchronization is fully up to date and that you have gathered the exact file URLs, timestamps, and library details before troubleshooting.
Clear Word Cache and Reopen the Document
Since this is often caused by Word's local caching behavior, fully closing and reopening the application can force it to load the correct file.
Microsoft Word utilizes an internal Office Document Cache that can retain the identity of previously moved files, leading it to fetch the wrong document version on the first attempt.
Completely exit the Microsoft Word desktop application to clear the current session memory.
Wait a few seconds to ensure OneDrive has completed any background sync processes and verifies the current SharePoint state.
Navigate back to the SharePoint Draft library and open the document again. Word should now fetch the correct file.
Submit a Microsoft 365 Support Ticket
Because this issue involves complex interactions between document identity, Power Automate, and SharePoint, investigating logs via official Microsoft support is the most effective resolution.
Try WPS Office for Reliable Document Management
If you are experiencing persistent synchronization and caching issues with Microsoft Office, consider switching to WPS Office. It provides a lightweight, highly compatible, and free alternative with robust local and cloud document handling.
- 1. Download WPS Office: Visit the official WPS website and download the free WPS Office suite for your operating system.
- 2. Install the Application: Run the installer and follow the on-screen prompts to set up WPS Office on your device.
- 3. Open Your Documents: Launch WPS Writer and open your existing Word documents directly with full format retention.
Frequently Asked Questions
Why does Word open the wrong version of my SharePoint file?
This usually happens due to the Office Document Cache retaining the identity of the previously moved file. When Power Automate copies a file back with the same name, Word may mistakenly retrieve the cached 'Live' version instead of fetching the new 'Draft'.
How can I prevent Power Automate from causing file identity conflicts in SharePoint?
You can try modifying your Power Automate flow to clear the original file's metadata or append a unique identifier, such as a timestamp, to the file name when copying it back to the Draft library to ensure Word treats it as a completely new document.
Does OneDrive synchronization affect this Word caching error?
While OneDrive handles local file synchronization, the issue is typically rooted in Microsoft Word's internal document cache rather than OneDrive itself. If OneDrive reports no sync errors, the caching conflict is strictly happening within the Word application.
