06-15-2019 06:11 AM - edited 06-15-2019 06:16 AM
06-15-2019 06:11 AM - edited 06-15-2019 06:16 AM
This thread was triggered by reading a training slide deck produced by my main client who uses Microsoft 365, Office 365 Groups and therefore SharePoint document libraries extensively. Like they've already got over 600 Office 365 groups for each project - and groups have only been around a couple of years? I came across this comment in another thread:
>My suggestion is to treat SharePoint more like online network drives and teach your users to use the sites and the cloud and not resort to old methods and syncing all those files across all devices so they look like drives.
A worthy suggestion and the official Microsoft line whenever you mention a problem with WebDAV. But my client is never going to accept this without a BIG fight and I suspect they are not alone. I reluctantly had to write them a reasonably complex PowerShell script that allows them to type in a simple project code (AM3231) and the script then maps a network drive. They then work 99% of the time in this network drive even though they have to open Internet Explorer every day (sometimes more often) in order to "Open in File Explorer" in order to re-establish authentication (aside this has never been in Edge 'cos of it's architecture - is it coming to Chromium Edge?).
In fact, if WebDAV network locations ever went away, this client would dump SharePoint without batting an eyelid and switch to Dropbox or something similar. More on why not OneDrive later.
These are the main blockers/why they love WebDAV network locations:
Let's tackle the last two first. Slower? Maybe but strides have been made in improving the speed of the document library browser and maybe Chromium Edge will be even better. Side note: same client has instructed me to shift everyone across to Chrome because it's visibly better. I fought this decision as long as I could, defending Edge alone but eventually had to concede they were right. That stubborn "Edge really is better" has caused more harm IMO in the long run than help.
But slower blockers can be overcome so let's park that one. It's not File Explorer - well of course. resistance to change is a common problem and can be overcome but it would be nice if the web browser experience offered something that network locations and File Explorer didn't. Access to version history isn't enough of a draw - most of the users haven't a clue it's even there.
Again, it's not File Explorer is a minor gripe in the scheme of things and can be overcome.
No, it's the first two that are just HUGE walls to adoption. I've just created a new document from within Word (and come on, let's just accept that desktop Office is going to be the preferred way to work forever) and I hit "Save" - here are my options:
Sure, if it's a project I've worked on a lot or recently, it's there but I mentioned this client has over 600 Office 365 groups. That user interface is not fit for purpose so you surprised they prefer to hit Browse and use network locations:
Considering Microsoft are in control of both Office, Edge and SharePoint, the lack of easy navigation and integration here is beyond belief. You can't even access favourites from Edge etc.
And final blocker - the assumption that Office is the only desktop application that people use and therefore the lack of the ability to open 3rd party documents directly from the browser:
Pray tell where are the "Open in Nitro Pro" for PDF documents or "Open in Photoshop" options?
Tech aside: I don't know whether the lack of these options is a limitation in SPO or lack of adoption by 3rd party developers. However, considering that if Nitro or Foxit did implement direct open from SharePoint, they would get my clients business in 30 seconds, I suspect it's the former.
Until you can open 3rd party documents in the associated application directly from the web browser, users are going to stick with network locations. Downloading and uploading it is not an option BTW. Ever heard of version control?
Now above I mentioned that if WebDAV network locations ever went away, they'd switch to Dropbox et all, I said why not OneDrive? And why don't they synchronise those folders locally with OneDrive?
1) They (and me) don't trust OneDrive. Its fundamental design around tracking changes across multiple devices just seems flawed compared to Dropbox and Google Drive. I've had many cases of users logging onto their home computer with OneDrive synchronised and had it restore long deleted folders and documents. I get this all the time with my own IT account where I often logon to a laptop many months later to have it assume it's the master. But the biggest problem for OneDrive sync of document libraries is that we've had two instances of users accidentally deleting the local copy before unsynchronising. BANG - entire document library gone. Sure, you can get it back from the recycle bin but the user has to own up immediately.
Side note: because of the limitations of the recycle bin, I convinced my client that a 3rd party backup of SharePoint, Exchange and OneDrive is essential. They're using Veaam provided by ILand. It's not a perfect solution but at least I know we can restore accidentally deleted document libraries.
2) Synchronisation is not a replacement for file-locking. I'll just leave that one there...
I hope that Microsoft appreciates me taking an hour out of a Saturday to write this diatribe. All triggered by one line on a slide saying "Don't use links to SharePoint, use links to File Explorer"...
06-15-2019 08:20 AM