No SharePoint custom fields in Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-44050%22%20slang%3D%22en-US%22%3ENo%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44050%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20SharePoint%20site%20created%20by%20Teams%2C%20I%20added%20a%20custom%20field%20(Choice)%20to%20the%20document%20library.%20This%20field%26nbsp%3Bdoes%20not%20appear%20in%20the%20Teams%20-%26gt%3B%20Documents%20in%20the%20Teams%20site.%20Metadata%20is%20a%20very%20important%20feature%20to%20organize%20and%20search%20documents.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-44050%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-47382%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47382%22%20slang%3D%22en-US%22%3E%3CP%3EJuan%20Carlos%2C%20thanks%20for%20your%20quick%20response!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20response%20to%20%231%2C%20I%20did%20go%20back%20and%20look%20at%20the%20ability%20to%20add%20metadata%20again.%26nbsp%3B%20You%20are%20correct.%26nbsp%3B%20I%20can%20create%20a%20new%20column%26nbsp%3Bduplicating%20one%20I%20already%20have%20on%20the%20top%20site%2C%20and%20attach%20managed%20metadata%20to%20it.%26nbsp%3B%20Not%20sure%20why%20I%20have%20to%20duplicate%20this%20column%20in%20the%20Group%2C%20since%20it%20already%20exists%20on%20the%20top%20level%20site.%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20use%20the%20top%20level%20Metadata%20Term%26nbsp%3BSet%2C%20you%20just%20cannot%20see%20in%20the%20Group%20Site%20Setting%20or%20get%20to%20it%20from%20there.%26nbsp%3B%20However%2C%20once%20you%20create%20the%20new%2C%20duplicate%20column%20you%20can%20attach%20to%20that%20main%20site%26nbsp%3Bterm%20set.%3C%2FP%3E%3CP%3E%232.%20I%20think%20I%20confused%20you.%26nbsp%3B%20%26nbsp%3BIf%20you%20look%20at%20the%20files%20view%20in%20O365%20Group%20the%20only%20columns%20you%20see%20is%20Name%2C%20Activity%2C%20Date%2C%20Person.%26nbsp%3B%20What%20we%20need%20to%20see%20is%20Name%2C%20Title%2C%20Activity%2C%20Date%2C%20Person.%26nbsp%3B%20Our%20(file)%20has%20no%20real%20meaning%20of%20any%20use.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20add%20the%20%22Title%22%20to%20the%20view%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47190%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47190%22%20slang%3D%22en-US%22%3EFor%20%231%3A%20Are%20you%20able%20to%20add%20a%20metadata%20field%20to%20any%20document%20librarie%20in%20the%20group%3F%20While%20it's%20true%20you%20are%20not%20presented%20to%20directly%20add%20a%20metadata%20column%20in%20a%20document%20librarie%2C%20you%20should%20be%20able%20to%20do%20it%20by%20using%20the%20document%20library%20settings%20page%3CBR%20%2F%3EFor%20%232%3A%20The%20problem%20you%20have%20here%20is%20that%20Microsof%20has%20decided%20to%20force%20metadata%20typing%20in%20document%20libraries%20so%20even%20if%20you%20have%20mandatory%20fields%2C%20user%20can%20still%20upload%20files%20without%20filling....so%20the%20question%20here%20is%20about%20how%20to%20automate%20Title%20field%20filling....could%20it%20work%20for%20you%20doing%20it%20after%20the%20user%20has%20uploaded%20the%20files%3F%20If%20not%2C%20you%20should%20have%20a%20look%20at%20other%20techniques%20that%20should%20allow%20here%3A%20SharePoint%20Workflow%20(old%20school)%2C%20Microsoft%20Flow%2C%20Remote%20Event%20Receivers%20or%20even%20Weebhooks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47187%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47187%22%20slang%3D%22en-US%22%3E%3CP%3EI%20understand%20the%20positions%20presented%20and%20agree%20to%20a%20point.%20%26nbsp%3BI%20have%20a%20couple%20of%20issues%20I%20think%20should%20be%20taken%20into%20consideration.%3C%2FP%3E%3CP%3E%231.%20If%20I%20try%20to%20go%20to%20the%20team%20SP%20site%20under%20teams%20I%20can%20add%20various%20fields%20and%20use%20existing%20choice%20fields%20with%20data%20embedded%26nbsp%3Bwithin%20them.%26nbsp%3B%20%26nbsp%3BHowever%2C%20there%20is%20no%20way%20I%20can%20find%20to%20link%20to%20or%20access%20the%20Term%20Set%20metadata%20existing%20within%20the%20top%20level%20site%20in%20which%20the%20group%20team%20site%20is%20saved.%20%26nbsp%3BI%20see%20this%20as%20a%20real%20issue.%20%26nbsp%3BIf%20I%20am%20in%20a%20SP%20Team%20site%2C%20why%20can%20I%20not%20get%20to%20the%20metadata%20and%20use%20it%3F%3C%2FP%3E%3CP%3E%232.%20We%20are%20pushing%20hard%20to%20use%20some%20standard%20file%20naming%20conventions%20to%20prevent%20the%20issues%20associated%20with%20tyring%20to%20input%20meaning%20into%20a%20file%20name%2C%20which%20then%20contains%20all%20kinds%20of%20things%20flying%20in%20the%20face%20of%20file%20naming%20best%20practices.%20%26nbsp%3BOur%20conventions%20have%20no%20real%20meaning.%20%26nbsp%3BThe%20meaning%20is%20contained%20in%20the%20SP%20Library%20Title%20field.%20%26nbsp%3BWhich%20is%20not%20shown%20in%20the%20O365%20Groups%20file%20view.%20%26nbsp%3BIf%20MS%20must%20keep%20it%20as%20is%2C%20can%20you%20at%20least%20add%20the%20Title%20field%20to%20the%20ODB%20%26amp%3B%20O365%20Groups%20file%20view%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45293%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45293%22%20slang%3D%22en-US%22%3EAgree...is%20just%20a%20different%20approach%20to%20collaborate%20and%20good%20thing%20about%20teams%20is%20that%20you%20can%20always%2C%20as%20you%20say%2C%20use%20the%20underlying%20blocks%20(SharePoint%20%26amp%3B%20Exchange)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45284%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45284%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20so%20if%20we%20concede%20that%20Teams%20is%20SharePoint%20Lite%20and%20will%20not%20have%20metadata%20in%20Files%20tab.%20But%20if%20I%20save%20Office%20documents%20with%20Tags%2C%20does%20Search%20in%20teams%20prioritizes%20or%20understands%20Tags.%20Also%2C%20from%20Teams%20itself%20can%20you%20sync%20files%20to%20OneDrive.%20Jumping%20between%20SharePoint%20and%20Teams%20for%20different%20features%20is%20not%20intuitive.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44151%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44151%22%20slang%3D%22en-US%22%3E%3CP%3EAgree%20with%20Paul%2C%20should%20kept%20for%20lightweight%20%26amp%3B%20fast%20collab%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44132%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44132%22%20slang%3D%22en-US%22%3EAnd%20I%20agree%20with%20your%20poing%20of%20view...Teams%20is%20a%20mean%20for%20fast%20collaboration%20using%20the%20best%20features%20of%20the%20underlying%20technologies%20(SharePoint%2C%20Exchange%2C%20Skype%20for%20Business)%20and%20services%20(Groups).%20If%20metadata%20is%20required%2C%20you%20can%20always%20go%20to%20the%20underlying%20site%20and%20add%20it%20to%20the%20files%20stored%20there%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44127%22%20slang%3D%22en-US%22%3ERE%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44127%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20going%20to%20present%20a%20contrarian%20view%20(as%20constructively%20and%20politely%20as%20I%20can).%20I%20feel%20that%20Teams%20should%20remain%20SharePoint%20lite%20and%20for%20the%20most%20part%2C%20not%20seek%20to%20reproduce%20the%20SharePoint%20metadata%20experience%20in%20the%20Files%20tab.%20I%20know%20it%20sounds%20like%20blasphemy%2C%20really%20I%20do.%20But%20I%20feel%20that%20since%20the%20modern%20team%20site%20experience%20is%20now%20based%20on%20groups%2C%20wouldn't%20it%20makes%20sense%20that%20for%20document%20centric%20scenarios%2C%20to%20go%20down%20this%20road%3F%20You%20get%20the%20full%20benefit%20of%20SharePoint%2C%20an%20mobile%20app%2C%20and%20you%20still%20get%20the%20discussion%2Fplanner%20capability.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20for%20me%20serves%20a%20critically%20important%20niche%20where%20the%20conversation%20is%20the%20dominant%20driver%2C%20whereas%20the%20modernized%20team%20site%20experience%20orients%20itself%20around%20documents.%20Besides%20which%2C%20it%20is%20possible%20to%20go%20to%20the%20underlying%20SharePoint%20site%20from%20a%20channel%20or%20team%20space.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20probably%20not%20a%20popular%20view%20I%20know.%20Also%20I%20feel%20that%20OneDrive%20sync%20also%20does%20not%20have%20a%20good%20metadata%20story.%20But%20for%20many%20teams%20use-cases%2C%20I%20have%20a%20feeling%20the%20ability%20to%20sync%20to%20OneDrive%20via%20the%20UI%20is%20probably%20a%20more%20common%20use-case%20as%20teams%20are%20distributed.%20Of%20course%2C%20one%20can%20ssync%20right%20now%20by%20going%20to%20the%20underlying%20SharePoint%20site%2C%20but%20I'd%20like%20to%20see%20a%20sync%20button%20before%20I%20see%20metadata%20exposed...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOf%20course%2C%20I%20am%20sure%20soon%20I%20will%20be%20presented%20with%20a%20use-case%20that%20makes%20me%20change%20my%20mind%2C%20but%20thats%20my%20present%20feeling%20on%20things%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44078%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44078%22%20slang%3D%22en-US%22%3EIn%20understand%20what%20you%20mean%2C%20but%20you%20know%20that%20Microsoft%20has%20also%20to%20acknowledge%20this%20functionality%20is%20essential%20for%20Teams%20to%20start%20developing%20it%20and%20add%20to%20the%20service%20in%20the%20future%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44070%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44070%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20response.%20This%20feature%20ommission%20is%20really%20not%20very%20useful%20considering%20the%20value%20of%20metadata%20in%20document%20libraries.%20Also%2C%20the%20fact%2C%20many%20solutions%20are%20built%20on%20this%20feature.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44052%22%20slang%3D%22en-US%22%3ERe%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44052%22%20slang%3D%22en-US%22%3EMetadata%20is%20currently%20not%20supported%20in%20Teams%20and%20I%20have%20just%20checked%20nothing%20in%20the%20roadmap%20is%20included%20in%20regards%20to%20metadata%20support.%20The%20idea%20is%20already%20posted%20in%20user%20voice%2C%20so%20go%20and%20vote%20for%20it%3A%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public-preview%2Fsuggestions%2F17165729-add-ability-to-add-metadata-to-files%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public-preview%2Fsuggestions%2F17165729-add-ability-to-add-metadata-to-files%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-868036%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20No%20SharePoint%20custom%20fields%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868036%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20an%20old%20thread%2C%20but%20where%20this%20argument%20of%20no%20metadata%20in%20Teams%20(SP%20lite)%20falls%20apart%20is%20records%20management.%26nbsp%3B%20Labels%20need%20to%20be%20applied%20to%20files%20(if%20not%20folder%20level)%20to%20ensure%20schedule%20compliance.%26nbsp%3B%20Without%20this%20capability%2C%20Teams%20violates%20our%20(and%20probably%20everyone%20else's)%20record%20policy.%26nbsp%3B%20It's%20a%20big%20bummer%2C%20since%20Teams%20is%20looking%20like%20a%20perfect%20tool%20for%20us%20otherwise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

