Forum Discussion
SharePoint Doc Library issues with newest OneDrive NGSC
In my experience that behavior has always been due to human errors, usually on shared files maintained in ODFB (hence contrarily to best practices...) and synced on multiple clients.
Have you carefully verified who is reported in the recycle bin to delete the file(s)?
Probably he/she is indeed the culprit. :-)
Just my 2 cents...
Salvatore,
Can you tell me why you wrote this "(hence contrarily to best practices...)". Is Microsoft discouraging use of a feature they built in? SharePoint sync is very useful especially now with the selective folder option.
Christine
Hi Christine.
I was speaking about ODFB.
ODFB is meant to store personal business documents: therefore such files are expected to be shared sparingly and temporarily by the owner.
All the documents heavily accessed by multiple users should instead be stored in classic team sites or in Groups.
Hence to keep indefinitely heavily shared documents in ODFB is contrary to best practice.
Give a look to this (a little) old but still perfectly valid article: https://en.share-gate.com/blog/onedrive-for-business-vs-sharepoint-team-site-infographic
I tend disagree with your point of view here. Your POV was right before they introduced sync for SharePoint sites. They are also positioning OneDrive as the workhorse for mobile working with SharePoint. Therefore sync will be subjected to heavy workloads.
Hi Simon, glad to hear from you.
I think there are two different subjects here:
- Correct usage of ODFB. ODFB is meant to store personal business documents, hence normally accessed only by a single person, i.e. the owner. Of course sharing temporarily ODFB documents is perfectly OK, but keeping permanently workgroup documents in ODFB is not a good practice. I think we can easily agree on this.
- Correct usage of sync. Here things tend to be a little more complicated, because IMHO there is a strong mismatch between technical and marketing reasons. I worked as a researcher for an academic institution, and at that time my area of interest was concurrency control. Hence I know exactly how difficult is to maintain coherency of a resource which is concurrently accessed by multiple users. Now, with sync we have not only concurrent accesses to data but even local copies potentially misaligned: a nightmare from a technical standpoint! (I must admit that I am surprised that it works... ;-) ) Microsoft is doing everything that is technically possible to give to people a feature that the marketing loudly requires, but IMHO such feature simply can't work reliably all the times. In conclusion, I think that syncing locally simultaneously accessed resources is a dangerous proposition from a data integrity point of view (as all complaints in this community demonstrate everyday...) and it should be done only when it is really indispensable (coauthoring etc.) and not, for example, only because people likes more the File Explorer UI instead of the ODFB Web UI. Just my opinion, of course...
- Totally agree with Salvatore's comments here!
