Share
Report
335Extender lookup created to allow selection of a given customer from customer master (RM00101) and that lookup attached to a field on an Extender form used to enter RMA information. For whatever reason, a given customer out of around 1,000 was no longer in the lookup list, and previous records entered into this form, when pulled up, that had that same customer selected now displayed the message 'Lookup value not found'.
I discovered that Extender lookups store their values in and read from EXT00900 (as opposed to reading directly from the table upon which the lookup is being performed). This means all customer values are stored in EXT00900 as opposed to reading directly from RM00101. When I compared EXT00900 to RM00101 where EXT00900.Extender_Lookup_ID = 'CUSTLOOKUP', I found one less record in EXT00900 compared to RM00101. My question is why would Extender have removed a record from the lookup values table when that customer was clearly still a valid customer in GP in the RM00101 table? Has anyone seen this before? I did notice the MODIFDT in RM00101 had a value of 2 days prior to today's date, and a misc note was attached to this customer related to preferred shipping so my guess is when this customer was modified Extender removed this customer from the lookup values table, but I have no idea why. I've been unable to reproduce when going through the same steps that the user did when the customer was modified 2 days ago.
I went ahead and just manually inserted the missing record to EXT00900, and that's "resolved" the issue, but obviously I'm slightly concerned with that solution; if anything, I have no idea why that occurred in the first place and therefore not sure whether this could occur again in the future. Any help/insight would be appreciated.
*This post is locked for comments
All responses (
Answers (
