Odd behavior nested shared families

[bahaaeldien.metwaly]

Hi,

I'm having a recurring problem where some random instances of a shared family - nested in a host that derive their instance parameters - tend to have their parameter values reverted to default, ignoring the host's values.

Example:

Shared family of a box, with "Height" of 500mm as default. Height is an instance parameter that is linked to host's type parameter "Box_Height"

The host is then nested and copied multiple times inside a main family, with "Box_Height" now driven by a new parameter in the main family.

After updating the family a couple of times .. some boxes will ignore the height given to the main family and have it back to 500mm.

Attached is a sample for Revit 2016.

Appreciate the support 🙂

[barthbradley]

Sounds like you reloaded the family into the project, and choose to overwrite the parameter values in the project with those in the family. Don't pick that option. 

[bahaaeldien.metwaly]

hi Bradley,
I never pick that option, in fact I deleted all old versio s before loading to upper level every time i nest the family or load it to the project.

I'm building a bit complicated families and used to have this problem for over a year. But it's getting un avoidable now.

[ToanDN]

So is it solved now?  I am a bit confused.

[bahaaeldien.metwaly]

I just loaded the page and found it marked as solved, but no it's not .. how can i undo it ?

[barthbradley]

Ouch! I'm looking at your family right now and feeling the burn. It's quite a monstrosity.  Frankly, I'm wondering why it doesn't mess up more often than it does. But, I will say, you did do it well for the most part. I don't see any fault with it per se. I am just wondering if it couldn't be simplified. For instance, maybe through using a Type Catalog. 

I'll explore it some more when I have some time -- and another cup of coffee. Ha!

Thanks for the solution credit all the same. I owe you one.  

[bahaaeldien.metwaly]

Hi Bradley,

Thanks for looking into it. the example i attached was a family type controlled by an integer parameter, but this is not always the case, I have other families that have simple controls like length, left hand/ right hand or even parent name, to be stored in nested families. what i found out recently is that whenever an instance goes odd it ignores all it's linked parameters, so you can easily track which ones are not following. but that doesn't help much if these models are used by others for coordination.

[ToanDN]

It appears you didn't associate the parameter of the two instances to different parameters in the parent family.  Do that and you shouldn't have the issue described.

By the way, why so many levels of nesting?  It doesn't seem necessary in this example file.

[barthbradley]

Wait a minute! Why would that be the solution? It's family type driven. That makes no sense to me. Sorry, @ToanDN.  

[ToanDN]

---

@Anonymous wrote:

Wait a minute! Why would that be the solution? It's family type driven. That makes no sense to me. Sorry, @ToanDN.  

---

Then associate them with Type parameters.  Enter the value directly for nested family instances can cause the exact issue as OP described, especially when the family have multiple types.

p/s: what the heck is going on with this thread?  It seams like the last response always receives Solution and Kudo.  Can you post something after this to confirm @barthbradley?

[barthbradley]

C'mon @bahaaeldien.metwaly!!! Make a decision here. Don't keep giving us solutions credits and then yanking them away.  It's very demoralizing. 

[barthbradley]

thank you, @bahaaeldien.metwaly. I live to fight another day. 

[bahaaeldien.metwaly]

every reply is automatically marked as a solution before i even check it !

[ToanDN]

@bahaaeldien.metwaly

If you did not accept Solutions and give Kudos then I think this thread is broken. I would start a new thread.

[bahaaeldien.metwaly]

Alright, I'll collect some more examples and start a new one .. thanks both 🙂

[Discussion_Admin]

---

@bahaaeldien.metwaly wrote:

Alright, I'll collect some more examples and start a new one .. thanks both 🙂

---

@bahaaeldien.metwaly

I unmarked the accidental solutions.

Please continue the conversation here in this thread.

Thanks
Discussion_Admin

[Anonymous]

Hey guys,

I was wondering if you found a solution. I have 2 nested families that are exactly the same except one has nested families that are not shared and the other has those exact same families, but shared.

The parent family with the nested shared parameter does not respond when i change parameters. e.g. if I change the length, the geometry does nothing. The one with the unshared nested families does change perfectly.

PS: The problem only exists in the project. In the family editor both work, and react the same.

[bahaaeldien.metwaly]

Hi Verdi,

I was able to fix the problem long back that I won't be able to give you the exact answer.

but it'd be one of two things:

- make sure all parameters of the shared-nested are instance parameters.

- make sure the default parameter values of the shared nested is far from your actual need, forcing it to be updated when placed.

it's a glitch , so don't seek a reason..

and share me the faulty family if you still need some help.

[Anonymous]

Hi Bahaaeldien,

I have 2 families attached. the family 01 is the one with shared nested families and does not work. The family 02 is the one without shared nested families and does exactly what I want it to do.

I have also tried creating a totaly new parent family where I just put 1 shared nested column in there and try the change the height in the parent family. It does not work. With a nonshared nested column it does work to change the height in the parent family.

[bahaaeldien.metwaly]

Both are reflecting very well for me .. any particular parameter ?