We would like to allow service request submitters to choose the crew in the SR application. I've added the custom attribute to the TICKET object, added a field on the SR app screen, and added the attributes to the TICKET2WO cross-domain; this all seems to work to generate a WO from the SR with the desired crew assigned.

When I add the AMCREW lookup to the field in the SR app, the lookup appears with all columns showing "Invalid Binding." I've tried adding a relationship between TICKET and AMCREW in the TICKET object, and adding MAXLOOKUPMAP entries in both SR and TICKET objects. Is there anything else I can try? Thanks.

Invalid Binding means your attribute on ticket (and the related views like SR) doesn't have a table domain, retrieve list automation script, etc. The MAXLOOKUPMAP tells the product what attributes to pull back from the object but doesn't handle the mapping entirely. If you add a retrieve list automation script you can fix the invalid binding and implement what you're doing in the MAXLOOKUPMAP. If you want to continue with the MAXLOOKUPMAP (remembering to restart the server if you add entries), you can just add a table domain to the attribute.

For the automation script approach, we have some documentation here: https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/attributescripts/attributelaunch

But there are other ways to do it that are more appropriate for your situation. Sharptree did a great blog post on it here: https://www.sharptree.io/blog/2022/2022-02-14-script-retrieve-list/ . Using the relationObject, relationWhere, listWhere, etc. approach is typically the default I use. 

Thanks very much. This is very helpful; it got me where I needed to go and gave me some more to learn. I went with the table domain because it was quickest, but I'll be experimenting with the other techniques.