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.
252 comments
-
Ingvill Greve
commented
Can you please share a status on this issue, this is affecting a lot of users.
-
BY
commented
Please fix....
-
Michael Pares
commented
PLEASE GET THIS FIXED I WILL LOVE NOT HAVING TO EXPLAIN THIS ISSUE TO MY USERS ANY MORE. THEY LOOK AT ME LIKE I AM CRAZY. LOOKING FORWARD TO YOU SAVING THE DAY FOR ME!!!
-
DP
commented
Thumbs up. Jsut writing to hopefully receive a notification when this is fixed.
-
Fabian Medina
commented
This is a must! Many issues in our company due to this issue. Thanks.
-
Lisa
commented
Can we have an update please on when this issue will be fixed. It is seriously affecting user comfort (read ADOPTION). Thanks.
-
Jale
commented
Microsoft validation policy
Please verify that the Team app can pass Microsoft Policy, refer to https://docs.microsoft.com/en-us/office/dev/store/validation-policies
E.g.
4.2 Your updated app or add-in must not decrease the app or add-in's functionality in a way that would be unexpected to a reasonable customer.
4.3 Your app or add-in description, imagery, documentation and any other associated metadata must be consistent with the functionality of the app or add-in.
4.11 Your app or add-in UI should not look unfinished.
If app cannot pass then:
9.1 If your app or add-in is found to violate any of our store policies, it can be removed from AppSource. -
Aleksandra Hoes
commented
We've renamed a few channels some time ago, but failed toe see that the underlaying names didn't change. Some time later we wanted to renew the adaptation in our team of MS Teams/Sharepoint. We wanted to do #2 workaround but found that this doesn't work for renamed channels in the past. So if you then delete the old renamed channel you end up deleting all the files you just thought you moved to the new channel. After some mild panic (and almost a heart attack... ) It ended up us turning everything back to the old names from the deleted folders. I never want to fo trough that again or to explain it to some people who are very negative about adapting Teams. So please work on it a lot faster! :(
-
Chris Conley
commented
@Robin Capper - You can kind of do #2 today. You can select either "SharePoint Library" or "SharePoint" if you add a tab to a channel. The former lets you link to any SharePoint link, which could go directly to a folder; the latter lets you point to a page.
Definitely not perfect, and doesn't address link rot, but it can work for some use cases.
-
Robin Capper
commented
Crazy this has not been resolved. Given the lack of solution on the Sharepoint side could the Teams team at least allow a user to
1) Pick a sync location for the Files Tab
2) Or remove it and allow a new tab for that link -
Simon Wiltshire
commented
This is a pretty big miss in the essential collaboration between Teams and SharePoint (and let's not forget OneDrive either for desktop sync). Your customers shouldn't have to be the ones to get you guys to work together. On the equivalent issue in the Teams User Voice they say you're working on it. And here you're working on it with them. But it's unclear if you really acknowledge and are fixing the issue, or what "working on it" actually means. Can you post perhaps a more elaborate response? Like, do you agree this is a problem, it's a problem with "SharePoint/Teams", and we're fixing it, with a view to releasing it in 20XX? It's been an acknowledged issue since March of 2017 so that's forever in tech land.
-
Chris Conley
commented
The problem with copying vs. moving files is that you lose audit history, version history, etc. It's a decent workaround if you can live with that, though.
-
Bia
commented
Can we please get an update on this? Thanks.
-
Brian Martinez
commented
WORKAROUND : TLDR : *transfer the files to a new team channel with the correctly named file folder > delete old channel*
Create a new channel with the correct name you want the corresponding folder in sharepoint to be > copy the existing files to that correctly named channel (because moving them does some other magic that I thought I figured out but don't want try to explain here) > delete old channel and voila !
However, if you still need to reference the conversation, then you can't delete the old channel...maybe rename to "DEAD CHANNEL/DO NOT F*CK WITH THIS CHANNEL ANYMORE OR EDIT ANY OF THE FILES WITHIN" or something to that extent...but, you would still have to worry about this incorrectly named folder (and it's contents) found within sharepoint housing your original files...I could definitely see one of my dumb co-workers going in and messing allll of that up...so I think deleting the channel AND the subsequent incorrectly named folder(s) would be the best option, for now...?!@#!$@%
Farewell to old convos, new ones are more interesting anyway.
Also, look up the convo between Bob Lazar & Joe Rogan on you t00b.
May the force live long and be prosperous with you all.
-
Jorge Zenezini
commented
this limitation is greatly hindering users adopting "Microsoft Teams"
-
Rosemary
commented
this undocumented feature really triggers my OCD tendencies.
-
max_sec
commented
pls fix!!! pls!!!
-
Anonymous
commented
Quick update: No update. Thanks
-
Pete Gleason
commented
Any day now MS. It is so hard to achieve user adoption when something as basic as changing a channel name completely screws up a project.
-
Jason Tan
commented
Wow... 2 years and still no ETA. Just discovered this issue, the solution doesn't even have to be automatic. All you need to do is to allow the user to select the appropriate sharepoint folder in Edit Channel, and then update all the connections to this folder. I'd be happy with that. What is holding back the team from implementing it?
