Parameters double nested family disappear

[Anonymous]

Hello all,

I have some trouble transferring parameters in nested families. The issue I have is most clearly described as follows:

- I create a generic model family (Let's call it GM1) with for example a length dimension which I make a parameter. As a result the parameter shows in the Family Types menu, in which I can change it's value and the correspondent length changes with it. The model is workplane based.

- I create a new generic model family (GM2) in which I create a reference line with an angle (XY angle). This angle is also added as a parameter. Next I nest GM1 on the reference line. This nested GM1 now has at the Family types menu the parameter angle, which I can change with no problem. And in the properties of the GM1 model it has the dimension length which I can change with no problem. Again I make the family workplane based.

But now comes the problem

- I create a new generic model (GM3) in which I create a reference line with an angle (Z angle). In this family I nest GM2 on the reference line. At the Family Types menu I have the Z angle which I can alter with no problem (GM2 alters with it), but in the properties menu of the model, I now only have the XY angle dimension. So in the process of nesting GM2 in GM3 the Length dimension parameter of GM1 has disappeared.

I'm hoping someone can tell me why the parameters are only transferring to the first family it is nested in. All parameters are instance parameters classified as length or angle.

Regards,

Peter

[FGPerraudin]

Hi @Anonymous,

I think your problem is quite simple.

You need to be able to access your GM1 parameter from a Higher level family.

From GM 2 it is easy, "classic".

But in order to access your parameter from GM3, you need to "report" your parameter.

In GM2, create a parameter named explicitely that will report your GM1 parameter (ie: GM1fromGM2)

That parametrer will be accessible from GM3.

Associate it with your GM1 parameter.

When you change your GM2 parameter in GM3, it will "cascade down" to GM1.

Hope this helps,

François

[Anonymous]

François,

Thank you for your reply. I have tried to work out your solution but haven't found a way to implement it succesfully. Could you maybe elaborate on the steps in your solution so I can work it out in my file? Thanks in advance.

regards,

Peter.

[FGPerraudin]

re-hi @Anonymous,

Can you send your family?

-I'll have a look at it and send it back in working state - you will then understand what I meant!

It might be that an adaptative component is much more suitable according to what you want to achieve...

François

[Anonymous]

François,

Sure, I attached it to this message, thank you for the effort.

Regards,

Peter

[FGPerraudin]

Fantastic.

I work with Revit 2017, so is it still interesting for you?

[Anonymous]

Does this affect wether or not your solution works for me in Revit 2015?

I am bound to 2015 for this project (Annoying outdated sub contractor). But am able to inspect your file in Revit 2017.

[FGPerraudin · Accepted solution]

The solution will work for you in Rvt 2015.

So here it is:

This is your nested family (check the title of the window to be sure). You need to:

1. Create a new parameter following the
2. instructions.
3. Associate your nested parameter to the new one.

You will have the same issue with your final family (the one you sent me), so you need to do exactly the same manipulation and create two "reporting" parameters:

Then they will be accessible straight from your project!!

Finally, here is the working family as an attachement.

Tell me if you need more help,

Just go through it it should make things clear,

Cheers,

François

[Anonymous]

Thank you! This explanation solved the problem for me. I have all the parameters now in the final family and editable. 

[FGPerraudin]

Happy to be of any help!

Cheers,

François