Joining Casework and Generic Model families

Joining Casework and Generic Model families

Anonymous
Not applicable
4,420 Views
7 Replies
Message 1 of 8

Joining Casework and Generic Model families

Anonymous
Not applicable

I'm a novice at Revit and started making casework families for work. A library of base units is my first objective and I made a single door base unit w/ plinth. And I found out the casework category doesn't join, so there are lines on plinth when I put the cabinets next to each other. the work-around I found online is either to change the category to generic model or make and finish the casework families w/ generic model template. It works, but the structures of the cabinets join as well. This will be the same issue for horizontal g-bar handle cabinet units.

 

To join only the plinth and g-bar not the structures, Do I need to make the elements separately instead of modeling inside of the cabinet family? or is there any other way to join selective parts of generic model family? or prevent the selective parts from joining? (pretty much the same haha)

 

Casekwork and Generic Model JoinCasekwork and Generic Model Join

0 Likes
Accepted solutions (1)
4,421 Views
7 Replies
Replies (7)
Message 2 of 8

ToanDN
Consultant
Consultant
Create the side panel as a separate family, under Casework category, nest it in you base cabinet family and associate parameters to match the dimensions. They will not join.
Message 3 of 8

Anonymous
Not applicable

Hello!

What do you mean by "associate parameters to match the dimensions. They will not join." ?

 

Currently the whole structure box is a separate casework category family and nested inside of a base unit family, which has a door panel and plinth in generic model category. I associated the structure box's width/height/depth parameters but they joined anyway. I attached the file fyi.

0 Likes
Message 4 of 8

ToanDN
Consultant
Consultant
Accepted solution

See the revised family loaded in a project and join geometry.  The bases join but the panels don't (I added the base piece for clarity since the family doesn't have one).

 

Annotation 2019-12-11 110424.pngAnnotation 2019-12-11 110455.pngAnnotation 2019-12-11 110049.png

Message 5 of 8

Anonymous
Not applicable

Wow.

I assume your avoiding working at work since '97 helped thousands on this forum.

 

Just to confirm if I correctly understand what you did here.

what you did is to uncheck 'Shared', which is Shared: This parameter is only relevant when the family is nested into another family and loaded into a project. If the nested family is shared, you can select, tag, and schedule the nested family separately from the host family. If the nested family is not shared, then components created by the host family and nested family act as a single unit. from the manual.  Since they act as a single unit, the caseworks don't join. Thanks.

 

0 Likes
Message 6 of 8

ToanDN
Consultant
Consultant
The definition is correct but it does not cover the joining differences between shared and not shared.

- If you do not want the nested casework panels to join, check the Shared box
- If you want the nested casework panels to join, uncheck the Shared box
Message 7 of 8

Anonymous
Not applicable

You're right, it doesn't cover the joining behavior. And It makes sense now that I know what 'shared' is. Thank you.

0 Likes
Message 8 of 8

Anonymous
Not applicable

Hey, after checking Shared, I changed all the family parameters (width, height & depth) to shared parameters in order to schedule them under Generic Model Category. Now I cannot associate the parameters of the nested and host family (No small grey box and equal signs).

 

Do you know the cause of this problem and possibly solution for it?

1) shared parameter in host family cannot associate with family(built-in) parameters in nested family?

2) Do I need to use shared or instance parameters in nested family instead of the built-ins?

 

Edited_

Never mind. I changed every family parameter to instance and they can be associated.

but, If you know why and let me know, that will be great. Thank you.

0 Likes