To be able to use the new BIM360 Design or BIM 360 Document Management in Revit you need to be able to see ‘Document Management’ after clicking the BIM 360 link in the Revit Open Dialog box:

  1. Revit 2018.3 (or newer) is required and a direct download link can be found here.
  2. Download and install Desktop Connector for Windows.
  3. Download and install the Desktop Connector for BIM 360 plugin.
  4. Restart your machine if not prompted to do so.

I have added these steps to my public OneNote notebook on using BIM 36o with Revit:

Installation  (Web view)

 

Check out this page from Autodesk Knowledge base. Notice how it describes three different ways of linking for BIM 360 Design projects that involve Revit worksharing:

  • 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.

 

Interesting to see that many BIM360 services are offline right now (approx 10am Australian time, 1 June 2018):

You can always check Autodesk online service health at this link:

Autodesk Health Dashboard

 

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)?

When using MySQL with Power BI Desktop, you may come across this error:

Value 'preferred' is not of the correct type

 

It seems that this is caused by an incompatibility between Power BI Desktop and a later MySQL Connector Net version. First, check your version:

If you are running the MySQL Connector Net 8.0.11, you may experience the error described above. To resolve the issue, install the older version:

  1. Close Power BI Desktop
  2. Uninstall MySQL Connector Net 8.0.11
  3. Install MySQL Connector Net 6.10.7 (from here)
  4. Open Power BI Desktop
  5. The error “Value ‘preferred’ is not of the correct type” should be resolved, and you can use MySQL with Power BI again

At Virtual Built, we typically create a federated Revit model for every project we work on. This allows us to run a host of automated processes on the links, right from the federated file.

Recently we received a dataset for a high rise building. The Architect had used 5 typical linked ‘module’ files, copied throughout a master file.

Initially, I used a Dynamo script to collect all the link instances into a saved selection set. I could then copy / paste aligned the link instances into our federated Revit model:

Link Instances to Selection Set

 

The Problem

This works fine, but in this models there were also nested consultant links inside the Architectural linked modules. So we have:

Architectural container file -> Architectural module files -> Consultant nested links

 

We want:

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:

  1. Create an empty proxy file (New Revit project, no template)
  2. Open the Module file and resolve all link paths (so they are loaded)
  3. Set links to Attachment
  4. 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.
  5. Save the new proxy file as ‘ModuleContainer’ or similar. We know have a file that only has link instances in it.
  6. Open a detached copy of the Federated Central file (you can save as temporary copy if you like)
  7. Manage Links
    • Select the current Module file,
    • Reload From,
    • 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:

  1. After load, Bind the ModuleContainer files to the detached Federated Central model
    1. To do this, right-click on the file in Revit Links in Project Browser

    2. Select All Instances – In Entire Project
    3. In the Ribbon, click Bind Link
    4. Untick Attached Details, Levels, Grids
    5. Click Remove Link when prompted
    6. Your nested links are now promoted!
  2. Optional: Ungroup all of those bound free instances (select all from Project Browser, Ungroup in Ribbon)
  3. Open the real Federated Central file
  4. 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.
  5. 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:

  1. Clear Pending Actions on Desktop Connector for BIM 360 (recommended, use with care)
  2. Work Offline (recommended). Folders will appear blue in Windows Explorer.

  3. 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.
    @echo off
    chcp 65001 >nul
    for /r "C:\Your\Folder\Path\Here" %%d in (.) do dir /a:-d "%%~fd" > "%%~dpnd\DirectoryFilePlaceholder.txt"
  4. Run the script on your target directory (the local directory that you want to mirror into BIM 360 Document Management platform)
  5. 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:
  6. Then, disable ‘Work Offline’, so the sync to cloud should begin.
  7. 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.

New versions of Firefox removed some support for extensions that allowed multiple tab rows. Here is how you can enable it:

  1. Type about:support in url field of firefox, hit enter.
  2. On the ‘Profile Folder’ setting (about 8th from the top) click the ‘Open Folder’ button.
  3. Create a ‘chrome’ subfolder, if you don’t already have one.
  4. Inside that folder create a file called ‘userChrome.css’ (right click > new > text document – make sure to name the file userChrome.css and not userChrome.css.txt or something)
  5. Open the file for editing and paste the contents of this file;
    https://gist.githubusercontent.com/forexhill/b0446cc31e5001c9e87754df83f0f1ca/raw/f4f1a807d43434a1f10908364dec56ecdf08422c/gistfile1.txt 411
    Into it.
  6. Restart FF and you should have multi row tabs

This comes from user fh1 at this link

This hotfix corrects an issue with non-English languages where the PnID Modeler functionality did not load correctly after appling Revit 2018.3 Update.

Some notes from readme below…

Additional software applied by this update

Collaboration for Revit 2018.3.1 Update, Dynamo Core 1.3.2.2480 and Dynamo Revit 1.3.2.2480

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, 1.2.2.373 and 1.3.2.2480.

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”.
  • For BIM 360 Design (formerly Collaboration for Revit), if the Modified date for the revit.exe.config file is newer than the Created date, the patch installer will fail to update it and Revit may not launch correctly. Consult Collaboration for Revit: Synchronize process starts failing for C4R.

Autodesk Uninstall Tool

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:

%appdata%\Roaming\Autodesk\Revit\Addins\2019\

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:

My Revit API 2019 Notes:

  • Building site export removed from API and Revit 2019
  • Project browser organisation for schedules added
  • Can now read the Phase Map parameter for the link. The phase map is a correspondence between phases in the host document and phases in the linked document…