Mar 14 2017 02:50 AM
Mar 14 2017 02:50 AM
When trying to create a channel I get "Another Channel already has that name. Try a different one" but a channel of that name doesn't exist (See below)
What may have caused this is - I created a channel a few days ago but I spelt it wrong. I then renamed the channel to the correct spelling but it didn't change the link to the folder in the document library, so I deleted the channel. Now when I try create the new channel with the correct spelling it won't let me.
Mar 17 2017 12:58 PM
I'm having the same issue. I have deleted a channel and am trying to add it back with the same name.
I don't get prompted when typing the channel name, but after clicking "Add" I get a "Another channel already has that name. Try a different one."
This is a huge oversight, any workaround?
Mar 17 2017 01:12 PM
From my understanding this is working as intended for now because of the way the security and compliance features work. Once a Team or Channel is created, that name is forever taken right now for tracking and audit purposes. Different Teams can have the same Channel name, but no two Teams can have the same name and no two Channels can have the same name within a team, even after deletion.
Mar 17 2017 01:21 PM
Mar 17 2017 01:32 PM
I can understand "for now," but this is a serious oversight in regards to corporate environments where naming conventions are so important.
a bug, not a feature.
Mar 17 2017 02:04 PM
Strict policy on the Team name (which is also the Office 365 Group name) I understand. But Channel? Every team is going to be somewhat unique. Even if you start them with a template, they are going to diverge onto their own path relatively quickly. If you keep things so locked down that they can't make their Teams experience at least somewhat their own, I would be concerned you'll begin to see low adoption and retention.
I'm sitting on a little over 30k users and we're probably a little more free than I'd like, but we'll be instituting some sort of automated inactivity governance solution that offers easy ways to harvest and archive data and then either locks the team into read-only or straight up deletes it, potentially depending on its data classification level via something like Azure Information Protection. Everyone always says they need all those ancient SharePoint sites we all still have laying around and have been migrating from version to version over the years, but if you go look at the usage stats the only people that go in there is the search crawl/index.
Hint hint Microsoft, don't make me custom develop this solution please! :)
Mar 25 2017 08:03 AM
Please fix this.
So.... if someone randomly creates a 'Microsoft' channel by misstake then deleted it..... this means that nobody can use the term 'Microsoft' ever again ??? This is absurd.
Jul 11 2017 07:54 AM - edited Jul 11 2017 07:55 AM
I ran into this today. Is this going to be fixed? There is no way I'm rolling out Teams to any user without this being fixed.
Jul 11 2017 08:58 AM
Does the folder in the Document library still exist? Are there any assets left related to that channel?
I've had a similar issue where I initially created a Channel using its acronym and renamed it to its full title. Just tried creating another Channel using the acronym again and Teams successfully added one.
Jul 25 2017 07:54 AM
Just to clarify with team naming it seems something may have been updated because I am able to create 2 teams with the same name, and I confirmed that someone else can create a team with the same name.
Jul 25 2017 01:58 PM
Uhhhhh... that is not a good idea, at all :) Hold please, this one merits a chat...
Jul 25 2017 04:45 PM
Reproduced this myself, and logged the concern with Microsoft.
The Teams seem to be different on the backend, but having 2+ Teams with the exact same display name is going to be wildly confusing to users IMO. Imagine 2+ Public Teams with the same exact name. Which do you choose to join? If you choose both, how do you remember which is which?
Apr 30 2018 02:14 AM
This issue seems to be on-going. Does anyone know whether there are plans to issue a fix? I notice it is documented as a known bug with no work-around. It is going to have significant implications for user adoption which is why I don't think we can proceed with Teams until it's sorted.
Apr 30 2018 08:40 AM
Which specific problem, there's quite a lot discussed here in an old thread, much of it no longer relevant.
If you trying to recreate a channel that was previously deleted, you can now see the old channel under Manage Team ... Channels and restore it. You still can't use the same name, as that would break the restoration option.
May 04 2018 07:43 AM - edited May 04 2018 08:26 AM
Thanks for the reply Steven. I will provide some further details...
We have just begun testing Teams and created some channels. A decision was taken to rename a channel. All seemed to be working at this point until we clicked on the Files tab and realised the underlying SharePoint directory holds onto the original name.
Anyway, fair enough, perhaps there is a good reason for this (struggling to think of one at this point), so we renamed the SharePoint directory to match the new Channel name. This appeared to work until we clicked on the Files tab again - it regenerates the original SharePoint Directory! Back to square one.
Ok, so next step. We deleted the channel, removed all trace of it from SharePoint, emptied the Recycle bin. We then attempted to re-create the channel with the same name only to be warned another channel already has that name...
Am I missing something here? Do I have to warn users when they are creating channels they are set in stone and can never be changed if they want to preserve naming integrity between Teams and SharePoint? Does anyone know why there isn't a unique ID assigned to each Channel to avoid this issue?
May 04 2018 08:57 AM
Well, there are various limitations, we've not had this cause us an issue at my org but it would seem you've pretty much found all of them :)
Firstly it's a known issue that you can't reuse a previous name, it's listed in the known issues at https://docs.microsoft.com/en-us/microsoftteams/known-issues. You can however restore a deleted channel from the Manage Teams ... Channels page of the team.
I don't think you should mess with the folders in SharePoint either, you can see it doesn't like it.