Forum Discussion
Sharepoint synchronization issues
Hello all, for a project we chose Sharepoint 365 as data storage and created a link from the Documents library to OneDrive, so all data stored in Documents is synchronized with the users device (...
It's not clear why you are linking the Documents library through OneDrive instead of simply syncing necessary SharePoint folders directly. Working via OneDrive can subtract from the working filepath length available, and is fragile to the extent that a SharePoint folder name change can break your OneDrive.
Secondly, it reads as if you're trying to sync a very large number of files: 11000 folders suggest you're working to the very limits of SharePoint sync in optimal device, network and sharing configuration. This indicates that your group is trying to work with SharePoint as if it were a network drive* which it is not. I've written in a recent post about the problems caused about from "lift and shift" without altering your data architecture.
If your file architecture requires frequent shared changes or reads of thousands of files, then SharePoint is not the solution. You should be working with a database that can handle the transactions or stay on a network drive. (Scientific data sets are a good example of this.)
*Mapping a network drive to Sharepoint/OneDrive is a dangerous short-term solution due to the file-locking and namespace issues.
Secondly, it reads as if you're trying to sync a very large number of files: 11000 folders suggest you're working to the very limits of SharePoint sync in optimal device, network and sharing configuration. This indicates that your group is trying to work with SharePoint as if it were a network drive* which it is not. I've written in a recent post about the problems caused about from "lift and shift" without altering your data architecture.
If your file architecture requires frequent shared changes or reads of thousands of files, then SharePoint is not the solution. You should be working with a database that can handle the transactions or stay on a network drive. (Scientific data sets are a good example of this.)
*Mapping a network drive to Sharepoint/OneDrive is a dangerous short-term solution due to the file-locking and namespace issues.