Home

Make an Existing Site Column a Managed Metadata Column?

%3CLINGO-SUB%20id%3D%22lingo-sub-1335239%22%20slang%3D%22en-US%22%3EMake%20an%20Existing%20Site%20Column%20a%20Managed%20Metadata%20Column%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335239%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%20I'm%20a%20new%20Sharepoint%20admin%20and%20I'm%20working%20to%20set%20up%20managed%20metadata%20at%20the%20site%20level.%20I'm%20trying%20to%20create%20a%20Managed%20Metadata%20column%20called%20'City'.%20When%20I%20try%20to%20create%20the%20column%20under%20Site%20Settings%20%26gt%3B%20Site%20Columns%2C%20Sharepoint%20says%20that%20the%20column%20already%20exists%20(which%20is%20true%2C%20it%20appears%20under%20the%20'Core%20Contact%20and%20Calendar%20Columns'%20pre-set%20group.%20I%20seem%20to%20be%20able%20to%20move%20the%20existing%20column%20to%20my%20custom%20group%2C%20but%20I%20cannot%20change%20the%26nbsp%3Btype%20to%20'Managed%20Metadata'.%20The%20option%20doesn't%20appear%20(see%20screenshot).%20I%20also%20don't%20seem%20to%20be%20able%20to%20delete%20it%20to%20re-create%20my%20own%20'City'%20column.%20So%20how%20can%20I%20create%20a%20column%20called%20'City'%20that%20is%20metadata%20managed%3F%20Do%20I%20have%20to%20use%20a%20different%20name%20for%20the%20column%2C%20or%20is%20there%20a%20way%20around%20these%20restrictions%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1335239%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335808%22%20slang%3D%22en-US%22%3ERe%3A%20Make%20an%20Existing%20Site%20Column%20a%20Managed%20Metadata%20Column%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335808%22%20slang%3D%22en-US%22%3EThis%20happens%20when%20you%20try%20to%20use%20a%20column%20name%20that%20is%20already%20part%20of%20the%20%22reserved%22%20labels%20in%20the%20default%20metadata%20for%20SharePoint.%20The%20easiest%20way%20to%20solve%20this%20is%20to%20use%20a%20different%20column%20name%20-%20like%20ABCCity%20(where%20ABC%20is%20the%20name%20of%20the%20org%20and%20after%20you%20create%20it%2C%20you%20can%20add%20the%20space%20to%20make%20the%20column%20more%20readable).%20There%20could%20be%20other%20ways%20to%20do%20this%20programmatically%2C%20but%20if%20you%20want%20a%20way%20to%20do%20it%20that%20is%20quick%20and%20easy%2C%20this%20will%20work.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi All, I'm a new Sharepoint admin and I'm working to set up managed metadata at the site level. I'm trying to create a Managed Metadata column called 'City'. When I try to create the column under Site Settings > Site Columns, Sharepoint says that the column already exists (which is true, it appears under the 'Core Contact and Calendar Columns' pre-set group. I seem to be able to move the existing column to my custom group, but I cannot change the type to 'Managed Metadata'. The option doesn't appear (see screenshot). I also don't seem to be able to delete it to re-create my own 'City' column. So how can I create a column called 'City' that is metadata managed? Do I have to use a different name for the column, or is there a way around these restrictions? Thanks.

1 Reply
Highlighted
This happens when you try to use a column name that is already part of the "reserved" labels in the default metadata for SharePoint. The easiest way to solve this is to use a different column name - like ABCCity (where ABC is the name of the org and after you create it, you can add the space to make the column more readable). There could be other ways to do this programmatically, but if you want a way to do it that is quick and easy, this will work.