Hi @Jay,
Thank you for posting your question in the Microsoft Q&A forum.
Based on your description, you’re seeing Word show “Upload Failed: Location not found,” SharePoint display “The URL ‘[url]’ is invalid,” and managed‑metadata values missing from views, while new files still work. We truly appreciate the detailed information you provided and the steps you’ve already taken.
This typically occurs when recent schema changes have introduced a mismatch between the library and the Office/SharePoint clients. Publishing or republishing content types, adding a duplicate column name (such as a second Project), or altering the managed metadata binding can cause the client to misread the file’s location and the column associations. When the managed metadata column loses its term set association or internal name alignment, views that depend on that column may no longer return items.
Below are some workarounds that suit for your situation:
1/ Begin by ensuring the paths are correct and opening the library.
- Open the affected library, copy its URL, and open a sample document using Open in app. In Word, check File → Info to ensure the location matches the library URL.
- If you use OneDrive sync, sign out/in of Office, pause and resume sync, then retry from the synced location.
2/ Then, establish proper alignment between content types and metadata definitions.
- In Library settings → Content Types, keep only the authoritative managed metadata Project column. Remove the duplicate text-based Project column.
- In Site settings → Term Store, confirm the managed metadata column is bound to the correct term set.
- In Document Set settings, include Project as a shared column and apply Update content types so the shared columns are pushed to all items.
3/ Next, restore views to proper functionality and update indexes accordingly.
- Edit views that filter or group by Project to use the managed metadata column, then save.
- Go to Library settings → Advanced settings → Reindex document library.
- If the issue spans more than this library, consider Reindex site and retest with a few sample items.
4/ Finally, confirm access rights and perform diagnostics as necessary.
- Verify Edit permission and whether check-out is required.
- Update and check in one sample file to confirm changes are accepted. If the error persists, capture a browser trace (press F12 on the library page, reproduce the save, and note any 404 on the document path or 400 on list metadata calls) and share the site/library URL plus one sample server-relative path.
5/ As your account is managed by your organization, please contact your IT administrator to check your permission and policies. For a more efficient resolution, we recommend using your administrator account or contacting your IT administrator to submit a support request directly to Microsoft Support team.
They can raise a support ticket by visiting: Get support - Microsoft 365 admin | Microsoft Learn
As community moderators, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.
Thank you for your patience and your understanding. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.
I look forward to continuing the conversation.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.