Re-naming file error - Sorry, we couldn't find your file
I started a conversation on a file, which posted it into the conversation feed
Then I went to the Files tab and renamed the file
Now when I click the file at the top of the existing thread in the conversation stream, it says "Sorry, we couldn't find your file."
Basically when you rename a file, the existing post of that file in the conversation feed does not know the file has been renamed
Bump again! We often rename (and move) files and this breaks the link in the Posts area. It makes life very difficult because then we have to dig around and try to find the renamed file in the Files area.
What boggles my mind is that the renamed file - when you find it in the Files area and click on it - still shows the Post conversation. So Teams retains the data connecting the renamed file and its conversation... so why can't the Posts area just use that data to keep the link current?
John Tropea commented
I'd like to hear an official response on this one as this is roadblocking some of my customers
- members upload files in posts
- team owner goes to Files tab and rename some files and moves them into folders
- existing posts with those attached files no longer preview the file (basically you get an error)
Matt Baker commented
The problem in a video:
Further to my comment about the experience in the desktop and web clients , I can confirm that the URL resolves fine in the iOS Teams app !
the request here is that the URL displayed in the Teams conversation is a dynamic URL and does not hard code the original file name.
We have noticed that when a conversation has been created in a channel due to commenting activity on a file in the files tab associated with the channel, the Teams URL has the file name hardcoded in the URL (i.e. <filename>.docx) . If the file name is changed , the Teams URL stays the same and therefore we get the "couldn't find your file" message. However, the SharePoint URL (which can be obtained from the ellipsis -> get link -> sharepoint option) is dynamic. i.e. if I copy the SharePoint link to a browser it will open the required document. I note that the same behaviour occurs in the web and desktop clients
This is a big issue for us. Happens whenever we rename a file in the Files tab or when we move a file in to a sub folder in Files tab in order to organize the files rather than have a dump of files in the Files tab. Generally Word, Excel and PowerPoint files will work after being renamed or moved to a sub folder, only occasionally does the link break. However PDF files always fail after a rename or move, but interestingly the PDF can still be open from an iOS device with the Teams app.
Very inconsistent and confusing for users.
Thomas Garrity commented
This happens even if you're just commenting on a file that was renamed. The conversation has a link to a file that no longer exists. You end up having to remove the file, and then re-upload it to get a conversation on a document with a functioning link if it was ever renamed previously.