Skip to main content

I have the Scan IT app on my iPhone when I am in Register Arrivals and go to scan the Inventory Barcode label (produced from Inventory Locations) instead of it being the actual IFS Inventory Location it’s just a number like 11127277.  Any ideas how to fix this please? Thanks

 

You are sure your are not talking about the Inventory Part Barcode like the data item BARCODE_ID, that is a barcode to identify a part its just a number ID that will identify everything you can see in page Inventory Part Barcode Analysis .

From what I can quickly see the inventory location barcode is just the LOCATION_NO in the barcode. If the value you get is not the expected LOCATION_NO maybe your device cannot support the BARCODE used in that label. Seems to be CODE 39 in the CORE report, but it can be changed to another standard also, so not sure which one you have in your case.


Thanks for the reply yes I’m sure see below the location barcode label.

 

 


Then I guess the device or in your case iPhone running Scan-It which uses the free ZXing plugin for camera scanning have issues with this barcode for some reason. It probably works better if using a proper scanner instead of camera or maybe it could be worth changing the BARCODE type on the report to something else than CODE 39 in this case.

 

You can try online ZXing test pages like https://zxing.org/w/decode.jspx to try out what ZXing supports.

I tried both the CORE barcode and your picture and ZXing didn’t seem to be able identify the barcode properly, I’m not sure why. It is supposed to support Code 39.

“No barcode was found in this image. Either it did not contain a barcode, or did not contain one in a supported format, or the software was simply unable to find it. Go "Back" in your browser and try another image.”

 


Then I guess it is the device or in your case your iPhone using Scan-It that uses the 3d party plugin ZXing to handle scanning with a camera, that have issues scanning this barcode.

You can google for ZXing and find online testing pages where you can upload your barcode picture to see if the ZXing software can scan the barcode or not. 

I tried both with the CORE barcode and your barcode and ZXing didn’t seem to be able to identify the barcode properly, I’m not sure why since its suppose to support Code 39. So maybe that is the reason why you are not getting the proper value from the barcode.

“No barcode was found in this image. Either it did not contain a barcode, or did not contain one in a supported format, or the software was simply unable to find it. Go "Back" in your browser and try another image.”

I would guess it would work better with using a proper scanner instead or changing the barcode type on the report to something else that ZXing supports.


Thanks again where to you establish the code and see the code report?


If you are talking about the barcode type it can be seen and changed in the report layout file for this report, you have the code type to the right of the screen where you can change the barcode type and other settings:

 

If there is an issue with ZXing one alternative could be to instead use the other plugin that was introduced back in apps10, which is Scandit, but then you have to get a license to use Scandit and save the license key inside IFS applications (where depends on which version you are using, apps10 or cloud). If IFS Scan-it finds a valid scandit key saved it will use Scandit instead of ZXing when using the camera to scan.

Scandit was introduced as camera scanning plugin since it handles some barcode types better than ZXing like GS1-barcodes and it worked better in darker environments or something like that.

 

 


thanks I’ve now managed to get it working by increasing the size of the barcode label!! it now scans the actual location fine.


Ok that was interesting to hear, since this barcode is actually larger then the one we have in Inventory Part Barcode and I have not heard about any issues scanning that one before. But yeah maybe ZXing like larger barcodes than regular scanners require.

What I remember when the inventory location report was built was that we mostly tested it with a regular scanner, like an USB scanner, I don’t think it was tested with any camera plugin/tools like that back then.


Reply