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
We’ve heard your votes and comments and we’re happy to say we are actively working on supporting this scenario within the OneDrive Sync client. Stay tuned for roll out details!
Just learned today that all my nice libraries on the nice SharePoint project platform with mandatory metadata columns won't sync with write permissions to OneDrive. Holy Sh...!!!
This is really ****. Why can Box.com do it and SharePoint not? I'm promoting SharePoint over Box in our Business but with such a drawback this will hardly be sucessful!
@Microsoft: When will this be implemented?
I just cannot see how they can implement this feature without having to update Windows 10 OS at the same time..(likely why they have been thinking on it for 3 years)
Making a 1:1 metadata link between SharePoint Online Document libraries and Windows Explorer.. likely too hard.
Although if they figure this out, it would be huge. Just imagine, being able to filter by metadata in Windows Explorer!
Hopefully some Product Manager gains inspiration from this comment!
Ansuman Mohapatra commented
Big business players are involved in raising this issue. Request for an early fix.
Been an issue for ages now - please provide a fix.
Bet Apple would have fixed it by now...
Ahmed Elhamidi commented
we need the part check out and check in be integrated with OneDrive sync folder as this push the user to use the browser. we need to use FULLY local folders to access and edit SharePoint Online, so please enable this for BOTH Windows and Mac
Hello Microsoft, this is an important use case for operation teams, let us know will it come or not, clear statement please
Please fix this issue as it prevents user adoption of both using SharePoint required fields and syncing.
This is just a minority user group. Microsoft won't care it that much. They have bigger client for more $$$ to work on it.
Any progress on this issue?
Actually, even if there is no mandatory or required column for library, the checkin/checkout feature can not be used with syncing. I think this must be solved immediately.
After some testing one issue i found was with the web browser, Edge, unable to check in and out or view documents in the window pane.
The new Microsoft Edge Chromium looks to address some of the SharePoint issues, although we are still having issues with excel and word documents not being able to be saved, with one drive installed
Want this functionality ASAP!
Make it happen guys!!!!! Need it so much
How soon can this be resolved? As we trying to move to a metadata centric approach, which will ultimately help with the search functions in SharePoint. But also allow our team to sync with SharePoint through OneDrive for business and enable them to access via file explorer the relevant files including when there is no web access.
Giorgio Capisani commented
We need this feature, please fix it!
Will P commented
This really needs fixing, it's not obvious that adding a required description on SharePoint Online would cause you to be unable to create files or folders locally when synchronised.
This needs to be addressed sooner than later. File Explorer is not going away and users prefer to work with large numbers of documents this way. Being unable to sync libraries with mandatory tags is ridiculous and prevents my users from using Tags instead of Nested Folders (to prevent the 255 char limit errors)
2020 here! Is there a fix? This is a HUGE issue.
This renders Document Sets unusable in modern document libraries as you cannot sync the document library or document set and drag and drop files into it - you get the "destination folder access denied" error.
This makes Document Sets a production rolled out feature with a critical bug. Suggestion is to not release Document Sets as it is not 'production ready' or fix the critical bug so it can be used.
Please prioritize this for 2020, it is affecting our SharePoint Online adoption.
Nick Winchester commented
2 years on and this still isn't solved? Really?
Why would you cripple the 2 biggest features of SharePoint document libraries to not work together?