Barcode Scanner Input - Variable Length

[Mark_Flaugh]

I have been using the Barcode Scanner Input on a Perspective view for almost 18 months with good success. It is reading a scanned barcode and send the value to a Transaction Group to grab information. I am using a regex code ([0-9]{7})$ to grab the 7 numeric digits of the scan.

However, now we are starting to have a mix of 7 and 8 digit barcodes. I have attempted to modify the regex code like this - ([0-9]{7,8})$ and ([0-9]{7,})$ - and it only returns 7 digits no matter what the length of the code. I am afraid that if I change to this - ([0-9]{8})$ - 7 digit barcodes will not work.

View the reader output in Notepad, I see that it appears to be appending an ENTER or new line suffix. There is no prefix. I thought that I could use that in the suffix field and get rid of the regex code but that does not appear to be working. I very well could be entering the format of suffix wrong. Because it is looking for a string, I created a simple expression binding for CHR(10). Is a prefix character required?

Any help would be greatly appreciated.

[pturmel]

You should be able to use a suffix character that the browser won't automatically interpret. Perhaps the Pipe | character.

(Variable length codes typically need unambiguous suffix codes when using keyboard wedge input modes. Which is all Perspective can do when the scan is not built into a mobile device.)

[Felipe_CRM]

@Mark_Flaugh

CHR(10).

I remember Perspective handles "Enter" a little differently from what one might expect, try \n:

Perspective Key Event Regex New Line

This is expected behavior, all. At the core of the regex match is the data that we receive from a JavaScript KeyboardEvent because this executes in the scope of the browser. We’re assembling a character sequence to match against from an input source (your barcode scanner) that creates KeyboardEvents. A “new line” character shows up as a key press for the “Enter” key. https://keycode.info/ is a pretty decent way to test what KeyboardEvent data your sequence would produce. It tests a key at a…

But honestly it would be better if you can change the scanner to output a different suffix as per Phil, to avoid keyboard getting picked up as a scan.