Bridge for Build and Docs FAQ
Find frequently asked questions and learn about limitations in the Bridge tool and Bridge in the Sheets and Files tools in Autodesk Build and Autodesk Docs.
For questions regarding Bridge in Design Collaboration, see Bridge for Design Collaboration FAQ.
Bridge Tool FAQ
In the Outgoing or Incoming tabs, when will the Automation column show "Yes"?
The first time that you send or receive content through Bridge, the Automation column will say "No". This is because you performed the initial share and an automation has yet to occur. In the future, this will change to "Yes" when the system sends content automatically.
If I resume an automation, will it sync changes from when it was paused?
No, changes that occurred when the automation was paused do not sync once you resume the automation.
If an item (file, folder, or sheet) with an automation is deleted in the source project, does it get deleted in the target project?
No, deletions in the source project do not have an impact on the target project. The target project will maintain all versions of an item that have been shared through an automation.
Bridge in the Sheets Tool FAQ
Bridge in the Files Tool FAQ
What can I create an automation on?
You can create an automation on folders only. The automation will copy files within the selected folder to the target project receiving the automation. However, any subfolders and files within those subfolders are not copied to the target project.
Do file and folder attributes values get copied to the target project?
The only attribute value that gets copied during the initial share is the Description. If the description is updated in the source project after the initial share, it does not stay in sync.
All other attributes, including custom attributes, are not copied to the target project.
If the name of a folder with an automation is changed in the sending project, will the receiving folder name change too?
No, if the name of a folder with an automation is changed in the sending project, the receiving file or folder name will not change. The recipient has control over how folders appear in their project.
If the name of a file with an automation is changed in the sending project, will the receiving project file name change too?
File names behave differently than folder names. The system uses a file's name to know whether a file should be automatically shared as a new version of an existing file or an entirely new file. Therefore, if a file name does not match an existing file in the receiving project, a new file will be synced over. The original named file still appears in the receiving project.
The following diagram walks through an example of what a receiving project will see depending on which project members change a file name.
What happens if the receiving project has naming conventions set up for Files?
If the holding area is not enabled and the target folder you want to share to has a naming convention, that folder cannot be chosen.
What happens if you archive a folder with an automation in the Files tool?
If a folder with an automation is archived in the Files tool, we delete the automation.
If a folder is restored and it previously had an automation, the automation will not be recreated.
Why can I not open the IWM file I received through Bridge in Infraworks?
IWM (Infraworks) files can be transferred through Bridge but can only be viewed in Docs or Build in the destination project. The files in the destination project will not open in Infraworks.
How are links (for example XREFs) in host files maintained when bridging the host file?
This varies based on the production software that you are using. For example, in Revit, the system does not currently send any references or links if the host file is sent. You can choose to send the host file along with any references. Then the receiving member can relink or re-reference them. Any updates will then be transferred and updated in the destination so long as the member is using Revit 2023.1.2 or 2024 or higher. This Revit version limitation is specific to Revit Cloud Workshared (RCW) models.
I uploaded a file to a folder that is automatically syncing from another project. Why does it look like its coming from another project?
A file you upload to a folder that is automatically syncing from another project will have an indicator that it is coming from another project even though it is not. You uploaded it to your project and it is not syncing to or from the other project.
