new types added to shared family don't propagate to other nested instances

[james.levieux]

I have a family A nested inside of two other families,  B and C .  When I add new types to family A, and load it into family B, the new types appear correctly.  However, when I load family B into the project, and specify to load the nested family A into the project (instead of the A family already in the project), the new types in family A do NOT propagate to family C.

This is a problem because, when I open family C and don't see my new types, I think that I've done something wrong and start recreating the type I made earlier.  Or worse, I don't notice the types are missing and overwrite the project version of family A with the version that lacks the new types.

Furthermore, if I've used this nested family  A into many families D,E,F,G,H,J,X,W,R.... I'll need to remember all the families that need family A loaded.  It's a nightmare.

I'm creating my families in release 2018 so I'm hoping this might be fixed already.  As anyone else run into this?

Regards, 

James

[RDAOU]

No access to Revit atm to check but I think its the standard (closed files not updated). did you try from the browser to reload B,C,D,E .... and when Revit asks about subcomponents select use existing/new A in the model? Which assuming A has the new types and is the same in all

[ToanDN]

The behavior you described is the same on any version.  You would need to open B, C, D, etc and reload A back in all of them.  On top of that, you still need one more trick to load all new types from A to B, C, D, etc...  But let's put it on hold until you ask for it.

If you are doing this a lot, consider using <Family Type> parameter to create Type selector, which you can select a type from A for B, C, D, etc.. directly in the project, without to open B, C, D...

[RDAOU]

---

@RDAOU wrote:

No access to Revit atm to check but I think its the standard (closed files not updated). did you try from the browser to reload B,C,D,E .... and when Revit asks about subcomponents select use existing/new A in the model? Which assuming A has the new types and is the same in all

---

@james.levieux 

Just wondering What is the purpose of loading ALL Types of A into .rfa of 20 Families??? One may understand that 10 types of Nested A are required to be loaded into Family B.rfa  because 10 types of B may be required in the project; however, why would the new 10 types of A be needed in Families C/D/E/F/...etc considering that

1. These families may not need more than 1 Type in the project. (ie:  the 1 Type of Nested Family A suffice)
2. Or when each of these families may require a various number of types but necessarily all 10 that correspond to the types of A (ie: 2 or 3 types of nested Family A may suffice)

You need to consider that Loading too many type of one family into all families does affect the performance of the model and for that purpose people use Type Catalogues.

• What is loaded into the project is an image not live linked to the .rfa saved on the hard drive.
• When one edits the family, one is editing the .rfa
• The .rfa may have 1 type while the project may have 20 types and vise versa. 
• When one needs more/new types of C/D/E/F...etc, one would simply generate them straight in the project without editing the families in editor and without reloading all the types of Family A into the .rfa of all parent families C/D/E/F...etc (only what is required)

If the intent is to update the existing .rfa library and the type catalogues after creating the new types in the project, then you would simply go to File Menu >> Save As >> Library >> Family .rfa this way only the the relevant types from the subcomponent are carried over from the project to the updated library .rfa