cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to add PartsLink classification attributes in any table views

Ability to add PartsLink classification attributes in any table views

 

When using Partslink, we are able to define different Classification NameSpace and/or different Classification trees with specific attributes at nodes level.

classif attributes.png

 

 But it is impossible to display these attributes in the configurable table views of Windchill.  Notably PSB , MAPSB, CAD2Part compare,Advanced Search Result,  folders, collectors, Change impacted/resulting ,  etc ...

Except the Node/Binding attribute ...

 

GregoryPERASSO_1-1588090818058.png

 

 

6 Comments
OliverDroop
Garnet

Gregory,

can you specify how this should look like since worst case each object could have a different attribute set which makes usability a nightmare.

I like the idea in general and there are definitely some attributes which are on the main nodes and therefore on almost every object.

Oliver

GregoryPERASSO
Aquamarine

Hello @OliverDroop 

You are right for the worst case … no real usability idea except if the table automatically hide columns where there's no values

Or if all table views we can , as in excel, filter by values  to reduce the list ….

 

But as you says, we try to control the way we build classification nodes.  And some "main" attributes will clearly be common on main nodes

mlasri
Regular Member

Hello Greg,

 

It is actually possible to display classification attributes in PSB table... I have to admit that I found that by accident. Some of the classification attributes I set up are also declared as well on the "CAD Document" type (in order to manage some CAD to Part mapping of classification attributes)

The result is that these attributes also declared on CAD Document type can be selected and displayed in PSB table as shown below:

 

12-10-2020 15-16-40.jpg

I am not sure it is an expected behavior... but still it may be a workaround.

GregoryPERASSO
Aquamarine

Hello @mlasri 

thanks for the input.

Does it mean that your classification attributes are also created as "classic IBAs" on WTpart ?  or only on CADDocument and  as you say , probably an expected behavior due to the fact that the CADDocument can be displayed as related Docs in the PSB  ….

 

But for a workaround, As you know ,  we can not really imagine setting all our classification IBAs on CADDocument type  .  Not sure that the type manager will allow such elements …    😉

mlasri
Regular Member

No, the classification attributes are only defined on classification nodes. They are not defined as "classic IBAs" on WTPart. They are however defined as "classic IBAs" on CAD Document.

I thought like you that it might be expected due to the fact that related CAD documents can be displayed in PSB.

Definitively, from a usability point of view it will not work if there are a large range/variety of classification attributes

+1 Vote @GregoryPERASSO very good idea.

There is the same limitation in the Folder, Advanced Search Results view and MAPSB.

 

Thanks a lot @mlasri for the tip. This helped me to avoid having to create alias attributes on WTPART to be able to display classifications attributes in PSB views 😀.

2020-11-19_19-04-13.jpg