Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Allow Direct Dynamic Linking of Families!

Allow Direct Dynamic Linking of Families!

After writing my Magnum Opus over here on titleblocks, I have a simple (almost fundamental) idea for you:

 

Allow direct dynamic linking of a revit family.  By that I mean eliminate the static copy of every family that exists in a revit model once it's loaded.  

 

Basic example:  You have Project A and Family 1 version 0.  You open Family 1 version 0 from a family (.rfa) file sitting in your working directory and then load it into your project.  Congratulations, now you have two copies of that family one in a .rfa file in the directory and one in your project (.rvt).  

 

Say you make a change to Family 1 and create version 0 (and that you do this in your project).  You must remember to save (or save as) the family over that .rfa in the working directory.  If instead of saving you just load into project and don't save, now you have version 1 of Family 1 in the project and version 0 is out there languishing in the project folder.

 

This seems unnecessary.  We should be able to directly link in a family and use it without storing a static copy in our revit project.  

 

As a sidebar:  I guess only revit models are allowed to be treated this way now.  And that's not even really true is it...you must manually reload models  (or at least that was the way it was in 2014 and prior versions, in 2015 and later Revit seems to automatically reload for you).  

 

Sidebar #2:  This problem is really exacerbated by project templates... If you start a project from a project template you get all the families in that template as a starting point.  If your company also has a library of families in a directory structure (in .rfa files), you must VERY carefully manage that these copies stay in sync with each other and all updates to families are saved in both places.  Totally non-automated.

2 Comments

Glenbob305,

 

I understand your concern, but I'm afraid your solution is not directly a valdi one either.

Since, if one changes a thing to your idea, he should be so very much more carefull, since this change would immediately affect all other projects within your office, even if it is a project in progress, where already another workaround was found for the problem someone tries to solve with a newer version.

I think, in practice, the main library is in your head, and in remembering which families worked best in a similar project... since you don't need all of the same things over and over... 

Status changed to: Archived

Thanks for taking the time to submit your idea. Unfortunately, this idea did not get the support of the community (votes or comments) over the last 24 months and as such we will not be pursuing it at this time. Please feel free to re-word (titles and clear descriptions are very important) and resubmit this Idea.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea