Forum Discussion
Read Only (Padlock Icon) files - OFDB 17.3.6743.1212
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.
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-started-syncing-SharePoint-sites-with-the-new-OneDrive-sync-client-Preview-6de9ede8-5b6e-4503-80b2-6190f3354a88
That was the problem, thank you!
This is the same problem we have. What is the solution? How can we set it not to get the padlock?
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.
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...
I just got off the phone with Microsoft support. They gave a link that describes the issues discussed here in the hyperlink below. Sure enough, it's by design.
- Hi I have the same issue did you resolve it?
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.
Thanks, Geoff
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.
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.
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.
I have the same issue... Is there a solution?
In my case this was the solution:
In SharePoint library settings 'Advanced settings'
Set 'Allow Management of Contenttypes' to 'no'.
Now the Required fields were visible in the library settings and I could uncheck them field by field.
Same behaviour here. Why don't they just admit that ODFB does not work in conjunction with SharePoint? It never has in my experience. Why are they rolling this out when they know about such a bug?
Synchronization appears to work if you place your required columns within a Content Type and apply said Content Type to the library. If you add a column to a library and make it required, it locks files again in the local synced folder (Windows 10, new ODFB client)
Olivier Jegaden wrote:Synchronization appears to work if you place your required columns within a Content Type and apply said Content Type to the library. If you add a column to a library and make it required, it locks files again in the local synced folder (Windows 10, new ODFB client)
This is not true in my case - I use content types exclusively, some of the columns in the content type were mandatory, so them being in a content type did NOT allow the data to be editable
- I have the same problem. This is terrible and frustrating!
Just discovered this thread because I'm having the same issue. Didn't know this was a bug. Hopefully it will be fixed soon.
I am having the same issue.
This is the first library I've tried applying multiple custom columns to. Not sure if that is the problem.
It turns out that the "Required Metadata" in a column was the problem. I made the column not required and it is now syncing without the padlock (write access is allowed).
Why should we have to give one benefit for another. I need the metadat required columns, I have any user who can read items checked and none of this has worked. However, yesterday when I booted up my system for the first time I went right to my files locally and they were all available and I had changed nothing. I thought Microsoft had corrected the issue but later in the day they were back so what was that abot?
I was doing it on a siteassets library, I didn't add any custom columns. I think just the fact that versioning is on does it.
