At some point in the not too distant future our company will be looking to replace our physical server with a new one and it has been suggested that we have this in the cloud! At the moment we use Teams/OneDrive/SharePoint for a lot of non project related data which is mostly (nearly all) Microsoft types files and this works fine. Project related information goes in project folders on the server.
The questions comes about what to do about .dgn (and .dwg/rvt) files and how we would use them if we moved them to SharePoint. So my question is, if we moved our .dgn files to SharePoint, how would we access & edit them?
There are 2 access methods for files in sharepoint. One is via the web browser and document libraries. This has zero support for reference files.
The second method is via OneDrive and syncing files locally. This can work with reference files via relative pathing or MS_RFDIR variables but it does not solve the problem of 2 people editing the same file simultaneously. Distributed file locking is not fast enough to prevent multiple people editing the same file at the same time. If you're lucking you just get a conflicted copy of the file. If you're unlucky the file will be corrupted.
ProjectWise Drive is Bentley's answer to wanting to have a local sync option but still requires keeping files in ProjectWise. I've only done preliminary testing with it but agree with a lot of the criticisms in this message (I haven't tested Print Organizer with PWDrive so can't comment on that part):
ProjectWise Drive - Best Practices to Enhance Performance? - ProjectWise Design Integration Forum - ProjectWise - Bentley Communities
In case you're wondering why MicroStation works ok with regular windows file shares it's because in that scenario all the users are accessing the same exact file and window file locking properly handles who can modify the one file. With OneDrive you have multiple copies of the file on each computer and OneDrive is trying to negotiate locking and syncing across a potentially slow (or non-existent) internet connection. It just isn't fast enough or even able to make sure all other existing copies of the file are also locked.
I agree with Kevin, don't do it.
Rod WingSenior Systems Analyst