Issue Tagging Family with a Nested Family

[Anonymous]

I have asked about this issue before. There seemed to a workaround at the time. But, it has failed to work. I have a family with a nested family in it. The nested family has a control connector. When this family is nested into the "main" family. It screws up the tagging. You tag the family in a project. The tag jumps into outer space. Becomes a complete mess when tagging all or tag on placement. Can't find what tag is associated with what family. I've tried all the past "fixes" but nothing seems to work. Why is this doing this? Any potential workarounds or fixes?

Thanks.

Revit 2016

[kadmonkee]

have you tried removing the control connector from the nested family and place it in the live family?

the live family has a power connector in the live family, it seems the tag is taking those parameter first

also neither (generic Model) family has any parameters assigned to them.

Shared Parameters may help also

try changing the family category to be more specific. (Electrical Fixture, Electrical Equipment ) etc.

what is the end result you are looking for?

[Revit_Whisperer]

Did you try setting the leader to Free End rather than Attached and then placing the tag?

[Anonymous]

have you tried removing the control connector from the nested family and place it in the live family?

I need to be able to circuit and tag the nested family separate from the live family. Only way I have figure that out is with a nest SHARED family with a connector. The circuiting aspect works great. Its the tag jumping far away that I'm having trouble with.

the live family has a power connector in the live family, it seems the tag is taking those parameter first

also neither (generic Model) family has any parameters assigned to them.

Shared Parameters may help also

In the end, this will be be a light fixture family. I have already created the families w/ shared parameters and parameters. Same result. The family I posted on here is just a quick example of the issue.

[Anonymous]

Did you try setting the leader to Free End rather than Attached and then placing the tag?

Yes, I have done that. It does seem to work the majority of the time. The main issue, is that I want to tag all and/or on placement. No control at that point. Trying to save time. Tagging each fixture in a building one by one is such a waste.

[kadmonkee]

look at the tag itself and the parameter associated with the tag

check the wrapping aspect and the justification of the label

text style options

[Anonymous]

Everything looks normal in the tag. It works just fine without the nested family. Also, it works with a "Free End".

[kadmonkee]

are the parameters in both the live family and the nested family the same?

maybe create a separate tag for the nested family or at least a different named parameter 

[kadmonkee]

are the parameters in both the live family and the nested family the same?

maybe create a separate tag for the nested family or at least a different named parameter.

[Anonymous]

They are different tags. The only thing in common with the tags is that they both show the circuit number for which they are circuited. Since that is the data that I need in the tag. Not sure how to get around that. 

[Anonymous]

So, that seems to be the issue. That I'm pulling the circuit information for both the live family and the nested family. Even though they are different tags. I just tested it by pulling something other than the circuit # from the nested family. And the tag did not jump off. Now... how to pull the circuit information for both families without the jumping of the tag? Not sure its possible. 

[Anonymous]

Also, it will not place a "tag on placement" if the leader is unchecked. Man, this thing gets buggy with a nested connector. 

[martinTstewart_Adsk]

Best practice at this time is to avoid nesting connectors, keeping connectors in the host family.

See also: Family with connectors in a nested family causes it to be incorrectly selected
 

For suggestions on Revit improvements or new features, please check for Revit Ideas to vote up and submit your own Idea posts.

If my reply was helpful, please give a "Kudo" or click the "Accept as Solution" button below (or both).

[Anonymous]

Thank you for the information. I understand that the issue exists. Struggling to find a way to be able to circuit a "relay" and a power connector from a light fixture family and get both the information from the power and "relay" to tag. We do not use wires on our views. I know that was a potential workaround. But, not for us.

[rudi.roux]

Hi @martinTstewart_Adsk, 

I'm not sure if this has been picked up by Autodesk, what I've noticed is that the tags "jump/tag" to the centroid of the instance (with nested connectors) and the project base point. 

Below is an illustration of what happens. 

I hope that this can serve as some useful information to possibly resolve this going forward. 

[jknight]

I know this is an old post but seems closest to my problem. I have a family of tanks and some heat exchangers inserted into a single family. I then have plumbed the two together. I have inlets, outlets, and assorted other fitting connections that I've added connector/tags too. I did remove them from the individual nested families as they don't come thru to the main family from what I've researched. I have 3 different tank heights with the same diameter, and the tags I add to the connection points stay attached to the connection face when changing between the different heights. However, when I change to a different diameter the tags go all over the place. I have seen that you can't really attach tags to nested families and that you really have to recreate the fitting in the main family. But how do these tags stay attached and move with the faces until I switch to a different size tank? Hope someone can help... Thanks in advance. I'm using 2016

[s.borello]

Why do you need nested family?

[jknight]

Well I have a family or the heat exchanger and a whole family of the tanks. So I inserted each and then added the piping to connect them together. I had finally got all of the these to work together and adjust like they should only to come up with this issue. I was trying to have everything in one model and not have to do multiple models to make things somewhat work.

[jknight]

Here's what I'm doing...