moving a document breaks link
When we are sorting out our filing system in files, creating new folders to move and tidy up our document's this changes the location of the document and breaks any links you have previously sent to users also the link in the conversations. This is extremely unworkable for our organisation, we need to be able to upload and move documents. keeping the integrity of any previous links sent. For example if you attach a document to a channel, this does not go into a folder it just sits in files, when links are sent round for this document they are broken once it is tidied up at a later date
Our org also has this problem. Many of our team's channels have 25-50 files added a week to the channel and are regularly moved to the proper project folder (Within subfolders of the channel root folder) from the channel root folder. Currently, there is a 50/50 chance that the link in the channel will no longer work. When will there be a way to repair the link or link it in a way that follows the document to the new folder within the SharePoint site?
This is so ELEMENTARY how has this not been repaired? I'm unable to rename a file without it linking to an older version what a joke?!
Has this issue been resolved? I am experiencing broken links when moving files.
John Newsom commented
This is essential for collaboration and expanded usage of Teams. We need to be able to change / improve how our files are organized and not break access for everyone that we shared links with previously.
It would be really great if this were fixed.
This would be very useful.
Mike Qu commented
This appears to have been fixed?
Peter McDermott commented
Agree--we move files across folders within channels as folders evolve. It would be helpful if links in conversations were persistent, even if a file moves.
L Joslyn commented
Yes, I thought this was supposed to be fixed if you activate the "Document ID Service" in Site Collection Features (under Site Settings) as well. But this does not seem to fix the problem.
I heard (a long while back) that everything was supposed to use IDs so this wouldn't happen. Obviously not the case right now. Any plans to move in that direction?
Kelly Stock commented
Broken links is a huge problem when we are working in programs that are constantly change and evolving and files are being moved around to align with the changes.
James Bibby commented
Agree this needs to be fixed so we have persistent links. We have two channels, one for finished products and one for current projects. When a project is finished, we copy to folder from one channel to the other. But this breaks all the links in conversations and in planner. Thus, if someone is trying to figure out what happened in an old project, they cannot easily find the documents from old conversations and planner tasks.
Any updates on this please? It's September well over 1 year since this was raised. If this is under review, what is the best alternative to advice users to move content without the risk of links breaking?
This is a bug and should be fixed!
Steve Dohm commented
Serious issue if you try to move files from a server into Sharepoint/Teams. It's a must have for us. Under review January 19,2018. It's been a year and a half. Can we get an update?!?!
Erika Young commented
At a minimum, the broken link should be allowed removed from teams file
Giulio Vannini commented
I just noticed that after moving a file if instead of clicking on the name you click on “…” and then “Edit in Teams” or “Open in …” it still seems to access the file.
Also if you select "Get Link" and choose "SharePoint" instead of "Microsoft teams" the DocID still works!!
So.. this is TOTALLY inconsistent!
- Clicking on the name in the chat resolves in a non-working TEAMS link
- Clicking on other options such as "Open in Teams" resolvers into a valid DocIS SHAREPOINT link
Is it really that difficult to fix the rest ??
We are only just starting to adopt Teams in our organisation and I am already finding lots of instances of this happening and links in conversations no longer working. It is a big concern for getting users to adopt and embrace the product fully.
J DeRose commented
This is a must-have feature for our organization to adopt. This is something which Box (and even SharePoint) have had for some time and moving to Teams is a giant step backward for many of us.
Elisa Munoz commented
Companies cannot keep up with change at the "link" level! I vote for self-keeping links.