Forum Discussion
MichaelTamoush
4 years agoQrew Captain
If you can run an edit API call, and an Add API call from a scan, then I think I have a way. But I am not sure how it would work because an add api call allows you to reference fields from the table you launch from, and I do not know how the system could know what table you are launching from when using the barcode scan.
Let me know if you find out if it's possible and I'll type out the rest of my idea.
------------------------------
Mike Tamoush
------------------------------
BenKrieger
4 years agoQrew Member
It is possible to run API calls using a QR code and that is the direction I have been working to implement. For instance this code generates a QR code using the "Create Child Record" button that quickbase creates automatically when it sets up a relationship:
"<img src=https://chart.googleapis.com/chart?chs=200x200&cht=qr&chl="&URLEncode([Add Selection])&">"
The code for that [Add Selection] is the API_GenAddRecordForm that the button uses. The way I have it set up is I have a pieces table, a pallet table, and a join table that allows me to relate the parts to the pallets. The QR scan creates a record in the join table associated to the pallet and opens it in edit mode so that a piece can be scanned and the record can be saved.
The problem with this approach is that it requires the user to scan the pallet code, select the "part #" field, scan a part code, save the record, and then repeat this process for every part that the user want to put on a pallet. Ideally I image that a user would scan a pallet, scan all of the pieces that they want on that pallet, and then select a save button.
------------------------------
Ben Krieger
------------------------------
"<img src=https://chart.googleapis.com/chart?chs=200x200&cht=qr&chl="&URLEncode([Add Selection])&">"
The code for that [Add Selection] is the API_GenAddRecordForm that the button uses. The way I have it set up is I have a pieces table, a pallet table, and a join table that allows me to relate the parts to the pallets. The QR scan creates a record in the join table associated to the pallet and opens it in edit mode so that a piece can be scanned and the record can be saved.
The problem with this approach is that it requires the user to scan the pallet code, select the "part #" field, scan a part code, save the record, and then repeat this process for every part that the user want to put on a pallet. Ideally I image that a user would scan a pallet, scan all of the pieces that they want on that pallet, and then select a save button.
------------------------------
Ben Krieger
------------------------------