In the SharePoint site created by Teams, I added a custom field (Choice) to the document library. This field does not appear in the Teams -> Documents in the Teams site. Metadata is a very important feature to organize and search documents.

12 Replies
Highlighted
Metadata is currently not supported in Teams and I have just checked nothing in the roadmap is included in regards to metadata support. The idea is already posted in user voice, so go and vote for it: https://microsoftteams.uservoice.com/forums/555103-public-preview/suggestions/17165729-add-ability-t...
Highlighted

Thanks for your response. This feature ommission is really not very useful considering the value of metadata in document libraries. Also, the fact, many solutions are built on this feature.

Highlighted
In understand what you mean, but you know that Microsoft has also to acknowledge this functionality is essential for Teams to start developing it and add to the service in the future
Highlighted

I am going to present a contrarian view (as constructively and politely as I can). I feel that Teams should remain SharePoint lite and for the most part, not seek to reproduce the SharePoint metadata experience in the Files tab. I know it sounds like blasphemy, really I do. But I feel that since the modern team site experience is now based on groups, wouldn't it makes sense that for document centric scenarios, to go down this road? You get the full benefit of SharePoint, an mobile app, and you still get the discussion/planner capability.

 

Teams for me serves a critically important niche where the conversation is the dominant driver, whereas the modernized team site experience orients itself around documents. Besides which, it is possible to go to the underlying SharePoint site from a channel or team space.

 

