Anuncios
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!

Ability to control workset for linked model

This request has been reported by customer and I am submitting on behalf of my valuable customer.

 

I'd like to control workset for nested Revit link model from the host model directly. For example, Model B.rvt has been linked into model A.rvt and model A.rvt has been linked into Host.rvt. I want to change workset for model B.rvt from Host.rvt.

Workset availability for B.rvtWorkset availability for B.rvtWorkset availability for A.rvtWorkset availability for A.rvt

Comentarios
Enthusiast
Enthusiast

Thanks Mr. Chong
Much appreciated for your support

Anonymous

You have mislinked your model.

 

Model A should have model B as an overlay link.

Both Model A and B should be directly linked into the destination file to allow for proper control. These are concepts that originated in CAD (overlay vs attachment in XREFs).

 

Trying to control a model in a model means that your client may not understand proper linking methodologies. If we go this route, people will want to control a link in a link in a link in a link in a link instead of linking properly.

It would be helpful to be able to assign a linked model to a workset when attaching or from the Manage Links window. My firm has this practice, but is running short of it implementation.  

I know the links when added are inserted in the active workset. But would be great if a little box could be added in manage links window, to choose the workset for all links uploaded. This applies for all type of links, and the option chosen should be saved between sessions.
 
Links_Workset.png

 

Autodesk Support
Autodesk Support

Reporting a scenario supporting this improvement idea: 

  1. Model A has nested links: model B and Model C (both attachments)
  2. Model A gets linked in the HOST file (with both model B and C getting put on the same active workset of the HOST when linked). 
  3. Model A receives a NEW model D as an attachment. 
  4. Model A gets reloaded in the host. Important to note: In this scenario, all previously existent (legacy) nested links remain on their old workset, but the new one gets placed in the host file on the active workset of the HOST model during the reload operation. 
  5. Should any of the Worksets of the nested links would need adjustments retrospectively, the only way for the user would be to remove and recreate the attachment in Model A and reload model A in the Host, with the active workset set to the desired one. Unfortunately this  action would ruin and delete previously placed tag and dimension elements associated with the nested link in question.