[Doug McLean]

In a word, yes.

My team works in SharePoint. We do tend to work on individual projects, however, when we do collaborate we have to do a couple of things differently.

The first thing you’ll need to do is go into your preferences and set up your SharePoint server, Revu> Interface>File Access and then add your SharePoint server to your list. Also on this page is a line that says “Open and save files to DMS from toolbar only” make sure this is unchecked. Now go to the Studio menu, under options select Attempt to Check Out Files on Open. Click OK.
The next thing I would suggest you do is add then Document Management Toolbar to your UI. From this you can open files directly.

The next couple of steps are important. Do not open files from Windows File Explorer, open them with Revu or through the new toolbar. You’ll get a slightly different dialog box that will pop up, open the file from there.

From this point forward, its pretty much like working in a Studio Project. When you open a file, it will be “Checked out” like it is in Studio. You’ll also have to check it back in or update the server copy like you would if you were in a project. If you open the file through File Explorer, Revu actually puts that in a temp folder under your user name, so someone else can actually have it open at the same time.

Overall the process is slightly slower than working through file Explorer, but you will lock out anyone else from having the drawings open.

Hope this helps.

[Vince]

I’ll be coming to you @Doug McLean if I ever need to do something with Sharepoint!!!

[Isaac Harned]

I am curious Doug, on PDF usage on sharepoint in relation to storage. You have some massive PDF’s, does your storage balloon with the versioning?

[Doug McLean]

It did actually.
Our IT department ran a check recently and noticed that we were near max on our storage capacity. We had 900GB used out of the 1000GB just in version history alone…lol.

He set a max copy limit to 50 and a max days limit to 180. Cleared the problem right up.

[Isaac Harned]

Thank you, that helps alot, we are slowly transitioning, and talks have turned to moving our entire server, makes me nervous

[Doug McLean]

the really nice thing is no more VPN.
SharePoint is so much faster than working over a VPN.

Just really mind the steps I mentioned earlier for locking out a file. That’s important.

[Isaac Harned]

Copy, I am also looking into the permission capabilities of sharepoint itself to set the PDF’s to a check in check out system. Technically the permissions would have to be set per folder, but as I understand it, Power Automate can handle the heavy lifting.

[Corbin Steinmuller]

Hey Doug,
I’ve asked the question through our reseller & Bluebeam direct but am getting multiple answers back, maybe you can clarify my understanding of the integration/connection between Bluebeam and SharePoint.

My understanding is we can connect SharePoint and Bluebeam.

Then inside a studio project, select a folder structure from SharePoint.

This will pull through the current folder structure and any files with in.

This is important because it is where we save original download documents and where we add our revisions.

As we begin to add and modify documents in SharePoint the Bluebeam studio folder will also update, and vice versa when we adjust document inside Bluebeam the file will also be reflected in SharePoint.

is this understanding accurate, or does the SharePoint connection not work with the studio feature of Bluebeam?

[Doug McLean]

not sure if Revu will connect to SharePoint through Studio, but why would you?

SharePoint is the cloud, and so is Studio, why would you go cloud to cloud service?

[Corbin Steinmuller]

The idea was to have two folder structures on SharePoint for a project.
one would not be connected to Bluebeam and contain information/files that were confidential we didn’t want to risk slipping through with Bluebeam permission not assigned correctly by employees.
The other folder would be connected to Bluebeam and used for project collaboration and features of Bluebeam.

Why have two different doc management systems. Existing integrations with SharePoint would be difficult to break from, not all employees are using Bluebeam so having a SharePoint file structure they can still navigate if needing project information could be beneficial .

you are correct though there is not a sync capability between SharePoint and studio it is either on or the other.