01-10-2017 04:37 AM
01-10-2017 04:37 AM
I am currently using the ODFB preview client 17.3.6743.1212 to sync a single group and a single SharePoint online document library. The Office 365 group library is working as expected but all the documents stored in the SharePoint library have a green padlock. When I open any of the documents, I am informed that this is an offline copy and the document is read only.
Has anybody else experienced the same behaviour? I assume if I deleted and re-synced it might solve the problem, but that’s not a viable solution after the sync tool has been deployed to many users.
01-10-2017 11:17 AM - edited 01-10-2017 11:18 AM
The reason could be the following:
"When syncing libraries that require check out, or libraries with required columns or metadata, the files are synced as read-only. If you do make changes to these files, the changes will not be synced back to Office 365." from https://support.office.com/en-us/article/Get-start
01-11-2017 01:36 AM
Thank you Salvatore, my files do fall into this category, do you know if Microsoft have any plans to fix the 'know issues'? We have many document libraries where we have required metadata, so this will impact our users if its not fixed before the client hits GA.
01-11-2017 03:26 AM
I have not heard of a specific committment by MS to solve this problem. But shortly (before the end of the month) the new OneDrive client should reach GA and we will see...
01-25-2017 07:36 AM
Yes, using the new gen client I am having the same problem when syncing a SharePoint folder. I have raised the incident with Microsoft Engineers (who had a remote session on my system) and they have escalated it to the Beta group who will release an updated client version - I hope soon!! If you right click on the blue OneDrive icon you can also report the problem.
01-25-2017 07:55 AM
If you are syncing libraries that require check out, or libraries with required columns or metadata, this at the moment is the expected behaviour, as already said. Otherwise it is a bug.
01-25-2017 08:30 AM
Hi, no I'm not doing doing either of these, and the MS Engineer checked if these had been activated somehow, but is not the case. It also is not related to SharePoint or local security permissions. I had been running the new client successfully, until updating to the Preview client (1212) a few days back. I think it's a bug.
01-27-2017 07:29 AM
This was a known issue in the preview client and was listed, although not right at the top as it should have been! The preview clinet has now been released as a full release, and this has STILL not been fixed. I agree this is a significant issue that potentially hurts collaboration. Everyone who is having this issue and is concerned should vote for this to be fixed on UserVoice
01-29-2017 08:33 PM
01-31-2017 01:08 AM
I think this issue must somehow be related to a bug in Onedrive. I have document libraries which were syncing fine and I was able to edit synched files with the previous ODFB (groove.exe). After installing the new ODFB Preview (onedrive.exe) I noticed the better part of my libraries were synced as Read Only.
If I remove versioning altogether for the document libraries it works... but I need versioning so that is not an option.
However, having fiddled around with the settings for my document libraries for a while I noticed that I can use Versioning and make them sync as editable content. What I did first of all was disabling "Require content approval for submitted items?" and "Require documents to be checked out before they can be edited?".
The only setting I've enabled in Versioning Settings is "Create major and minor (draft) versions". By setting the Draft Item Security to "Anyone user who can read items" the library syncs fine and I'm able to edit content synched to my local PC via ODFB.
BUT, every time I change the Draft Item Security setting to anything except "Anyone user who can read items" (e.g. "Only users who can edit items") all content is synched as Read Only again!
Has anyone else experienced this?
I'm not using any Meta Data settings or mandatory columns. The document libraries I've tested this approach on are basic, straight out of the box Sharepoint document libraries on Sharepoint Online. I'm using Office 2016 too btw.
02-02-2017 02:46 AM
I also have this issue on a a basic document library with no check-out required, or mandatory metadata columns. The library only uses major versioning.