To Test: - create an item with barcode "123 " - enter barcode "123" in either batch item deletion or batch item modification - receive a "barcode not found error for "123" - note that your item with barcode "123 " does appear in the list for deletion/modification similar to bug 22799 for case sensitivity in these tools.
Hi Andrew, The patch I attached on bug 23800 fixes this issue.
Marking as blocked until bug 23254 is resolved (and see if it fixes the issue from this bug report).
This is the confusing screen: https://snipboard.io/b6nxN8.jpg
I just signed off bug 23800. While testing that, I also tested this. I created items with the barcodes "123 " and " 123" Without the patch for bug 23800, putting "123" in my list of barcode for batch item mod found the item with barcode "123 " but gave an erroneous barcode not found error. It did not find " 123" at all. With the patch and the same two barcodes in the system, I entered "123" into item batch mod and it didn't find anything. Then I entered " 123" and "123 " into item batch mod and they didn't find anything either. So the patch from 23800 has changed this behavior, but doesn't seem to have fixed it.
(In reply to Andrew Fuerste-Henry from comment #4) > I just signed off bug 23800. While testing that, I also tested this. > > I created items with the barcodes "123 " and " 123" > Without the patch for bug 23800, putting "123" in my list of barcode for > batch item mod found the item with barcode "123 " but gave an erroneous > barcode not found error. It did not find " 123" at all. > With the patch and the same two barcodes in the system, I entered "123" into > item batch mod and it didn't find anything. Then I entered " 123" and "123 " > into item batch mod and they didn't find anything either. > So the patch from 23800 has changed this behavior, but doesn't seem to have > fixed it. Yes, and it cannot work, it is the expected behavior :) But, since bug 22996 you can define the separator, so try to remove \s from the separator list and try again, it should work.