Share

Bridge for Build and Docs FAQ

Find answers to frequently asked questions about the Bridge tool in Autodesk Build and Autodesk Docs, including its use in the Sheets and Files tools.

For questions about Bridge in Design Collaboration, see Bridge for Design Collaboration FAQ.

Bridge Tool FAQ

If I resume an automation, does it sync changes from when it was paused?

No, Bridge does not sync changes that happened while the automation was paused.

If I delete a shared item, will it also be deleted in the target project?

No, deleting an item in the source project does not affect the target project. The target project keeps all versions of a file it has received through Bridge.

Bridge in the Sheets Tool FAQ

Bridge in the Files Tool FAQ

What can I create an automation on?

Automations can only be created on folders and any subfolders if included when setting up the automation.

Do file and folder attribute values copy to the target project?

Bridge copies custom attribute values and the Description attribute value during the initial share and when an automation occurs.

Custom attributes must meet the required criteria to be copied into a target project. Learn more.. If you update a custom attribute value later, it does sync.

If you update the Description later, it doesn't sync.

Bridge does not copy other attributes to the target project.

If I change the name of a folder with an automation, does the receiving folder name change?

No, changing a folder name in the sending project does not change the folder name in the receiving project. The recipient controls folder names in their project.

If I change the name of a file with an automation, does the receiving project file name change?

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. If a file name doesn't match an existing file in the receiving project, a new file will be synced over along with the custom attributes values. The original named file still appears in the receiving project with the original attributes values.

The following diagram shows what the receiving project sees when project members change a file name.

A folder with an automation is sent from Project A to Project B through Bridge. File "Hello world" is inside the folder.
A folder with an automation is sen...
A member in Project A changes the name of the file to “New world” in Project A.
A member in Project A changes the name of the f...
A member in Project A uploads a new version of the file "New world" to Project A.
A member in Project A uploads a new version of...
A member in Project B will see the original file and the new renamed file:

"Hello world" - Version 1
 "New world" - Version 1
A member in Project B will see the original file an...
A member in Project B changes the name of the file to "Brave new world" in Project B.
A member in Project B changes the name of the f...
A member in Project A uploads a new version of the file "Hello world" to Project A.
A member in Project A uploads a new version of...
A member in Project B will see the renamed file and the new version of the original file:  

"Brave new world" - Version 1
"Hello world" - Version 1 
A member in Project B will see the renamed file and...
Text is not SVG - cannot display

What happens if the receiving project has naming conventions for Files?

If the holding area is not enabled and the target folder uses a naming convention, you can’t choose that folder.

What happens if you archive a folder with an automation in the Files tool?

If you archive a folder with an automation, Bridge deletes the automation.

If you restore the folder, Bridge does not recreate the automation.

Why can’t I open the IWM file I received through Bridge in Infraworks?

You can transfer IWM (Infraworks) files through Bridge. You can view them in Docs or Build in the destination project. You can’t open them in Infraworks.

Do shared files or folders link to the source project?

No, the link goes to the new version of the file in the receiving project. The exception is Revit Cloud Workshared (RCW) models. Learn more about Revit Cloud Worksharing.

I uploaded a file to a folder that syncs from another project. Why does it look like it’s from another project?

If you upload a file to a folder that syncs from another project, Bridge shows an indicator that it’s from another project. You uploaded it to your project. It does not sync to or from the other project.

File in folder with automation indicator

Was this information helpful?