Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
There was a thread on this from ~10 years ago (here) and I'm sure things have changed for the better since then.
Is there a way to autoassociate CAD to a soft type of a WTPart in certain contexts?
I have 2 subtypes of WTParts and one is set as the default on CAD associations.
In one context, I want the other one to be the only WTPart type going in. I tried adjusting the preference for that context (Operations/General/Custom Modeled Part Class and added my WTPart internal name there) and I tried adjusting the OIR to enable only the subtype I want AND in the OIRs calling out wt.part.WTPart|my custom part internal name. Still, it auto-associates to the default.
Solved! Go to Solution.
Hi @Dobi
You need to define 2 CAD SubTypes where you define different WTpart type in type and attribute management.
Then you can set model parameter to define what CAD Document subtype should be used for that model and then the auto-generation uses WTPart subtypetype defined in the type and attribute management
CS41665 - How to create subtypes CAD Document
So your start models just need to contain that parameter with correct value.
PetrH
Hi @Dobi
You need to define 2 CAD SubTypes where you define different WTpart type in type and attribute management.
Then you can set model parameter to define what CAD Document subtype should be used for that model and then the auto-generation uses WTPart subtypetype defined in the type and attribute management
CS41665 - How to create subtypes CAD Document
So your start models just need to contain that parameter with correct value.
PetrH
Hi @HelesicPetr and thanks for that!
So there isn't a way to do this association without having a CAD subtype, I take it?
I'll give this a try.
Hi @Dobi
Yes there is a way with customization. I showed you how to achieve your needs by OOTB functions.
With customization you can do whatever you want. You just need to know what is condition so set correct subtype.
For example @RandyJones has mentioned one option with custom class that is configured in preference management for autoassociation.
PetrH
We do this very thing here where different contexts need different WTPart subtype associated. We are doing this as follows:
Did you do this with CAD subtypes or just with the string attribute?
@Dobi wrote:
Did you do this with CAD subtypes or just with the string attribute?
With my method you do not need CAD Subtypes - we do not use them. The string attribute is defined on the containers (Product, Project, and Library) using Type and Attribute Manager.
Screenshot of a Product showing this attribute.