Forum Discussion
PhoenixMS
Apr 07, 2021Iron Contributor
SharePoint team says the Teams Channel rename bug is fixed, but it doesn't appear to be
The SharePoint Roadmap Pitstop: March 2021 post (posted 3/31) included the following: I've tested this in two different tenants (one standard, one early release) and the issue has not been ...
Peter_Bors
Mar 29, 2022Copper Contributor
PhoenixMS I am trying to resolve a problem similar to what I'm reading here in this message.
A few months back we changed the name of a teams channel from “Youth Groups” to “National Youth Missions”. When we did that it did not change the file folder host name from “Youth Groups” to “National Youth Missions”. One of our teammates was trying to correct that and decided to change the name of the folder manually on his Mac through the Finder synced files. I believe this essentially made the change at the SharePoint location which started a mess. As I'm sure you know, the name change created the new “National Youth Missions” folder and moved all the files but it disassociated the files from “National Youth Missions” teams channel.
Now, our “Youth Groups” folder that is hosted in the “National Youth Missions” Team channel is empty. The original files are still in the new folder that was created called “National Youth Missions” but are not associated with the channel. We'd like to try and keep the teams channel “National Youth Missions” and change the host folder in that channel to the “National Youth Missions” folder that now holds all the files. However, we are not sure that is possible or can be fixed.
According to the Microsoft 365 Roadmap site, "For legacy Teams channels that were renamed prior to this rollout, there will be no change in experience. When a legacy channel is renamed after this release, it will simultaneously rename the corresponding SharePoint folder." I suspect this we are in the no change to experience group since this problem occurred several months ago. I think I understand and have read things through on this topic but I may have missed something or there is an answer out there I have overlooked. What recourse do we have to correct this problem? Thanks!