Forum Discussion
Onedrive readonly (green locks)
Yes we have a premiere support ticket. Ticket #:13695302 adam deltinger Fennix Mach
A few weeks ago, several document libraries started syncing in Read Only mode. The cause – several columns suddenly became mandatory behind the scenes.
The site content types show the columns as optional, but mandatory columns from the base content type have re-appeared behind the scenes – hidden from view.
These columns are Owner, Record Type and Sensitivity.
Fix
- Go to “Library Settings” > “Advanced Settings”
- In the first option, choose “No” on “Allow management of content type”
- Then the column will display the “Required” tab in the library settings as my following first screenshot
- Click the columns which are required, and change to option “Require that this column contains information” to No
After changing the columns back to optional, the folder in OneDrive should become available immediately
Then we could go back to “Advanced Settings”, then enable content type again
Finally, check that the files are again editable in OneDrive.
this is a bug. We have asked Microsoft to investigate what changed. We have this problem for thousands of libraries and the workaround is unacceptable.
Nicolle Brice THANK YOU SO MUCH, this workaround worked for us. No more lock icons in Files On Demand.
pharphel it is pretty poor. We didn't have a problem with this until a couple of months ago. Something changed... now it's a "Limitation". Confidence in the platform was greatly diminished as many high value document libraries were affected. Even though no mandatory columns existed for the library and site content type, for some reason the original state of the base/parent content type was suddenly being remembered in the background. The product team are working to update the sync client to allow editable synchronization of SharePoint sites with mandatory columns. We had a premiere ticket, but seems they don't care. We have to tell site owners to manually employ this fix to more than 500 affected libraries.
Nicolle Brice you are absolutely correct. I myself have repeatedly spoken with MS Support about FOD issues and they were not even aware of this workaround to resolve it. We only have a handful of sites so this was not a major issue, save for the fact that anything can seem to break it after an update is rolled out. It does make user adoption and site management (we are on classic mode) tenuous. Very frustrating.