It's probably not a popular view I know. Also I feel that OneDrive sync also does not have a good metadata story. But for many teams use-cases, I have a feeling the ability to sync to OneDrive via the UI is probably a more common use-case as teams are distributed. Of course, one can ssync right now by going to the underlying SharePoint site, but I'd like to see a sync button before I see metadata exposed...

 

Of course, I am sure soon I will be presented with a use-case that makes me change my mind, but thats my present feeling on things :)

Highlighted
And I agree with your poing of view...Teams is a mean for fast collaboration using the best features of the underlying technologies (SharePoint, Exchange, Skype for Business) and services (Groups). If metadata is required, you can always go to the underlying site and add it to the files stored there
Highlighted

Agree with Paul, should kept for lightweight & fast collab

Highlighted

Ok, so if we concede that Teams is SharePoint Lite and will not have metadata in Files tab. But if I save Office documents with Tags, does Search in teams prioritizes or understands Tags. Also, from Teams itself can you sync files to OneDrive. Jumping between SharePoint and Teams for different features is not intuitive.

Highlighted
Agree...is just a different approach to collaborate and good thing about teams is that you can always, as you say, use the underlying blocks (SharePoint & Exchange)
Highlighted

I understand the positions presented and agree to a point.  I have a couple of issues I think should be taken into consideration.

