Enable sync client to allow editable synching of team sites with mandatory metadata columns
As at 23rd Jan 2017 the newly relased One Drive for Business synch client enables synching of Team sites BUT if any libraries have mandatory meta data or require check out, the synched folder/library is read only. This cripples collaboration by teams on documents. This needs to be fixed
With build 20.114, users can now sync libraries with required metadata as read/write instead of read-only.
Joe Goodgame commented
Any news on this, this negates the benefits of one drive syncing with controlled document folders. Considering this used to work i have no idea why anyone thought it was a good idea to remove
Jasiek Gryboś commented
I think this bug kills the collaboration.
Leonardo Marinelli commented
Any news or workaround?
Any update on this? Still thinking?
Michael Haslé commented
We are really having more and more issues due to that limitation.
The Check-out is a clear added value and avoids many conflicts, but if we cannot get these libraries synced locally, that is just another good excuse for them go for alternatives.
So please just review the "Thinking about it" and jump on the keyboard to get that fixed...
Steven Spray commented
I've actually come across another problem with the NDSC; I can't use the Desktop version of Office anymore with SharePoint.
When I check the file out, and try to open the document using desktop Excel, I get the same series of errors as if I was syncing to the library using Windows Explorer. So, I have an Office license that permits desktop applications but I can't use it, wow!
Marco Mangiante commented
So, if I can't edit items with check-out/check-in property enabled, the sync client is useless. Sorry Douglas Pearce, but your "Thinking about it" and no more news is a suicide in communication.
I got updated to new client (somehow) and nothing works any more. Syncing is essentially useless. Had to stop syncing all my folders because I need to use libraries that require check-in/-out. Closing unmodified file (i.e. word doc) no longer prompts for Check-in causing a lot of locked files as people do not notice they are leaving their files checked out. On top of all this the files I tried to open, while sync was enabled, got messed up and no longer prompt for checkout at all (the only fix was to rename these files, after disabling sync, to get them to start at last prompting for checkout). MS you have literally halted the company wide rollout of sharepoint.
Ed Harrison commented
Fully agree with the comments below. Libraries that require check-in/-out are a great feature of Sharepoint, but if we can't use these and have them sync then this is a real retrograde step. Can we please have an update on this?
Steven Spray commented
Why does this problem exist? More importantly, why is this STILL a problem? C'mon guys, this is basic stuff. This is supposed to be your "New and Improved Sync Client". I had the old client working absolutely fine until I 'downgraded' to this new one yesterday. Sort it out asap guys, this is not a 'suggestion', it's an absolute basic requirement!
Josh Waclawski commented
Approaching six months later and he's still thinking about it. Is Microsoft paying this team to sit and think about adding basic functionality? This is absolutely insulting.
Can we get some kind of response? Is this officially a bug yet? Has anyone looked into it?
What in the **** is going on?
Darren Andrews commented
Really MS!! this is meant to be a business tool. You can't really think this is acceptable?
This is unbelievable. How somebody can have a though of removing support for one of the key features of SharePoint in OneDrive ??? Think fast, we want to get it back.
Daire Ryan commented
I cannot believe this is happening. We are going to have to move away from Microsoft Onedrive as they don't appear to have any respect for their customers and their needs.
Vicki Little commented
Have you thought about it long enough yet Douglas? This is a real inconvenience. The mandatory metadata is a bonus that should not stop the ability to use another system bonus.
Greg Jones commented
This comes down to primarily one thing....a good user experience, not an IT or Technical thing. Forcing changes that don't make sense in OneDrive is just dumb....I can tell you that in a hybrid environment for the past 1+ years and having all these changes in OneDrive Sync client and having to use the old client for certain things and the new client for others, lack of support in new client for key features that should just exist and our actual business users expect is a terrible experience. To have to explain, yet another shortcoming with this Sync client is just pitiful, in my humble opinion. Please make this better, not for IT and Technical people but more for the business users who we are trying to get to adopt these tools!
The more information support page (https://support.office.com/en-gb/article/Learn-more-about-the-Sync-button-update-on-SharePoint-sites-9762aef3-d17f-4486-aae3-9c20bb979cbf?ui=en-US&rs=en-GB&ad=GB) on the latest changes states:
"The following types of libraries will transition from the old sync client as read-only:
-Libraries that contain multiple required columns, extra metadata, or custom columns. See Create a column in a SharePoint list or library.
-Libraries that require check-out of files."
However, apparently these are not the only circumstances.
Our sharepoint site/document library has:
1. No mandatory columns.
2. No metadata (?)
3. No required check out
However, in Library Settings under Document Version History we have "Create major and minor (draft) versions Example: 1.0, 1.1, 1.2, 2.0" checked.
And, under Draft Item Security we have "Who should see draft items in this document library? : Only users who can edit items" checked.
This scenario also causes files to sync as read only. Checking "Any user who can read items" makes it sync properly, but this defeats the purpose of draft items.
I was so excited to move to the new Sync Client because the old one periodically needed reinstalled/reconnected to fix sync errors. But with this new client, we actually lose the functionality that makes it worth using at all...
Here we are months later, and the latest news is "not only are we not fixing it, we are making it so that you can no longer use the old client which you were using as a workaround also".
Checking in and out documents and having extra metadata are some of the best features in SharePoint. I'm glad that you are giving us an option to opt-out of the change that permanently removes the old client that allowed this functionality, but it sounds like doing that also means that we are opting out of updates for the NGSC, which works GREAT for OneDrive.
Why do we have to lose one functionality in order to have another? Why can't we have a great OneDrive sync experience AND retain some of SharePoint's best features?
Peter good catch this is a massive backwards step from Microsoft and one that might make us move away.
Peter White commented
As the old OneDrive for Business is being phased out the OneDrive for Business software stops working and throws an error that you need to move to the latest sync client. After being forced to upgrade we have found out that the new sync client doesn't handle syncing libraries with:
'Checkout, Required columns or metadata, or when Draft Item Security is set to either Only users who can edit or Only users who can approve items in Version Settings of the library'
Any libraries meeting these conditions will be synced as Read Only so that users can't edit any files. This completely defeats the purpose of SharePoint where the power comes from metadata, checkout and permissions and has made the Onedrive client unusable for any business users. I can only assume this is a massive oversight by the MS team..?
This behaviour needs to be addressed. The correct behaviour would be for the sync to allow editing of files if the metadata has already been filled in and the file has been checked in while if the file is checked out or has not had the metadata populated to remain read only.
To confuse things further the sync behaviour does work correctly if a library has a site content type added with required fields etc, however once the library level columns are changed to mandatory and the content type inheritance is broken it all fails.