[ http://issues.apache.org/jira/browse/OFBIZ-238?page=comments#action_12445141 ] Iain Fogg commented on OFBIZ-238: ---------------------------------
Jacques, Came across this one myself but the context is a little different (I agree with the Jira BTW). My use case is a little different and I have a patch that addresses it. Scenario.... Product_id A has multiple alternative good_ids that map to it. This is extremely common in the book industry (eg, a 10- or 13-digit ISBN number). However, publishers often also supply an EAN which most of the time turns out to be the same as the 13-digit ISBN. If both of these IDs are in the product database then the POS lookup will retrieve multiple records in the GoodIdentificationAndProduct view with the same product_id. The simple solution is to check whether the multiple rows returned actually refer to the same product, and if so return is. I'll try to attach a patch to this issue (I haven't done that before). BTW, this patch works whether the product lookup returns 0, 1, or many records, so is a benign change. I have not addressed the actual JIRA issue (providing a selection screen), but treat this as a precursor because you wouldn't want duplicate records to appear in this selection screen anyway :-) > POS Multiple bar code product match > ----------------------------------- > > Key: OFBIZ-238 > URL: http://issues.apache.org/jira/browse/OFBIZ-238 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: pos > Reporter: Jacques Le Roux > Assigned To: Jacques Le Roux > > If one or more product ids are found when searching for a SKU the system > presently falls out with a "Product Not Found" error dialog. > The improvement here is to add a new dialog that will present the search > results to the user in a list for selection into the basket or to cancel if > desired. > The list should contain product code, name and price. Each row should have > enough height to ensure easy and accurate selection with a touch screen and > the list should be scrollable when necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
