Ok, different plan:
How about adding two columns to the List tab: CLASSSTRUCTURE.HIERARCHYPATH and CLASSSTRUCTURE.DESCRIPTION
This way, users could
search on the List tab based on the persistent Description field, and still get to
see the Hierarchy Path. And if the user
has to search with the Hierarchy Path, then they'd have to use the Advanced Search dialog.
(I'm doing this exact thing in Item Master, FWIW)
------------------------------
Travis Herron
------------------------------
Original Message:
Sent: Wed July 07, 2021 12:53 PM
From: User1971
Subject: Use classification drilldown in WOTRACK list view?
Note:
HIERARCHYPATH is a non-persistent field. It doesn't seem to be possible to filter the list view using a non-persistent field.
Original Message:
Sent: Tue July 06, 2021 10:36 PM
From: User1971
Subject: Use classification drilldown in WOTRACK list view?
A beginner's observation:
psdi.webclient.beans.common.SearchSpecBean updateOriginatingRecord() ... seems to be hardcoded to only return the hierarchy path value for specific applications and beans: [updateClassstructure(hierarchypath)]
- VIEWSR application
- SelectMoreAssetsMoveBean
- SelectMoreLocationsBean
- SelectMoreCIsBean
Notice that WOTRACK isn't in that list.
To test that theory, I added a classification drilldown field to the VIEWSR application. And it worked, unlike the WOTRACK list view. So that leads me to believe that the above observation is correct.
(Bear in mind, I have no idea what I'm talking about.)
#AssetandFacilitiesManagement
#Maximo