#1. If I try to go to the team SP site under teams I can add various fields and use existing choice fields with data embedded within them.   However, there is no way I can find to link to or access the Term Set metadata existing within the top level site in which the group team site is saved.  I see this as a real issue.  If I am in a SP Team site, why can I not get to the metadata and use it?

#2. We are pushing hard to use some standard file naming conventions to prevent the issues associated with tyring to input meaning into a file name, which then contains all kinds of things flying in the face of file naming best practices.  Our conventions have no real meaning.  The meaning is contained in the SP Library Title field.  Which is not shown in the O365 Groups file view.  If MS must keep it as is, can you at least add the Title field to the ODB & O365 Groups file view?

Highlighted
For #1: Are you able to add a metadata field to any document librarie in the group? While it's true you are not presented to directly add a metadata column in a document librarie, you should be able to do it by using the document library settings page
For #2: The problem you have here is that Microsof has decided to force metadata typing in document libraries so even if you have mandatory fields, user can still upload files without filling....so the question here is about how to automate Title field filling....could it work for you doing it after the user has uploaded the files? If not, you should have a look at other techniques that should allow here: SharePoint Workflow (old school), Microsoft Flow, Remote Event Receivers or even Weebhooks
Highlighted

Juan Carlos, thanks for your quick response!

 

In response to #1, I did go back and look at the ability to add metadata again.  You are correct.  I can create a new column duplicating one I already have on the top site, and attach managed metadata to it.  Not sure why I have to duplicate this column in the Group, since it already exists on the top level site. 

You can use the top level Metadata Term Set, you just cannot see in the Group Site Setting or get to it from there.  However, once you create the new, duplicate column you can attach to that main site term set.

#2. I think I confused you.   If you look at the files view in O365 Group the only columns you see is Name, Activity, Date, Person.  What we need to see is Name, Title, Activity, Date, Person.  Our (file) has no real meaning of any use. 

Is there a way to add the "Title" to the view?

Highlighted

This is an old thread, but where this argument of no metadata in Teams (SP lite) falls apart is records management.  Labels need to be applied to files (if not folder level) to ensure schedule compliance.  Without this capability, Teams violates our (and probably everyone else's) record policy.  It's a big bummer, since Teams is looking like a perfect tool for us otherwise.