We will be using use a bar code scanner to enter an item UPC into a field. How can we use the entered UPC to populate other fields with information from another table?

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • Answered
We have a production application that we use to track productions runs of products. Currently when entering a production run the user picks the item to be produced from a drop down list linked to an item list table. What we want to be able to do is scan the UPC on an item to populate the UPC field and have QuickBase reach out to the item list table to retrieve the description and other information.

Any suggestions?
Photo of Douglas0507

Douglas0507

  • 0 Points

Posted 2 years ago

  • 0
  • 1
Photo of QuickBasePros_IDS

QuickBasePros_IDS, Champion

  • 3,028 Points 3k badge 2x thumb
Trinity Integrated Solutions offer Barcode Scanning integration.  Not sure if your scenario fits their tool; but it's worth finding out.
Photo of Douglas0507

Douglas0507

  • 0 Points
Looked at that already.  Way more than we need.  Just need to know how to use QuickBase native functions to retrieve information from another table based on the scanned bar code input.
Photo of QuickBasePros_IDS

QuickBasePros_IDS, Champion

  • 3,028 Points 3k badge 2x thumb
Sounds like your UPC value needs to match a key-field value in another table to auto-connect the two together.  So when you scan the UPC that you have QuickBase populate a [Related Reference] field value with the same UPC value which matches another table of records where the Key Field is the UPC value.
Photo of Douglas0507

Douglas0507

  • 0 Points
When you say [Related Reference] field do you mean having the Input Type set to From Another Field?  Once I set the relationship between the two tables using the the common UPC field, how to I populate other fields in the target table with data from the reference table based on that relationship?
Photo of QuickBasePros_IDS

QuickBasePros_IDS, Champion

  • 3,028 Points 3k badge 2x thumb
Table A is where your data is entered.  Table B is a table where [UPC] is the Key Field.  You build your relationship as you normally do; but then you change [Related UPC] field from a text-field to a formula-text field.  You then reference the [Table A UPC Entry Field] as the formula value in your [Related UPC].  This will auto-connect your two tables together.

Caveat - when joining tables like this, you lose the Summary Field functionality of the relationship on the Parent side (Table B).  

The alternative would be to use a Webhook most likely to force-populate the [Related UPC] field value with the same value in [Table A UPC Entry Field] so that it populates automatically without being a formula-text join.  This way you keep your summary field functionality because the [Related UPC] is still a text-entry field, but you're using a Webhook to populate it.