I am using the new barcode scan feature available in FM GO 13 and I can't seem to get it to work. My script step is:

 

Insert from Device [Equipment Log::zBarcode; Type: Bar Code; Camera: Back; Resolution: Full]

 

I have all the barcode types enabled and the barcode that I am testing with is Code39. The error that I get is "Specified field has inappropriate filed type".

 

Equipment Log::zBarcode is a Text field. I tried changing it to a Container field to see if that would make a difference, but no luck. Does anyone have any ideas?

 

Thanks,

Ryan

I have seen this error before, but I never got to the bottom of it. Scanning into a text field can work fine, and is usually what I recommend. I don't remember exactly what the fix was, but it could have involved making another field set-up the same way and deleting the original field that wasn't working, or running the script on a different layout, or some such. Are you willing and able to post the file here for the rest of us to try things on?

It is a really large file. I will try to create another trimmed down version. 

I noticed this error when attempting to insert to a global field

It would be good to discover the underlying reason.

I did see that insert into a portal row gave the error too.

I tried in a global field first. I believe that I also tried in non-global field. Both produced the same error.

I may have figured out a work around.

 

Instead of storing the scanned bar code in a global field, I create a table with only one text field and one record to store the bar code. In that way, filemaker do not complain. 

 

However, when I turn error capture on, I still get error 413 "Specified field has inappropriate field type". For some unknown reason, a normal field works but a field that has global storage don't.

 

Update: Please read the following two posts.

It turns out the the work around is not reliable. After I've created one more table in my database, the scanning of barcode failed again, with the same error.

 

Update: the reason why creating a new table works is that, FileMaker automatically create a layout with the field defined. Since the layout is not needed, I delete the layout. As a result, the "work around" fail. 

 

The actual solution is to define the field that going to hold the barcode on the layout concerned. 

I've nailed down the cause. For Input From Device to work properly, the target field should appear on the layout. Adding the field on the layout, the error code will be 0. I have not tried for global storage, but at least it works for a non-global field.

Thanks for coming back to update.  This helped me with my new inventory database!

Just a followup from me as well: your solution of having the field on my layout (although in my case hidden) worked. Thanks!