Troubleshooting
Problem
Users may face the error below when trying to change an application presentation, in the Application Designer app by adding new TextBoxes in the Canvas. BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL
Symptom
BMXAA6713E - The MBO fetch operation failed in the mboset with
the SQL
Environment
Maximo Asset Management 7.6 Multi-Tenant only
Diagnosing The Problem
In a Multi-Tenant environment, tenants are permitted to add custom attributes to tables, if the GA has created an extension table for that object.
Example of a tenant-specific attribute:
If the tenant adds this custom attribute to the list tab, they may encounter a SQL error when attempting to query records.
Example of this error:
Resolving The Problem
This can be corrected by updating the field on the list tab to refer to the extension table column name, instead of the tenant attribute name.
In Application Designer, open the Properties dialog window for the List Tab Table Column of the tenant's new attribute.
For example, if the tenant has an added an attribute to WORKORDER named 'TEST', which maps to WORKORDER_EXT.ALN1, the attribute should be updated from 'TEST' to 'WORKORDER_EXT.ALN1' for the list tab Table Column Properties.
If the tenant wishes to have a lookup on this field, further steps are required. Instead of defining a domain on the attribute, the tenant must modify the LOOKSUP.XML.
In Application Designer, select action 'Export System XML' and choose 'LOOKUPS.XML'.
Open the exported LOOKUPS.XML, and add a new table section. This section must define the mboname and whereclause to be used for the valuelist lookup, as well as the attributes to be displayed.
For example, from LOOKUPS.XML: (In this example, an ALNDomain named 'WOTEST' is used for the lookup).
<table id="wotest" inputmode="readonly" selectmode="single" mboname="ALNDOMAIN" whereclause="domainid='WOTEST'">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="wotest_lookup_tablebody">
<tablecol dataattribute="value" id="wotest_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="description" id="wotest_lookup_tablebody_col_2" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
</tablebody>
</table>
Notice that a mboname and whereclause were added to the table body XML.
The mboname must refer to the appropriate type of domain object (ALNDOMAIN, NUMERICDOMAIN, NUMRANGEDOMAIN, TABLEDOMAIN).
If the domain type is ALNDOMAIN, NUMERICDOMAIN, or NUMRANGEDOMAIN, the whereclause must uniquely identify it.
If the domain type is TABLEDOMAIN, the whereclause must contain the TABLEDOMAIN’s List Where Clause.
- Save and import that updated XML.
- In Application Designer, and modify the lookup field for the desired attribute with a value of this lookup table.
In this example, the attribute WORKORDER_EXT.ALN1 in the WOTRACK application list tab was modified to have a lookup against the WOTEST table from LOOKUPS.XML.
- Save the updated Application definition, and log out. Upon the next login, the lookup will now function as expected. Test1, Test2, and Test3 are values in the WOTEST domain in this example:
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg22013591