Info Window should use key and display columns setting from lookup

Sorry - it was not my intention to upset you

The reversal without discussion is because a major iDempiere functionality was broken (barcode scanner on product field), as we have systems using release-11 in production I reverted the commit as an emergency.

It should be the test case above where the identifier setting is different between info window and table (or reference value key ?).

Since this have been revert without any discussion, I’m not going to spend any more time looking at this. If you want, you can just close the ticket.

Hi - if this was solving a problem or a bug, I can take a look if you want.

If not solving a bug, maybe we can close the ticket?

Reported by Vincent Paruh on forums:
https://groups.google.com/g/idempiere/c/dTvs5ho2-Bw/m/Dcf_cGL9BAAJ

when I typed in search key in the Business Partner field and press enter ( or click somewhere else), the field does not find the BP, even though there's only one BP with that search key

I didn't notice the impact of this, but is a big step back on functionality. Apart from the issue mentioned by Vincent, it broke the usage of EAN for product fields, that means it breaks the usage of barcode scanners - of course it can be configured making the EAN an identifier of the product, but that's not good for the rest of windows where products are displayed.

I think the old way was very handy as it was easy to configure the order of parameters on the info window to allow the usage as search keys.

I'm going to revert the change and then we can review if there is something broken to fix (f.e. with the mentioned test case).

Regards,

Carlos Ruiz