Menu

Autodesk A360 Collaboration For Revit: Renaming Models, Links, and Maintenance Workflows

As discussed in a recent blog post (Deleting and Restoring Models in A360 Collaboration for Revit), there are two layers to the server side of A360 Collaboration for Revit (C4R). One layer is the A360 layer (which interacts with Revit), the second is the Team layer (where models Published by A360 are stored and viewed).

In addition to affecting deletions, this dual-layer structure also affects renaming files, and workflows for maintaining and repairing models.

The biggest impact is that the only way to rename a model is within Revit, via the Manage A360 Models function on the Collaborate Tab. Click on the Actions for the Model:

Screenshot 2016-04-08 13.49.37

 

Select Rename

Screenshot 2016-04-08 13.49.43

 

Enter the new name in the Rename dialog box.

Screenshot 2016-04-08 13.49.53

 

You will see a notice telling you the name will not update in Revit until you do a STC.

Screenshot 2016-04-08 13.50.04

 

Note that the file name in Revit has not yet changed:

Screenshot 2016-04-08 13.52.27

 

Next, do a normal STC. You should see the new name in the dialog box.

Screenshot 2016-04-08 13.52.36

 

This will also change the file name in Revit.

Screenshot 2016-04-08 13.52.43

Linked Models

What happens to linked models in this process? Links to other C4R models have a Path Type of “A360,” and the name should change after both models do a STC.

Screenshot 2016-04-08 16.24.27

 

However, it is important to note that when you download a Published version it will download a Zip file that includes all of the linked models. In addition, it will change those links to an Absolute Path to the extracted folder:

Screenshot 2016-04-08 16.24.27

 

If you enable the downloaded file for Collaboration again, it will maintain that absolute link, and will not load it. You will need to manually reload the linked model from C4R.

Screenshot 2016-04-08 16.31.55

Maintenance Workflow

Why note this behavior? On occasion, you should be performing maintenance on your C4R models, much as you would any other Revit model, and some of these tasks are best done offline. This means we need a workflow that involves changing names, enabling the cleaned-up model for collaboration, and reloading linked models.

In this workflow, let’s assume the model is called “State University Library – Architectural.rvt” with a linked model “State University Library – MEP.rvt”

  1. Make sure all users have synced their work, and closed the model.
  2. Publish State University Library – Architectural.rvt
  3. Download the Published version of State University Library – Architectural.rvt
  4. Rename the model on C4R. (E.g. State University Library – Architectural – Maintenance 2016-04-08.rvt)
  5. Open the downloaded version with Audit and Detach From Central checked.
  6. Perform your maintenance. (Our guide can be found here)
  7. In the cleaned-up model, enable the model for collaboration with the name State University Library – Architectural.rvt
  8. Close the model, open the C4R version of State University Library – Architectural.rvt, check all links, and do a STC

As an optional step, you can move the older version to a different project for archival purposes. This will preclude Project Contributors from accidentally editing the older file.

Note that if there are any Project Contributors who have access to the archival project, they can edit it; thus, you may want to set up a Closed or Secret Project without anyone Invited to the project, except your firm’s administrator. If anyone needs access to the older version(s) of the model, the admin can send them a share link in Team.

If you have questions about these procedures, please email us at support@microsolresources.com or by phone at 888-768-7568.

Categories: BIM, IT
SHARE THIS

About the author

John has been the Director of IT at Microsol since 2014. Prior to that, he worked with architecture firms. He is an expert in multi-site collaboration technologies, licensing, subscription software, CAD & BIM specific hardware & digital imaging.