Problem with reloading Family contains nested shared families when changing some parameters

Problem with reloading Family contains nested shared families when changing some parameters

Mohamed_Faramawy
Advocate Advocate
593 Views
8 Replies
Message 1 of 9

Problem with reloading Family contains nested shared families when changing some parameters

Mohamed_Faramawy
Advocate
Advocate

Hello everyone,

 

I am facing a problem will try to explain: 
I have Family A (host family), contains some nested families and family types, lets say Family B (nested shared family) 
Family B has some type parameters.

when i change some parameters for Family B within Family A, and then reload Family A (host) to the project, the project doesn't update the new parameters of Family B (nested) 

attached this example in revit 2024 files 
The example is to open family A and change some parameters of Family B (which is nested inside), then load Family A into a project

The problem: the updated parameters of the Family B is not updated
sometimes the a dialog appears if i wanna overwrite the parameters or not, sometimes the dialog doesn't appear at all.. the revit has a random behavior in this issue.. 

please advice and help, noting that, this is just a sample but in my real project Family A is a very huge family contains many nested families so any manual solution will be nearly impossible

 

One more final note: i tried to make the parameters shared but it wont solve the problem also.. 


Thanks in advance 

0 Likes
Accepted solutions (1)
594 Views
8 Replies
Replies (8)
Message 2 of 9

Simon_Weel
Mentor
Mentor

when i change some parameters for Family B within Family A, and then reload Family A (host) to the project

If Family B contains Instance parameters driven by Family A, it would / should work.

But you modify Type Parameters in Family B and since Family B is a Shared Family, you have to reload it into the project - not into Family A.

0 Likes
Message 3 of 9

Mohamed_Faramawy
Advocate
Advocate

but even if i reloaded the nested family directly to the project sometimes the project doesnt update the new parameters.. especially if Family B is already in the project 
am i correct ?

0 Likes
Message 4 of 9

Simon_Weel
Mentor
Mentor

Since it's a Shared Family, Family B is (also) available in the Project Browser under the Families. So if open it, make some changes and reload it into the project, you should get the familiar dialogue if you want to change the parameters as well. And if you just need to modify some parameters, use Edit Type from within the Project Browser.

0 Likes
Message 5 of 9

Mohamed_Faramawy
Advocate
Advocate

the work flow forces me to do the modifications of the nested families within the host family itself, not in the project.. why? because i 
1- i can modify the type parameters of the shared nested element in the project file, but i cannot move it or relocate it 
2- i have to add elements to the host family, which are more nested families 

i need to say that the real case is a marble fixation sub frames (screen shot attached)

RKS_PRECISION_0-1778576028695.png

this is the family screen shot 

RKS_PRECISION_1-1778576080322.png

this is the project where i load the subframes family 

 



0 Likes
Message 6 of 9

Simon_Weel
Mentor
Mentor
Accepted solution

Ok, but the problem is: modifications to parameters in shared families (in the Family Editor) don't (always?) show up in the project, right?

I had a look at the project and families and it's pretty straight-forward. And it works as expected - at least on my side?

What I've done is open Family A (host), open Family B from within Family A, modify parameters for one of the types. Loaded B back into A and then loaded A back into the project. Then Revit presents you with this:

Simon_Weel_0-1778586985995.png

The first option is to use Family B in the host family, overwriting the same Family B (model elements) that's already in the project, but use the parameter values of Family B as specified in the project. I.e. discarding any changes to parameters you made in the Family Editor for Family B.

The second option does basically the same, but instead of using the parameter values of Family B as specified in the project; use the values specified in Family B itself.

The third option uses Family B as specified in the project. I.e. discarding any changes to model elements and parameters you made in Family B.

I guess in your case, you should use the second option.

Message 7 of 9

obulesub
Community Manager
Community Manager

Hi @Mohamed_Faramawy ,

Did the info from @Simon_Weel  help answer your question?

If it did, it’d be great if you could click the "Accept Solution" button so others can easily find it too.

If you’re still needing more help, feel free to share an update here. The community will be happy to jump in with any next steps to help you get where you need to be.

Best, 

Obulesu | Community Manager

Obulesu | Community Manager
0 Likes
Message 8 of 9

obulesub
Community Manager
Community Manager

Hello @Mohamed_Faramawy ,

Just checking in—did the responses shared by Simon_Weel  help clarify your question?

If so, please consider clicking the "Accept Solution" button. Doing so helps others in the community find answers to similar issues.

If your question still needs more attention, feel free to reply here with an update. This way, other members can jump in with further suggestions or guidance to help you move forward.
 

Obulesu | Community Manager
0 Likes
Message 9 of 9

Mohamed_Faramawy
Advocate
Advocate

I would like to thank u for your efforts 

0 Likes