Make rename in Teams reflect name changes in Sharepoint?
When I rename a folder in the Teams app, the underlying folder is not renamed in sharepoint. This is most confusing.
Anonymous
shared this idea
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
Quick update on this suggestion. We are still working on this with MS Teams. We don’t have an ETA to share still.
225 comments
-
Anonymous
commented
Duplicate of this User Voice item that is more up to date: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16934143-rename-of-team-channel-doesn-t-rename-associated-s
-
Anonymous
commented
Any Workaround on this issue?
-
Shannon Clegg
commented
This has been brought up as a major problem since 2017. Yet no fix as of 2020??? My corporation which is one of the largest employers in the State of Utah is trying to implement and encourage all employees to use TEAMS. This "bug" is beyond frustrating! If it isn't fixed soon, there are many who say we should just return to using the network drive. This will be extremely disappointing since there are so many other great features to using TEAMS. Please advise when this will be fixed.
-
J Bedford
commented
Just adding my voice here. Cmon, MS, get it done.
-
Anonymous
commented
This is not a missing feature but rather a bug and should be fixed asap
-
Todd Edwards
commented
@David that may be the case, but that is extremely short sighted of Microsoft. Plus as voted on here and in the teams uservoice you can see that is not how teams is being used by most customers. They need to fix this!
-
Todd Edwards
commented
How the hell has this not been fixed yet? It has been 3 years!! Over a year from "working on it" to now without any update
-
[Deleted User]
commented
To rename folders and channels is needed, without breaking the links! Thanks!
-
Josh Coles
commented
This absolutely needs to be worked on.
Because we renamed our Sharepoint folder the "Files" tab within Teams within that same channel lead to all the files becoming unlinked. They were still located on Sharepoint of course.
The solution was that we had to create a new channel and move all the files and folders across to the new channel so the "Files" tab would relink.
Such a faff and really shouldn't be necessary. Surely both Teams and Sharepoint to sync changes like this to each other to avoid these issues? -
Bénédicte Cauwe
commented
Any update on this issue?
-
David
commented
With the current pandemic and utilizing MS Teams more, I think I have realized why Microsoft didn't think about renaming channels and the folders created in the SharePoint document library behind them. We're using it wrong.
I believe the intent of channels were to facilitate conversations. The document library behind them was just intended to manage the attachments that people put into conversations. It was never intended to be a replacement for a formal SharePoint site or document library.
Channels also were not intended to be renamed, and especially the corresponding SharePoint library folders behind them. Once a conversation had run its course in a channel, it was intended to be deleted and a new channel (conversations) would be added as needed.
The files in the SharePoint library were just to store the files as long as you needed to keep the conversation around. If the documents were formally needed as part of a process, then they should be stored in a regular SharePoint site, which is why you can display a SharePoint site in a tab.
Teams was thus intended to facilitate conversations and meetings, while SharePoint was intended to manage documents and lists and the two would work together.
Thoughts? Agree/disagree?
-
Anonymous
commented
When I rename a Teams channel, I expect the following cascade to follow suit:
The title string under Files tab must reflect the new channel name
The associated SharePoint folder of the channel reflect the new channel name
All URLs used to link between Teams and the SharePoint space must be updated to reflect the new channel name. -
LMS
commented
This is coming up frequently in sharing content with strategic relationships, especially on private channels.
-
Tonia Sayre
commented
Please provide an update and/or workaround. Last update on this thread looks to be almost 1 year ago. Thank you.
-
Preston Lathrop
commented
I second the more polite of the pleas below to take this bug seriously! We are longtime on-prem SharePoint users. This is not our first rodeo. Show us that it is not yours.
-
Dan Easley
commented
Taylor E. said it best, so I'm just copying-and-pasting him here again.
The corresponding issue on the Teams UserVoice has been updated recently. Please check & upvote here:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16934143-rename-of-team-channel-doesn-t-rename-associated-s#%7Btoggle_previous_statuses%7DAlso, this really needs to be resolved ASAP, both SP and Teams Devs need to bubble this up to the top of the list. It is driving IT/system admins insane, and it's a huge obstacle to getting our organizations to adopt Teams. This needs to get resolved quickly.
-
Taylor E.
commented
The corresponding issue on the Teams UserVoice has been updated recently. Please check & upvote here:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16934143-rename-of-team-channel-doesn-t-rename-associated-s#%7Btoggle_previous_statuses%7DAlso, this really needs to be resolved ASAP, both SP and Teams Devs need to bubble this up to the top of the list. It is driving IT/system admins insane, and it's a huge obstacle to getting our organizations to adopt Teams. This needs to get resolved quickly.
-
Justin
commented
Not only does it provide confusion - It also BREAKS the link into the SP folder/Teams folder making the channel uesless.
Why has there been 0 updates on this????
-
Ian
commented
Nobody wants to use Teams because of this.
-
Anonymous
commented
No offense, but this is becoming ridiculous. When is it going to be done?
Not even an update in almost a year...
So much confusion comes out of this and it's been 3 years that this has been logged as a major issue. Come on Microsoft developers, please!
