i am working on creating a new piping end cap. while doing so i was going to have a coupling i made flex with it. is there a way to use a lookup table to change the label on the nested family?
Solved! Go to Solution.
i am working on creating a new piping end cap. while doing so i was going to have a coupling i made flex with it. is there a way to use a lookup table to change the label on the nested family?
Solved! Go to Solution.
Solved by mark.j.eaken. Go to Solution.
Solved by mark.j.eaken. Go to Solution.
Just associate the parameters under type properties in family browser I think... edit: ow to change a label you wrote, probably some formula for a type parameter within the nested family based on a number ie... not exactly sure
Just associate the parameters under type properties in family browser I think... edit: ow to change a label you wrote, probably some formula for a type parameter within the nested family based on a number ie... not exactly sure
So, the way I understand it, is that you have a Nested Family with a Parameter that you to use as a Tag Label. If so, make the Nested Family Shared, and the Parameter that is be a Tag Label Shared and an Instance Type Parameter. Then load this Nested Family into the Host Family and Associate this Instance Parameter to a Host Parameter using the same Shared Parameter. Additionally, the Tag Label must use the same Shared Parameter. Now you can attach a Tag to the Nested Family in the Project by TAB-Selecting on it.
...and, YES, you can include this Host Shared Parameter in the Lookup Table.
So, the way I understand it, is that you have a Nested Family with a Parameter that you to use as a Tag Label. If so, make the Nested Family Shared, and the Parameter that is be a Tag Label Shared and an Instance Type Parameter. Then load this Nested Family into the Host Family and Associate this Instance Parameter to a Host Parameter using the same Shared Parameter. Additionally, the Tag Label must use the same Shared Parameter. Now you can attach a Tag to the Nested Family in the Project by TAB-Selecting on it.
...and, YES, you can include this Host Shared Parameter in the Lookup Table.
@barthbradley wrote:...and, YES, you can include this Host Shared Parameter in the Lookup Table.
Drive a type parameter from the Lookup Table? Didn't think you could... which is why I was thinking to use a number parameter to drive the type parameter in the nested family. But that idea and how you've described it is pretty much the same I suppose, something along those lines...
@barthbradley wrote:...and, YES, you can include this Host Shared Parameter in the Lookup Table.
Drive a type parameter from the Lookup Table? Didn't think you could... which is why I was thinking to use a number parameter to drive the type parameter in the nested family. But that idea and how you've described it is pretty much the same I suppose, something along those lines...
What I said was "Instance Type Parameter", meaning the type, sort or kind of Parameter. I guess I shouldn't have capitalized the "T". Sorry. My bad.
What I said was "Instance Type Parameter", meaning the type, sort or kind of Parameter. I guess I shouldn't have capitalized the "T". Sorry. My bad.
so i fixed the problem by changing the way my nested family was driven. changed it from Type Name driven parameters to creating a Lookup Table for it. Works great now, thank you all for the help and ideas, now onto the next problem i created 😃
so i fixed the problem by changing the way my nested family was driven. changed it from Type Name driven parameters to creating a Lookup Table for it. Works great now, thank you all for the help and ideas, now onto the next problem i created 😃
Huh? Come again. That reads like a word salad to me. What did you do?
Huh? Come again. That reads like a word salad to me. What did you do?
i changed how the nested family flexed.
i originally was trying to control type name thru a lookup table but from my understanding you cannot.
creating a lookup table for the nested family let me control it better within the parent family by just linking the Nominal Diameter.
i changed how the nested family flexed.
i originally was trying to control type name thru a lookup table but from my understanding you cannot.
creating a lookup table for the nested family let me control it better within the parent family by just linking the Nominal Diameter.
Can't find what you're looking for? Ask the community or share your knowledge.