Notifications
Announcements
No record found.
Hi @Sagar121, thanks for your reply.
I’ve tried both approaches:
1) Without custom code (using table relation / EDT lookup) I created a relation between my header table and the custom table, and also configured the EDT and field groups (Overview / AutoLookup). In this case, the lookup works, but it only shows one column (the key field) and does not display additional fields like the name.
2) With custom code (SysTableLookup in form datasource) I also implemented a custom lookup using SysTableLookup in the form datasource fieldLookup() method, for example: SysTableLookup sysTableLookup = SysTableLookup::newParameters(tableNum(MyCustomTable), _formControl);
SysTableLookup
fieldLookup()
The lookup is triggered correctly, but the dropdown still behaves like a single-column lookup, and the additional field does not appear as expected.
So my question is:
Is it required to use a lookup form (instead of a dropdown) to properly support multi-column lookup?
Or is there any additional setup required (EDT, field group, control properties, or event cancellation) to make a multi-column lookup work correctly for a custom table?
Thanks in advance for your help.
Thanks, Layan Jweihan Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 551 Most Valuable Professional
André Arnaud de Cal... 450 Super User 2025 Season 2
BillurSamdancioglu 278 Most Valuable Professional