Modern UI does not enforce mandatory fields properly
Somewhat related to this (https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/17274506-leave-files-checked-out-when-required-fields-are-n) problem, is that if the Modern UI is turned on for a document library, it wont enforce mandatory fields, unless "enforce checkout" is turned on.
You can edit document properties, check-out/in and publish quite happily without filling out the required fields.
Turning on "enforce check-out" still allows you to edit properties without completing the mandatory ones, but check-in will complain about missing columns.
Thanks you for the feedback; in our new design we do prompt for metadata on upload but we are not blocking save/check-in, opting instead for an attention view model. For more details check out this Ignite 2017 session: https://techcommunity.microsoft.com/t5/Microsoft-Ignite-Content-2017/Geek-out-with-the-product-team-on-SharePoint-lists-and-libraries/m-p/98886#M425
10 commentsComments are closed
this is bullshit!!!! Although ALL the required fields have been filled-in, SharePoint refuses to save the document & complaint that required fields are empty!!! Can't you do ANYTHING right @Microsoft????? Evidently NOT!!!!!!!!!!!!!!!!!!!!
It is totally asinine for Microsoft to pull this feature while evangelizing all to move to Offiec 365 and SharePoint online. Seems they think enterprise uses SharePoint to play and not for real business needs. I guess this may force many to stay with on premise 2010 or another solution. Thanks for nothing Microsoft
Donia Strand commented
We find the attention view model far inferior to having the metadata dialog pop up for users, and it is far more work for them (more clicking).
If metadata can't be required, can MS remove metadata as a feature? It seems to be taking up a lot of peoples time and MS has already decieded for us that it isn't useful.
When uploading a file when checkin/checkout is NOT enabled, the Details Pane opens but there is no requirement for completing the required fields before it is 'saved' to the library. A user can ignore the details pane and required fields and the file is not checked out. Only if the file is checked out to begin with, due to the feature being enabled or when a file is created from within the library (which means it is automatically checked out whether the feature is enabled or not) is there any indication of a problem if editing using the fully functional version of Word, for example. However, when initially creating a file, the details pane does not appear to prompt the user to complete any required fields and the file is saved as a 0.1 version. If versioning isn't exposed to the user, there is no explanation of why the file is checked out.
The document management abilities touted by MS and SP are completely negated if required data is left unfinished due to user oversight or lack of knowledge. Bottom line is that it doesn't get done.
The true irony of it all is that in the Classic UI THIS FUNCTIONALITY WAS IN PLACE! A pop up window appeared showing the required fields and do not allow the user to complete the upload or checkin task without completing the fields. Why in the world would MS not maintain that functionality in the Modern UI is a true mystery to me.
Mike Hatheway commented
Totally agree... I tried to capture the various ways the new UI behaves here:
Mandatory metadata is a must, to avoid inconsistency in search results.
Dan Durand commented
Critical for true ECM as required metadata is essential for lifecycle management. This is a must have as we heavily rely on it today and cannot move to the modern UI without required metadata.
This is an extremely important requirement for us to be able to move from on-premises to SharePoint Online. We heavily leverage Content Types and Metadata to drive our business processes and records management.