When a recent update to Autodesk Desktop Connector forced a migration to Autodesk Docs, file paths were generally change like this:
FROM – C:\Users\USERNAME\BIM 360\YOURFOLDERS
TO – C:\Users\USERNAME\ACCDocs\YOURFOLDERS
If you were doing some interesting tricks with BIM 360 Docs, and sharing and federating Revit models as non-initiated files on BIM 360, you may find that links were broken and “Not Found” in Manage Links after that latest Desktop Connector installation.
But don’t worry! You can just set a symbolic link to point from the old BIM 360 Docs location, to the new location. The Command Prompt script looks like this:
The moment after this script was run, I was able to hit Reload from Manage Links in Revit and the new location was detected and links were loaded successfully. Note that they still appear in Revit as if they are in the old location, but really it is reading the latest data from Autodesk Docs, and that new location is being updated by Autodesk Desktop Connector.
What happens if you enable BIM360 Design Collaboration on a project, but would then like to switch it off? I asked Autodesk this question, and here is part of the response (in italics):
Unfortunately we cannot disable active services on specific projects. Once a service is active, it remains active.
If the project is underway and there is information that cannot be moved (such as issues/ RFI’s, etc), then my recommendation would be to make sure no one has access to the Design Collaboration module on the project.
If you would like to see a feature implemented that allows the ability to deactivate a service, you can share your thoughts and request it via the Ideas Board using this link: https://forums.autodesk.com/t5/bim-360-ideas/idb-p/2032
In light of the above, if you do want to make sure no one has access to Design Collaboration, switch it off per-person in the Project Members page as shown below:
If you have Desktop Connector installed, you probably realise you can ‘upload’ Revit models and other files to BIM 360 Docs by dragging and dropping to the folder in Windows Explorer (using Desktop Connector). However, when you try and link this using the BIM 360 shortcut in Revit, you might not be able to see the file…
Here is a workaround that may allow you to link a non-initiated Revit model into your Revit file:
Ensure you have Autodesk Desktop Connector installed
Start Link Revit command from the ribbon
Update: Click on the Address drop down
Click on This PC
Browse to BIM 360 from the window below:
Select the file (non initiated) that you want to link
You should get the BIM 360 prefix in Manage Links:
Here is a video of this process (with audio, This PC – BIM 360 workflow):
I have developed a working BIM360 to on-premises backup mechanism. There were a few different ways to go…
I initially considered:
Hacking Windows Explorer to touch the files in the BIM 360 node and try and trigger the BIM360 Docs download and copy to local PC or network location
Developing a Forge app that essentially pulls the desired models out of the BIM 360 cloud to desired location?
In the end, I decided to use the Revit API (Dynamo and Python), along with VirtualBuiltApp, to essentially reverse engineer a folder structure from the local CollaborationCache folder. These ideas are hinted at here.
In simple terms, the BIM 360 Docs on-premises backup workflow is:
Create a super federated BIM 360 model (with all other BIM 360 models linked into it)
A Dynamo script reloads all links in order to cache them locally
The same script interrogates, then determines the target file name and folder from VirtualBuiltApp
Dynamo then copies the files into their ‘backup’ location on the local network
Some more detail is presented below:
A) Cache Cleaner CMD Script (may not really be necessary, as the ‘reload’ should overwrite superseded cache anyway):
Kill Revit if Open… be careful of below steps, particularly if Revit has crashed recently. You might need these local copies 🙂
cd "%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit 2018"
for /d %i in (*) do move "%~i" oldCache
B) Manual steps to setup Revit model environment to run the script:
Open Federated BIM 360 file (worksets closed)
Unload all links
Open all Worksets
C) Dynamo Script:
Run Dynamo (Python) script that reloads and unloads all links (this collects .rvt into cache). Key Python commands to use are: RevitLinkType.Load() and RevitLinkType.Unload(None).
Coordination Monitor alert, no longer exists
Instance of link needs Coordination Review
“Some numerical data within the imported file was out of range. This numerical data has been truncated.”
“Geometry in the file … has extents greater than 20 miles (33km).”
Just to be clear, while the steps below *work* at this time, it apparently is an unsupported and inappropriate workaround and there could be risks (financial or otherwise) for BIM 360 Docs customers who invite free users into their projects. You should only invite:
BIM 360 Docs users for which you have paid for and applied an entitlement
BIM 360 Design (C4R) users who have purchased their own entitlement
I expect this workaround may eventually be disabled by Autodesk? You can view if you have exceeded your purchased package of BIM 360 Docs entitlements in the relevant Autodesk Manage pages. For example, it might show 16 of 10 licenses used in red? This is where I think there is potential for Autodesk to back charge users who abuse this current state of affairs.
My advice: check directly with Autodesk about who you can and cannot share your BIM 360 projects with…and proceed accordingly.
You are a paying BIM 360 Docs user and would like to invite a non-paying user to collaborate inside a BIM 360 Docs workspace. Perhaps you just want them to be able to upload and download files, but not Collaborate in Revit…
They need to create a free BIM 360 Docs account, and then get invited to your workspace.
Previously, this was all working with the old Desktop Connector and b360provider.exe (I think?) but the new versions of Desktop Connector seem to have broken the ability to ‘browse’ C4R Revit models on BIM 360… and guess what? There is no Solution. This functionality is in fact ‘by design’. You can copy and paste a non-C4R Revit model to BIM 360 Docs via the connector, and that RVT will be visible in Windows Explorer. But if you have C4R initialised Revit models on BIM 360 Docs, they will not be visible under the BIM 360 (Preview) node in Windows Explorer. You can only view those C4R Revit files in their folder structure by navigating through Revit 2018.3 or newer.
This is the feedback from Autodesk:
Revit cloud models (C4R models) are not supported in Desktop connector. They won’t be showing up in Desktop Connector. Published C4R models are only available in Revit and Docs.
I went looking for another answer, but there really isn’t one. Below is a list of steps I took to play around with the Desktop Connector installation. In the end, the only way I can foresee being able to ‘automate’ onsite BIM 360 Docs backups will be to leverage the CollaborationCache folder. You will need some Revit API know-how to forcibly populate this through some BIM 360 Reload methods (refer here). Unfortunately this will be a flat list of files without descriptive names, so there will have to be some workarounds and cleanup scripts in place (we already have a system of BIM 360 file management in VirtualBuiltApp). I intend to post some more about these workarounds in future.
Keep reading for excessive detail on my Desktop Connector journey …
Uninstalled this old version. Interestingly, there were 3 different uninstall processors triggered? Like I had three different versions installed?
Also tried removing this folder and reinstalling:
I found a pile of errors in the diagnostic logs:
CDX pipleline builder output
Output=Warnings received from AddInStore.Rebuild
Could not connect up a part in a pipeline to its neighbors: AddInAdapter Name: "ISecureSettingsProviderViewToContractAddInAdapter" Location: "AddInSideAdapters\Comet.AddInFramework.DataSourceProviders.ProviderAdapters.dll".
and a few of these
Could not connect 2 valid add-in model parts.
While inspecting an assembly, caught a BadImageFormatException: The file is not a valid binary: C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServices.dll This occurred while inspecting assembly C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServices.dll.
While inspecting an assembly, caught a BadImageFormatException: The file is not a valid binary: C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServicesUI.dll This occurred while inspecting assembly C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServicesUI.dll.
I scanned through the Registry and deleted old references to Desktop Connector.
Found this link with the command line switches: here
Tried an install from elevated command prompt:
C:\Temp>DesktopConnector-x64.exe /install /quiet
Note: you do not actually need the Desktop Connector to collaborate on BIM 360 Revit projects in the cloud. You only need Revit 2018.3 or newer, and the relevant license for Revit Cloud Collaboration (too hard to keep track of the names but I think ‘BIM 360 Design’ is the current terminology).
You will be able to see this link in Revit 2018.3 or newer:
When ‘linking’ Revit models, CAD files, and other resources, you will see this option when working in a cloud workshared model:
These models will be temporarily stored in the CollaborationCache folder: