SOLVED
Home

Folders: Name change in SPO breaks connection with Files tab in Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-94491%22%20slang%3D%22en-US%22%3EFolders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94491%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3EWhen%26nbsp%3Bchanging%20the%20name%20in%20Groups%2FSPO%20file%20library%20associated%20with%20a%20given%20Teams%20Channel%2C%20I've%20tested%20a%20break%20in%20association%20between%20the%20folders%2C%20giving%20me%20a%20404%20error.%20Moreover%2C%20when%20changing%20the%20Teams%20Channel%20name%2C%20the%20name%20of%20the%20associated%20folder%20in%20Groups%2FSPO%20doesn't%20change%20accordingly.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETested%20on%202%20tenants%20and%20with%20the%20same%20result%20every%20time.%20I%20expect%20this%20to%20be%20a%20bug.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20way%20the%20Channel%20and%20Folder%20could%20be%20attributed%20a%20unique%20ID%20NOT%20dependent%20on%20the%20name%20of%20it%20so%20as%20to%20avoid%20this%20error%3F%20I%20expect%20challenging%20user%20adoption%20due%20to%20inconsistency%20and%20having%20to%20deal%20with%20renaming%20and%20reorganizing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experiencing%20this%3F%20Any%20indications%20of%20a%20fix%3F%20Can't%20see%20anything%20on%20the%20roadmap.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-94491%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332822%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332822%22%20slang%3D%22en-US%22%3EThe%20link%20looks%20right%2C%20but%20it's%20broken.%20You%20need%20to%20remove%20the%20prefix%3A%20%22http%3A%2F%2Fjuan%2520is%2520correct%252C%2520it%2527s%2520already%2520know%2520issuse%2520and%2520also%2520microsoft%2520already%2520started%2520the%2520work%2520for%2520this%2520issue%252C%2520you%2520can%2520refer%2520the%2520below%2520link%2520%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95205%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95205%22%20slang%3D%22en-US%22%3EGood%20to%20know%20the%20team%20is%20already%20working%20on%20a%20solution%20to%20fix%20this%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95163%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95163%22%20slang%3D%22en-US%22%3EExcellent!%20Thanks%20for%20referring%20me%20to%20the%20blog%20post%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95162%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95162%22%20slang%3D%22en-US%22%3EOk.%20Good%20to%20know.%20Thanks%20for%20answering.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94534%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94534%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EJuan%20is%20correct%2C%20it's%20already%20know%20issuse%20and%20also%20microsoft%20already%20started%20the%20work%20for%20this%20issue%2C%20you%20can%20refer%20the%20below%20link.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F16934143-rename-of-team-channel-doesn-t-rename-associated-s%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F16934143-rename-of-team-channel-doesn-t-rename-associated-s%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94523%22%20slang%3D%22en-US%22%3ERe%3A%20Folders%3A%20Name%20change%20in%20SPO%20breaks%20connection%20with%20Files%20tab%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94523%22%20slang%3D%22en-US%22%3EI%20would%20say%20this%20is%20a%20lack%20of%20functionality%20and%20it's%20a%20well%20known%20issue%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Hi all,

When changing the name in Groups/SPO file library associated with a given Teams Channel, I've tested a break in association between the folders, giving me a 404 error. Moreover, when changing the Teams Channel name, the name of the associated folder in Groups/SPO doesn't change accordingly. 

 

Tested on 2 tenants and with the same result every time. I expect this to be a bug.

 

Is there any way the Channel and Folder could be attributed a unique ID NOT dependent on the name of it so as to avoid this error? I expect challenging user adoption due to inconsistency and having to deal with renaming and reorganizing.

 

Anyone else experiencing this? Any indications of a fix? Can't see anything on the roadmap.

 

Thanks

6 Replies
I would say this is a lack of functionality and it's a well known issue
Solution

Hi,

Juan is correct, it's already know issuse and also microsoft already started the work for this issue, you can refer the below link.

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16934143-rename-of-team-channe...

 

Ok. Good to know. Thanks for answering.
Excellent! Thanks for referring me to the blog post :)
Good to know the team is already working on a solution to fix this :)
The link looks right, but it's broken. You need to remove the prefix: "http://juan%20is%20correct%2C%20it%27s%20already%20know%20issuse%20and%20also%20microsoft%20already%20started%20the%20work%20for%20this%20issue%2C%20you%20can%20refer%20the%20below%20link%20"
Related Conversations