Our data model contains about 400 WTPart sub-type. These sub-types have there own attribute list. A large part of them are reused through the sub-types.
The end-user who perform the search know the attribute name but not all there use cases.
Example : The attribute "Luminescent material" is defined on about 10 sub-types.
We want to search for all WTPart there "Luminescent material" = Tritium.
Now we have to know the 10 use-cases of the attribute and select them in the list of 400. But it could be easier to select the Parts type and have the entire attribute list of sub types.
This behaviour should be set with a preference.
Wow, sounds like a lot of soft types. I think your use case is not common to how other people use Windchill. We use Partslink to classify parts which removes the complexity that you have created by controlling part types with different soft types.
That being said, it's still a good idea, but if you had 400 soft types and you wanted to search on all available attributes on those soft types, how long is that list of attributes? It's possible it could be an unmanageable list of attributes.
We tried to use Partslink but for many reasons it was unimplementable. But we know that our data model is a limitation and will work on a retrofit on Partslink.
That's correct the list could be unmanageable but we can imagine a picker with filter options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.