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)?
Federated Central file -> Everything else (no nested links)
Next challenge: how can we quickly promote those nested links into our federated model? Well, we currently have the module files populated, so how can we leverage those positions to promote the nested links?
Promoting Nested Links
It is a bit hacky, but here is how I went about it. For each module file:
Create an empty proxy file (New Revit project, no template)
Open the Module file and resolve all link paths (so they are loaded)
Set links to Attachment
Copy / paste the link Instances from the module file (Level 0 or Base Level) into the empty file (Level 1, default level). You can use Dynamo graph above.
Save the new proxy file as ‘ModuleContainer’ or similar. We know have a file that only has link instances in it.
Open a detached copy of the Federated Central file (you can save as temporary copy if you like)
Select the current Module file,
replace with the ModuleContainer you created. Once you have done all the modules, you are ready for binding as described below.
After populating the detached Federated Central file, we just need to Bind and then Copy / Paste the free instances:
After load, Bind the ModuleContainer files to the detached Federated Central model
To do this, right-click on the file in Revit Links in Project Browser
Select All Instances – In Entire Project
In the Ribbon, click Bind Link
Untick Attached Details, Levels, Grids
Click Remove Link when prompted
Your nested links are now promoted!
Optional: Ungroup all of those bound free instances (select all from Project Browser, Ungroup in Ribbon)
Open the real Federated Central file
Copy / paste the populated free instances from the detached Federated Model to the real Federated Model. Use the Dynamo script to collect them.
Tip: Paste into a closed workset for better performance.
Close the detached one, and sync the real one
The only thing we technically ‘broke’ or lost in this process is the module link->nested link relationship. So if someone decides to move one of the nested links in the module link, obviously that won’t replicate into the Federated Central file.
Hope this helps some of you out there building or dealing with large federated models.
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.
Collaboration for Revit 2018.3.1 Update, Dynamo Core 22.214.171.1240 and Dynamo Revit 126.96.36.1990
With this install the following will be updated: Revit 2018, Collaboration for Revit 2018, and Dynamo. The updated version of the Dynamo Revit add-in does not include a desktop shortcut and can be accessed from the Visual Programming panel found on the Manage ribbon tab. If multiple versions of the Dynamo Revit add-in are installed, a dialog will prompt you to select which version to launch.
After this update is applied, there will be two versions of Dynamo Core installed, 188.8.131.523 and 184.108.40.2060.
Known Issues with applying the update.
During the installation of the hotfix you may be prompted to exit revit.exe. If you do not have a visible session open of Revit, please open Windows Task Manger, switch to the Processes tab, click “revit.exe” and the option “End Process”.
After this update is applied, attempts to uninstall Revit 2018 using the Autodesk Uninstall Tool may become unresponsive during the Dynamo Revit uninstall process. To avoid this problem, uninstall Dynamo Revit first and then continue with the uninstall of Revit 2018.
After a new version of Revit comes out, we all take some time to catch up. Revit API developers often have to get up and running really quickly so they can upgrade their apps for Revit 2019 compatibility. The first few things you will need are: the Revit 2019 SDK and help file, RevitLookup installed, and an understanding of What’s New in the Revit 2019 API.
To install RevitLookup for Revit 2019, head over to this page and grab the latest version, currently 2019.0.0.1. Put RevitLookup.addin and RevitLookup.dll into one of your Revit Addins folders, like:
To install the Revit SDK, follow these steps:
Install Revit 2019 (or access the install media)
Look in the installation folder
In the Utilities subfolder, you will find the Revit 2019 SDK installer – RevitSDK.exe
This will basically unzip a whole heap of Revit API samples and goodness into a folder of your choosing. The key thing I look for initially is the RevitAPI.chm help file. I put this somewhere I can get to it easily (like OneDrive).
Until http://www.revitapidocs.com/ is updated for Revit 2019, the help files is the best way to access information about the Revit 2019 API.
Useful links, mostly from Jeremy over at The Builder Coder: