Ensure you can see the BIM 360 (Preview) item in Windows Explorer
Using BIM 360, create a suitable folder under the Project Files area, and upload your resource file, such as UniformatClassifications_2010.txt
Browse to that folder in Windows Explorer:
Navigate to Manage – Additional Settings – Assembly Code Settings
Copy and Paste the folder address from Windows Explorer (which actually shows the local sync location for BIM 360 data, typically C:\Users\YourUserName\BIM 360\YourBIM360License\YourBIM360Project\Project Files\
Back in Revit, after navigating to the correct BIM 360 folder, select the text file resource and click Open
Revit detects that this resource is stored on BIM 360 Docs and you can proceed…
Sync your model to save the settings
You should be able to use the same process to save other files like Keynote references and Shared Parameter files in the cloud. Keep in mind that you will still have to manage BIM 360 access control, as you probably don’t want multiple people actually be able to edit these files.
If you are still running a relatively small SSD (like 512gb), you might see that your C drive fills up pretty quickly while working on a large BIM 360 Design Revit cloud worksharing project. See below image, where the CollaborationCache folder is using almost 50gb of space on my machine:
While I realise that the SSD is the best place to have that data in terms of performance, if you don’t have the space available you may consider moving your CollaborationCache folder to a secondary, larger hard drive. I used a symbolic link to do this, with the script below:
if exist "%localappdata%AutodeskRevitAutodesk Revit 2018CollaborationCache" rename "%localappdata%AutodeskRevitAutodesk Revit 2018CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%AutodeskRevitAutodesk Revit 2018CollaborationCache" E:C4R
if not exist E:C4R MD E:C4R
robocopy /mir "%localappdata%AutodeskRevitAutodesk Revit 2018CollaborationCache.old" E:C4R
This creates a folder called C4R on your E drive, copies the CollaborationCache over, and sets up the symbolic link. To use it:
Sync all Revit instances and shut down Revit completely
Make a CMD from the code above and run it as Administrator (elevated privileges required for mklink )
In Explorer, confirm you have the symlink and delete the .old folder :
I previously posted about how to quickly repath links based on some control mechanisms. Enter BIM 360, and the wild world of Revit cloud worksharing… I expect that it will be commonplace now for existing projects and datasets to move across to BIM360 ‘mid project’. But that creates some interesting problems, like creating folders, dealing with the initiation process, and replacing local Revit Links with their cloud versions.
This post is focused on that process of changing all of the Revit link paths to link to the BIM 360 models. Unfortunately, the previous method I used (TransmissionData, like eTransmit) is not available for cloud hosted models. So how do we automate this process?
We went about it this way:
Initiate all Revit models on the BIM 360 Document Management cloud (manually, for now)
Create one federated model on the BIM 360 cloud that links in all the other cloud hosted Revit models. You might do this one manually, using Reload From in the Manage Links dialog box.
Once you have that one ‘super host model’, use a batch process to harvest all of the cloud model data
Using the harvested data, create a script that implements a Reload From method to batch reload local models from their cloud counterpart
On the journey to solving step 3, I experimented with a few different methods. I discovered that you need to use the ExternalResource class to get information about BIM 360 cloud models (not ExternalReference).
I also realised that I had to deal with Reference Information, which appears to be a .NET dictionary per link that stores some funky Forge IDs and so on. But I want to store all this data in our VirtualBuiltApp BIM Management system, so I had to serialise the Reference Information to a string that could be stored in a database VARCHAR field (or push to Excel if you are still doing things the old way). Dimitar Venkov gave me a few tips about using JSON with IronPython in Dynamo (thanks mate!), so after that all the harvesting pieces were in place!
Here is some of the harvesting and JSON code. Notice that I played around with using a container class to pass data between Dynamo nodes. In the end, JSON string was the answer:
data = 
for u in unwraps:
container = dummy()
sdicts = 
for y in data:
dictinfo = ExternalResourceReference.GetReferenceInformation(y)
container.dictinfo = dictinfo
The next step was to create the ‘batch reload from’ tool. Now that we had the necessary data, we just had to use it to grab the matching cloud path information (from our database) and apply it to each Revit link.
I created a node that essentially built a new reference path from the JSON and other data that we had harvested. Here is some of that code:
des = 
for x in referencesInfo:
newdicts = 
for y in des:
serverGuids = 
for g in serverIdsIn:
tempguid = Guid(g)
newrefs = 
for z in range(len(referencesInfo)):
serverIdIn = serverGuids[z]
referenceInfo = newdicts[z]
versionInfo = versionsInfo[z]
sessionPathIn = sessionsPathIn[z]
tempRef = ExternalResourceReference(serverIdIn, referenceInfo, versionInfo, sessionPathIn)
OUT = newrefs
The final step was to get a RevitLinkType and a matching ReferenceInformation and apply them to each other. I stored the data in our cloud based BIM Management Application, VirtualBuiltApp. Then I could easily just pull the data into Dynamo with a suitable database connector, and match up the RevitLinkType in the current file with its associated cloud identity. For that genuine 90s feel, you could use Excel to store the data as it is just a JSON string and some other strings:
Here is the key bit of code that actually changes the link path (without all of my other error checking bits and pieces):
newCloudPath = newCloudPaths[l]
reloaded = fileToChange.LoadFrom(newCloudPath, defaultconfig)
successlist.append("Failure, not top level link or workset closed")
To actually implement the script and get productive, I opened 4 instances of Revit, and then used this process in each instance:
Open the Revit file from BIM 360, with Specify… all worksets closed
Unload all links
Open all worksets
Run the Reloader Script
Confirm link status in Manage Links
Optional: Add ‘bim 360 links loaded’ text to Start View (just for tracking purposes)
Optional: Add comment to VirtualBuiltApp (optional, for tracking purposes)
Close and Sync
In this way I can have 4 or more sessions operating concurrently, fixing all the link paths automatically, and I just need to gently monitor the process.
One nice thing is that I set the script up to immediately Unload a link after it had obtained and applied the new Path information. This means that the Revit instance does not get bogged down with many gigs of link data in memory, and in fact this is way faster than trying to use Manage Links for a similar process.
Ideally I would like to fully automate this, to the point where it opens each file, runs the script, and syncs. Unfortunately, time didn’t allow me to get all the code together for that (for now).
Finally, because we are using our custom built schema and validation tools, we can easily create visuals like this:
Modified versions of the Dynamo graphs can be found on the Bakery Github here:
Method 1 – Controlled Sharing – ‘Consume’ Published Models from Packages
Method 2 – Controlled Sharing – Link from the Shared Folder
Method 3 – Live Linking
Each method requires fundamentally different sharing standards, and varying degrees of prior BIM 360 permissions and team setup.
Notice that Method 1 includes the concept of ‘packages’. The overall intention here is to try to emulate some existing workflows. While BIM files continuously change during project development, in traditional workflows a ‘team’ only interacts with a snapshot of the available BIM data from other teams (a package).
At this point, it is key to keep in mind that these different methods exist, and if you are a BIM Manager on a BIM 360 Design with Revit project, you will need to discuss and agree on the linking Method for managing the Revit data throughout the BIM creation phase of the project.
It is something to think about as we move forward with reliance on cloud services – how important is 100% uptime with collaboration cloud products in the BIM world? Is 100% uptime even possible with current technology services, and the stacks (like Autodesk cloud) that rely on other stacks (like AWS cloud)?
I’m looking into ways to batch initialize Revit models onto the new BIM 360 Docs (Document Management) platform. It is a work in progress at the moment – in Revit 2018, I think that there is limited ability to use newer API features for creating a Cloud ModelPath for batch processing. But more on that later…
For now, I wanted to replicate a folder structure from a local network onto the BIM 360 Docs platform. To do this, you just need the Desktop Connector + Preview installed, and then you copy and paste the data.
Here are the steps:
Clear Pending Actions on Desktop Connector for BIM 360 (recommended, use with care)
Work Offline(recommended). Folders will appear blue in Windows Explorer.
Set the folder path in the and create a CMD script using code below. It populates each subdirectory with a text file indicating the contents of the directory.
chcp 65001 >nul
for /r "C:\Your\Folder\Path\Here" %%d in (.) do dir /a:-d "%%~fd" > "%%~dpnd\DirectoryFilePlaceholder.txt"
Run the script on your target directory (the local directory that you want to mirror into BIM 360 Document Management platform)
Run a FreeFileSync task with filters to include only the ‘DirectoryFilePlaceholder.txt‘ as a mechanism of building the file structure. This task copies those txt documents to the BIM 360 using the local Desktop Connector path, as shown here:
Then, disable ‘Work Offline’, so the sync to cloud should begin.
Wait for ‘Processing’ to complete
To force the sync you may have to toggle the ‘Offline’ status in the tray.
You can review sync state with the ‘Pending Actions’ link from the system tray:
After the file structure is copied and synced, you will be able to see it in BIM360 Docs.
You can then proceed with adding Permissions or uploading other files.
Install beta version of a plugin for Desktop connector that allows access to BIM 360 Docs under a separate link
From the help:
This plugin is a connector that establishes BIM 360 Docs as a recognized data source for the Desktop Connector – making it available in your desktop folder and file structure for easy file management.
As with Desktop Connector, this means your BIM 360 Docs files are replicated in a connected drive. You can manage files in BIM 360 Docs through the connected drive, just as you would any other folder on your machine. Changes made on the desktop are automatically uploaded to BIM 360 Docs.
If you are already a C4R user, for a while you can keep working as you are. But the entire platform is shifting from C4R to B3D (BIM 360 Docs), and you will eventually have to make the leap. In the long run, it will allow for more control, like folder-level permissions, so for big projects it is going to make a lot of sense. For now, there is some confusion out there (like in this Twitter thread), so here are some basic steps to activate a new BIM 360 Docs account, setup a Project, and then invite some collaborators into the project.
First, you can go to your account and use the special link to create a new BIM 360 Docs workspace. That is, if you are starting fresh in the new platform.
Here is the activation form notes (read carefully). Note: the links are different depending on how you activate it. For example, if you have an existing C4R account and you want to ‘transition’, you would use the relevant activation link for existing C4R customers :
Once done, you should have a new BIM 360 account:
And you just have to click the activate link in your email:
After that, you should be able to login to your BIM 360 workspace and start setting up some company settings, like adding a Logo and Business Units: