Hello Pavan
Go for the existing lookupid: astspecattribute as your lookup for the field
<table id="astspecattribute" inputmode="readonly" selectmode="single">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="astspecattribute_lookup_tablebody">
<tablecol dataattribute="assetattrid" id="astspecattribute_lookup_tablebody_col_5" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="description" id="astspecattribute_lookup_tablebody_col_6" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
</tablebody>
</table>
See how that goes
------------------------------
Niv Geo
------------------------------
Original Message:
Sent: 11-05-2025 01:26
From: Pavan Uppalanchu
Subject: Help Needed - "Invalid Binding" Error for Status Field in Work Order Lookup List After Domain Configuration
@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.
<table id="eg_assetspecattrid" inputmode="readonly" selectmode="single">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="eg_assetspecattrid_lookup_tablebody">
<tablecol dataattribute="assetattrid" id="eg_assetspecattrid_lookup_tablebody_col_1" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="siteid" id="eg_assetspecattrid_lookup_tablebody_col_2" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
</tablebody>
</table>

------------------------------
Pavan Uppalanchu
IBM
------------------------------
Original Message:
Sent: 09-15-2025 22:17
From: Craig Kokay
Subject: Help Needed - "Invalid Binding" Error for Status Field in Work Order Lookup List After Domain Configuration
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
------------------------------
Craig Kokay
Principal Consultant
COSOL
email: craig.kokay@cosol.global
#IBMChampion