This is a classic case of the tool fighting the user, and it is a battle you cannot win by force. The user here is caught in a specific, frustrating loop: a SharePoint template that breaks its own links the moment it is moved. The core problem is that Excel, in its current form, treats file paths as relative references when files live in the same SharePoint site. When the template is copied to a new folder, Excel dutifully and incorrectly updates the link to point to a copy of the source file in that new folder, rather than keeping the original path. The result is a cascade of #REF! errors, and the user is left asking for a technical lock that simply does not exist in Excel Online.
You cannot fix this by tightening a setting or using a special path format. The user's search for an "absolute path" solution is a logical idea, but SharePoint's web-based architecture doesn't honor absolute file paths in the same way a desktop file system does. The underlying issue is one of design: Excel was built for a world of static, local files, not a dynamic, collaborative cloud environment. Asking the tool to behave differently in this context is like asking a hammer to screw a nail. The user is not doing anything wrong; they are simply hitting the hard limit of what traditional spreadsheets can do in a modern workflow.
For anyone reading this who has felt that same jolt of panic when a critical link turns to #REF!, this is not a failure of your process. It is a signal that the process itself needs to evolve. The solution is not to fight the tool but to step back and ask a different question: *How should data flow between files in a connected workspace?* Instead of linking a template to a static "User List" file, which will inevitably move or be copied, consider a single source of truth that lives outside the template's folder structure. A shared data table within the same SharePoint site, or a structured list that the template can query, would remain stable regardless of where the template is stored. This approach removes the fragility of file-to-file links entirely.
The practical takeaway is direct: stop trying to lock the links, and start restructuring the data. If your workflow depends on a template that must move, then the data it references must be independent of that movement. Explore SharePoint lists as your data backbone. They are accessible from Excel Online, they do not break when a file is copied, and they are built for exactly this kind of multi-file collaboration. The path forward is not to fix a broken link, but to eliminate the need for it.