I've written some supplementary documentation about Maximo views, since the IBM documentation seems to be lacking in this area.
Maximo Views
There are two options for creating views in Maximo: Imported views and non-imported views.
Imported views:
- Create a view directly in the database via an SQL client. Import the view into Maximo by creating a Maximo object with the same name as the view. Maximo will automatically read the view definition from the database and import it by populating the object properties and creating attributes (including any custom/calculated SQL attributes).
- For imported view objects, the Extends Object property is optional.
- Once an imported view object is created via applying DB Config changes, the object properties will become read-only. Additionally, view attributes will become read-only (although a few minor properties will still be editable). Attributes can't be deleted. However, it is possible to create new attributes for an existing view object.
- If the view object or its attributes need to be modified, then you will need to recreate the view object by deleting the view object (deletes the database view), recreating the database view, and recreating the view object with the required changes.
- All fields will be automatically flagged as persistent, including any calculated fields. Persistent attributes can be used in reports and filtered in the list view.
- If the view has custom attributes, such as calculated SQL fields, and you plan to filter on them in the Maximo UI (example: filter in Advanced Search), then you need to change the Search Type from NONE to WILDCARD or EXACT, depending on the field type. This must be done before the Maximo object is initially saved. There are known issues with the Search Type property in Database Configuration.
Non-imported views:
- Alternatively, you can create a view in Maximo via the Database Configuration application. Create the view in Maximo by creating a new object and enabling the "View?" field. Enter SQL code into the SELECT, FROM, and WHERE fields. Or choose the "Automatically Select?" option.
- Non-imported view objects must have the Extends Object property populated.
- If the view has calculated SQL fields, then when you add the calculated fields as attributes to the object, the attributes will automatically be flagged as non-persistent. The "Persistent?" field is read-only. It’s not possible to use non-persistent attributes in reports or filter them in the list view.
- It is possible to modify non-imported view object properties, even after the object is created. You can also modify and delete existing attributes.
- Note: It's technically possible to use other SQL clauses like JOIN and GROUP BY in the view by including them in the FROM field (after the FROM clause SQL).
Additionally, the IBM Database View documentation categorizes views as dynamic vs. static (I think that's similar, if not the same, as the concept of imported vs. non-imported views).
There is information about views in the Maximo Secrets Imported Views page.
There is some outdated information about views in this tech note: Creating a non-auto select view using the Database Configuration application
On a side note, as a refresher about persistent vs. non-persistent objects and attributes:
- Persistent objects: tables and views
- Tables can have persistent and non-persistent attributes
- Views can also have persistent and non-persistent attributes
- Non-persistent objects: tables (not actual database tables)
- Views can only be persistent, never non-persistent, regardless of whether they're imported or not
- Non-persistent objects can only have non-persistent attributes
#AssetandFacilitiesManagement#Maximo