Skip to main content
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
August 23, 2022
Solved

Work around for displaying classification attributes in a custom table view

  • August 23, 2022
  • 2 replies
  • 2040 views

I have a requirement to report out a whole mess of classification attributes for all levels of Parts Link classifications for a BOM (custom table views). According to this article, CS72284 , the answer seems to be that its not possible. Or is it? 

I have transitioned away from using soft-types to use PartsLink. As a result, all my previously soft-typed parts are now WTParts (normal Parts) and the previous soft-types are disabled from instantiation.  Since I am using the same attributes as I was before in PartsLink as I did with soft-types, everything transitioned over perfectly.  I also noticed or thought that the classification attributes were showing up in custom table views:

avillanueva_0-1661267880179.png

Well, not quite. What I was seeing was the attributes for the soft-type Parts that I am no longer using. When I added new attributes specific for PartsLink only, they did not show up, see previous CS article and pound sand.  

Not to be deterred, I wondered if I also added the same new attribute to the now defunct soft-type, would it show that attribute as selectable in the custom table view. Sure enough, it worked.  I will do some more testing but this is huge. Can anyone seeing and downsides or land mines down the road?

 

 

Best answer by avillanueva

I am going to put this in the confirmed column.  Sneaky work around.  I created a fake subtype of WTPart and added an attribute to it:

avillanueva_0-1661281874413.png

avillanueva_1-1661281899789.png

The part is non-instantiable or sub-typeable.  I have not created a single part of its type. Checking the available attributes for a custom table, Forward Current is not selectable:

avillanueva_2-1661281978035.png

Since this sub-type should be 100% removeable, I am curious to see what happens to the custom table. 

 

2 replies

S
17-Peridot
ScottMorris17-Peridot
17-Peridot
August 23, 2022

i have the same need, but i stopped looking for a solution until i have more time. my thoughts were to create an alias attribute on the wt.part that maps to the classification attribute, but this seems like a lot of work. would be nice if we could add the classification attributes to folder and structure tables. that is where most people want to use them. hopefully someone has a better work-around?

    avillanueva
    23-Emerald I
    avillanueva23-Emerald IAuthor
    23-Emerald I
    August 23, 2022

    If this works, you can simply create a non-instantiable soft-type that never gets used.

    avillanueva
    23-Emerald I
    avillanueva23-Emerald IAuthorAnswer
    23-Emerald I
    August 23, 2022

    I am going to put this in the confirmed column.  Sneaky work around.  I created a fake subtype of WTPart and added an attribute to it:

    avillanueva_0-1661281874413.png

    avillanueva_1-1661281899789.png

    The part is non-instantiable or sub-typeable.  I have not created a single part of its type. Checking the available attributes for a custom table, Forward Current is not selectable:

    avillanueva_2-1661281978035.png

    Since this sub-type should be 100% removeable, I am curious to see what happens to the custom table. 

     

      Terms & ConditionsCookie settingsAccessibility statement