Maximo Open Forum

Hi everyone, I am practicing Table domain with a scenario

I recently added a new domain (testtable table domain) to the status attribute in the Work Order object.

After this, the Work Order tab is working fine, 

but when I go to the Work Order Tracking list (lookup) page, I am seeing an "Invalid Binding" error for the status column.

Here is what I have done in the lookup configuration:

• In lookup.xml, I added the status  and location   column inside the <table> tag with the proper dataattribute="status" and dataattribute="location".

  <table id="workorder" inputmode="readonly" selectmode="single">
  <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="workorder_lookup_tablebody">
  <tablecol dataattribute="location" id="workorder_lookup_tablebody_col_6" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  <tablecol dataattribute="status" id="workorder_lookup_tablebody_col_7" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  </tablebody>
  </table>

• also  I have added workorder(tableid) in lookup section for list and workorder tab status field.
• But the main Work Order tab works perfectly, but the list lookup shows "Invalid Binding" instead of status values.
• Since nothing else worked, in Database Configuration for the WORKORDER object, under Lookup Map, I mapped the src and targetkey with the value STATUS, and set the Source Object as WORKORDER. and restart the server

Could anyone please help me understand what might be missing or misconfigured that causes the list lookup to fail with this error? Is there something specific I need to do for domains or attribute bindings in lookup mappings for the list page?

Hi Jack

I have a disconnect. 

• You have created a new table domain that should only list work orders that have a status of APPR.
• This has then been registered against the WORKORDER.STATUS attribute
• The work order detail screenshot is 'supposedly' showing the list of matching work orders, but only displays the WORKORDER.LOCATION and WORKORDER.STATUS attributes
• The work order list screenshot shows a list of workorder, but an invalid binding (assuming it should be WORKORDER.WONUM) and the WORKORDER.DESCRIPTION

The reason I'm not following is that none of it matches. The two lookups are totally different.  The lookup XML snippet does not makes sense.

The domain is fine, but how is it supposed to be used?  Please detail the design.  We don't know why you're showing the detail vs the list.  We don't know from where you're launching the lookup on either tab.

BTW: The domain should be registered to the field from which you will have a lookup configured from the UI.  The Lookup Map is only needed where the source field is the same as the target field i.e. source = PERSONID target=SUPERVISOR

Hi everyone, I am practicing Table domain with a scenario

I recently added a new domain (testtable table domain) to the status attribute in the Work Order object.

After this, the Work Order tab is working fine, 

but when I go to the Work Order Tracking list (lookup) page, I am seeing an "Invalid Binding" error for the status column.

Here is what I have done in the lookup configuration:

• In lookup.xml, I added the status  and location   column inside the <table> tag with the proper dataattribute="status" and dataattribute="location".

  <table id="workorder" inputmode="readonly" selectmode="single">
  <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="workorder_lookup_tablebody">
  <tablecol dataattribute="location" id="workorder_lookup_tablebody_col_6" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  <tablecol dataattribute="status" id="workorder_lookup_tablebody_col_7" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  </tablebody>
  </table>

• also  I have added workorder(tableid) in lookup section for list and workorder tab status field.
• But the main Work Order tab works perfectly, but the list lookup shows "Invalid Binding" instead of status values.
• Since nothing else worked, in Database Configuration for the WORKORDER object, under Lookup Map, I mapped the src and targetkey with the value STATUS, and set the Source Object as WORKORDER. and restart the server

Could anyone please help me understand what might be missing or misconfigured that causes the list lookup to fail with this error? Is there something specific I need to do for domains or attribute bindings in lookup mappings for the list page?

 @craig.kokay@cosol.global I do have similar issue in Advance search.  In Work order application, In Advance search,I have added ASSET.ASSETSPEC.ASSETATTRID Field. On this field, I have an automation script witten on retrieve list [Attribute Launch Point - ASSETSPEC.ASSETATTRID] and using one custom table domain, and modifying listWhereClause. 

The table domain is a view of ASSETSPEC Table. 

<textbox dataattribute="ASSET.ASSETSPEC.ASSETATTRID" id="eg_assetattid_col" lookup="eg_assetspecattrid"/>

New lookup has attributes from View. 

Hi Jack

I have a disconnect. 

• You have created a new table domain that should only list work orders that have a status of APPR.
• This has then been registered against the WORKORDER.STATUS attribute
• The work order detail screenshot is 'supposedly' showing the list of matching work orders, but only displays the WORKORDER.LOCATION and WORKORDER.STATUS attributes
• The work order list screenshot shows a list of workorder, but an invalid binding (assuming it should be WORKORDER.WONUM) and the WORKORDER.DESCRIPTION

The reason I'm not following is that none of it matches. The two lookups are totally different.  The lookup XML snippet does not makes sense.

The domain is fine, but how is it supposed to be used?  Please detail the design.  We don't know why you're showing the detail vs the list.  We don't know from where you're launching the lookup on either tab.

BTW: The domain should be registered to the field from which you will have a lookup configured from the UI.  The Lookup Map is only needed where the source field is the same as the target field i.e. source = PERSONID target=SUPERVISOR

Hi everyone, I am practicing Table domain with a scenario

I recently added a new domain (testtable table domain) to the status attribute in the Work Order object.

After this, the Work Order tab is working fine, 

but when I go to the Work Order Tracking list (lookup) page, I am seeing an "Invalid Binding" error for the status column.

Here is what I have done in the lookup configuration:

• In lookup.xml, I added the status  and location   column inside the <table> tag with the proper dataattribute="status" and dataattribute="location".

  <table id="workorder" inputmode="readonly" selectmode="single">
  <tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="workorder_lookup_tablebody">
  <tablecol dataattribute="location" id="workorder_lookup_tablebody_col_6" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  <tablecol dataattribute="status" id="workorder_lookup_tablebody_col_7" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
  </tablebody>
  </table>

• also  I have added workorder(tableid) in lookup section for list and workorder tab status field.
• But the main Work Order tab works perfectly, but the list lookup shows "Invalid Binding" instead of status values.
• Since nothing else worked, in Database Configuration for the WORKORDER object, under Lookup Map, I mapped the src and targetkey with the value STATUS, and set the Source Object as WORKORDER. and restart the server

Could anyone please help me understand what might be missing or misconfigured that causes the list lookup to fail with this error? Is there something specific I need to do for domains or attribute bindings in lookup mappings for the list page?