Forum Discussion
New Library UI - non-required "Required" metadata
Bumping this topic, as it remains a major roadblock to businesses like ours adopting SP Online. I did discover a minor improvement - modern library experience does now pop open the details pane when a document is uploaded that requires metadata. However, the user can simply click anywhere and then there is no indication that the document is incomplete. Other issues mentioned previously are still unresolved.
Mark-Kashman danholme, can you or someone from the team confirm issues with required metadata are being worked on to make this viable solution for businesses that rely on metadata?
I did some additional testing with content types. In addition to the issues listed in the original post, such as not prompting for content type selection on upload, I noticed odd behavior of required fields Assume a document is uploaded and the default content type has a field that requires metadata. If the user changes the content type, the information pane continues to display the "Missing required information" for the original content type. If a new content type is selected, the user should not need to fill in metadata for the original content type.
Anyone have ideas on how to promote this topic and get someone at Microsoft to provide some guidance. My organization really needs to know if this type of enterprise functionality is even part of the future SharePoint. Or do we need avoid content types and required metadata in our design/migrations? I see no comments about this elsewhere, or any mention in the roadmap. Maybe 3rd part workflow/forms tools will need to supplement (would need to think this through and experiment). Maybe it is a matter of a new way of thinking as pointed out by Andrew Gilleran, but there are business processes that will need to be rebuilt.
- danholme
Microsoft
Hey all! Sorry we've been busy getting ready for the SharePoint Virtual Summit (join us! https://aka.ms/SharePointSummit) on May 16th.
The good news is that we TOTALLY UNDERSTAND the situation and the challenges you're describing, as well as the challenges many customers faced with the 'classic' model that prevented documents from being visible to team members if required metadata was not completed. There is work being done to address the scenario. We're not ready to announce the details, yet.
I'll add LincolnDeMaris and Chris McNulty to this and will let them reply when they have a chance.
danholme wrote:Hey all! Sorry we've been busy getting ready for the SharePoint Virtual Summit (join us! https://aka.ms/SharePointSummit) on May 16th.
The good news is that we TOTALLY UNDERSTAND the situation and the challenges you're describing, as well as the challenges many customers faced with the 'classic' model that prevented documents from being visible to team members if required metadata was not completed. There is work being done to address the scenario. We're not ready to announce the details, yet.
I'll add LincolnDeMaris and Chris McNulty to this and will let them reply when they have a chance.
Hey danholme, now that the Virtual Summit is over, may we expect some traction on this front? the modern experience is turning out not-so-modern for our users. Lots of frustations and friction in switching from classic to modern. Too many rough edges.
LincolnDeMaris and Chris McNulty any updates on this?
Same here. Built a brand new intranet on SP Online but left it in classic due to the metadata. Interestingly have a read of Tony Redmond's article on a related area and Delve.
https://www.petri.com/efficient-delve-searches-office365
Metadata makes documents findable either by users or the machine!
