Yeah unfortunately this isn't possible. Since the classic Maximo UI executes a SQL filter to search, it has to be persistent to enable searching. For hierarchypath, we created a view in our system that builds this path out so we could use it for reporting and other purposes.
With the new work centers and transition to the REST API, I expect this to change. As an example, there was a new system property added in 7.6.1.2 (mxe.int.allowrestnpsort) which based on the name allows you to sort on non-persistent attributes. It's disabled by default, but if they can do this, I'm confident they can eventually do the same for filtering. And when the dataset is smaller and all the data could already be available locally, you can easily do client side filtering. I expect to see them do a combination of this with the new UI work they're doing.
------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------
Original Message:
Sent: Wed July 07, 2021 01:22 PM
From: User1971
Subject: Filter non-persistent field in list view?
MAM 7.6.1.2:
Is it possible to filter a non-persistent field in the list view?
I believe the answer is no. But I just wanted to check if there are possible workarounds.
Thanks.
#AssetandFacilitiesManagement
#Maximo