MAM 7.6.1.2:

I have a db view that I am adding to Maximo as a imported view object (not yet saved).
The view has attributes that are costs. The attributes have been automatically added to the object.

The Search Type of the attributes has been automatically set to NONE...and the Search Type is read-only, even though the object has not yet been saved.

I know from experience that the Search Type needs to be EXACT in order for the cost fields to be searchable in places like the WOTRACK Advanced Search window.

Question:
How can I change the Search Type to EXACT -- if the Search Type is read-only?



#AssetandFacilitiesManagement
#Maximo

If I set EXTENDS OBJECT to WORKORDER, then it partially works. I can inherit the SEARCH TYPE from the WORKORDER table -- at least for some of the fields in my view (but not all).

It seems to work for calculated number fields. But not calculated text fields.
#AssetandFacilitiesManagement
#Maximo

TS007493198

 

How to update Search Type if it's read only in Database Configuration

https://www.ibm.com/support/pages/how-update-search-type-if-its-read-only-database-configuration


RFE: View attributes: SEARCH TYPE other than NONE
https://ibm-ai-apps.ideas.ibm.com/ideas/MASM-I-615

Views Documentation:
https://community.ibm.com/community/user/iot/communities/community-home/digestviewer/viewthread?MessageKey=df08c582-8dfc-481d-80bf-f86ee0c64657&CommunityKey=3d7261ae-48f7-481d-b675-a40eb407e0fd&tab=digestviewer#bmdf08c582-8dfc-481d-80bf-f86ee0c64657

#AssetandFacilitiesManagement
#Maximo

#AssetandFacilitiesManagement
#Maximo

The solution was to use MxLoader:

1. Optional: Create the imported view object via MxLoader (or do it via the UI).
   1. The db view's columns will be automatically loaded as attributes. But the fields/values will just be the defaults...not what we want. The DB Config UI is too buggy to use...it's not possible to set the fields/values that we need via DB Config.
2. Update the attributes via MxLoader.
   1. Update attribute fields such as:
      1. Description
      2. Title
      3. Type (datatype)*
      4. Length*
      5. Search Type*
      6. Required
      7. Persistent
      8. Default value*
   2. *Bolded fields are buggy in the Maximo UI (arbitrarily read-only, depending on the combination of values). So we update them via MxLoader instead.
3. Apply db config changes. Works as expected.

Summary:
MxLoader solved all my problems. As mentioned, the the DB Config UI was too buggy to use.

Hopefully this can save someone from the frustrations that I went through.

#AssetandFacilitiesManagement
#Maximo

Details:

I loaded these attributes from MxLoader:


Which were synced successfully to Maximo:



I don't think that combination of TYPE, LENGTH, SEARCH TYPE, and DEFAULT VALUE was possible via the DB Config UI. It kept making fields be read-only for no reason.
But as far as I can tell, the MIF/business rules can handle the values ok...the sync from MxLoader worked fine. It was just the Maximo UI that was the problem.

Notes:

• For the UPPER fields like WONUM and SITEID, MxLoader didn't sync the LENGTH properly on the first attempt (values just stayed as the defaults). But if I ran the sync a second time, that worked. Not sure what the root cause was.
• Initially, I had tried using Application Import/Export to sync the attributes. That worked to a degree; it was able to sync everything except the TYPE and LENGTH. So I had developed a process where I did the TYPE and LENGTH via the UI, and then did everything else via Application Import/Export. And that was successful. But ultimately, it was a lot easier just to do everything in MxLoader. Since I didn't have the issue with TYPE and LENGTH in MxLoader.

Original Message:
Sent: Fri November 26, 2021 06:47 PM
From: User1971
Subject: View: How to change attribute search type (read-only) from NONE to EXACT

The solution was to use MxLoader:

1. Optional: Create the imported view object via MxLoader (or create through the UI).
   1. The db view's columns will be automatically loaded as attributes. But the fields/values will just be the defaults...not what we want. The DB Config UI is too buggy to use; it's not possible to set the fields/values that we need via DB Config.
2. Update the attributes via MxLoader.
   1. Update attribute fields such as:
      1. Description
      2. Title
      3. Type (datatype)*
      4. Length*
      5. Search Type*
      6. Required
      7. Persistent
      8. Default value*
   2. *Bolded fields are buggy in the Maximo UI. So we update them via MxLoader instead.
3. Apply db config changes. Works as expected.

Summary:
MxLoader solved all my problems. As mentioned, the the DB Config UI was too buggy to use.

Hopefully this can save someone from the frustrations that I went through.


Original Message:
Sent: Thu October 21, 2021 07:12 AM
From: User1971
Subject: View: How to change attribute search type (read-only) from NONE to EXACT
#Maximo
#AssetandFacilitiesManagement