I have many parts that all are iParts in and assembly. And they all have to change with eachother so the assembly itself is an iAssembly. When I change the iAssembly values so it changes the part it also changes the parts name on the parent child tree adding in a value.
In this case it added in "36" on the "LEFT_FRAME_LEG-SKIRT" and if i change the value in the table the value 36 will change along with it. This is where I run into my issue. I also need to use iLogic/Rules to suppress parts at times. but because the part names all change the rule losses what part it's related to. How can I get around this issue?
Solved! Go to Solution.
Solved by jalger. Go to Solution.
How should I use Level of Detail do you think? Also, the 72 was just like the 36 value, it can change depending on what part of iAssembly I select.
Hi ASchlaack,
You need to Stablize the Names first. (Change the name in the Browser to a generic name that reperents both the 36 and the 72 part)
So, "LEFT_ FRAME_LEG-SKIRT(_CO)36:1" Becomes "Left Frame Leg Skirt_1" Removing the ":1" makes it unique.
After that if you have different mates for each part you will need to suppress the mates and the parts at the same time otherwise you will end up with errors. The best thing to do is to make a quick excel spreadsheet or a quick hand drawn chart to figure out what you want to control.
You need to decide is what are you going to use as the control to drive the logic.
is it going to be driven by a user parameter, or a model parameter?
I hope this Helps,
James
James, I think that may just work. Thanks!
No problem,
Let me know if you have trouble coding it.
I love setting up models with ilogic.
Regards,
James
Hey James, I'm just now getting around to doing what you told me would fix the issue. And it worked. Thank you so much!!