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.
Hi everyone,
I’ve tested this scenario and can confirm that the behavior is related to the Field Group configuration.
In my case, the lookup was showing only one column when using SysTableLookup, even though multiple fields were added via addLookupField().
addLookupField()
The solution was to configure the table Field Group = AutoLookup properly.
Once I added all required fields (e.g. Code, Name, Description) into the table’s AutoLookup field group, the lookup started displaying multiple columns as expected — without needing to switch to a lookup form.
So in summary:
SysTableLookup does support multiple columns
The table must have the desired fields included in Field Group: AutoLookup
A lookup form is not required for this use case
After updating the AutoLookup field group, everything worked correctly.
Hope this helps.
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 659
André Arnaud de Cal... 465 Super User 2026 Season 1
Syed Haris Shah 304 Super User 2026 Season 1