I have 2 tables, Batches and Items. Each item has a barcode on it that I plan on scanning to make entry faster. All the item records are already in that table. I need to create batches and would like to do something like clicking on a button for Add to Batch and have a find performed based on the barcode scanned. Then I would like the item record to show up in the container field that I have setup[ on the batches layout.
I'm having trouble using the find command inside the container.
barcode scans can result in numbers placed in fields and not images to containers. So scanning a barcode to find a product, and then adding one of the results to a "batch" would look like:
Part 1 - scan to find ( "find product" button )
Enter Find Mode [ pause: off ]
Go To Layout [ Products Search Results ]
Insert From Device [ barcode ; items::barcodenumber ]
Perform Find
Part 2 - tag a record for batch ( "add to batch" button )
Set Field [ products::tempBatch ; 1 ]
Part 3 - Do something with batch
Enter Find Mode
Set Field [ products::tempBatch ; 1 ]
Perform Find
# Do Something to all the records
# Reset batch
Replace Field Contents [ products::tempBatch ; "" ] [ no dialog ]
If you need to account for multiple users doing batches at the same time, use a $$session variable with UUID instead:
Part 1
Set Variable [ $$session ; Get(UUID) ]
Enter Find Mode [ pause: off ]Go To Layout [ Products Search Results ]
Insert From Device [ barcode ; items::barcodenumber ]
Perform Find
Part 2
Set Field [ products::tempBatch ; List( products::tempbatch ; $$session ) ]
Part 3
Enter Find Mode
Set Field [ products::tempBatch ; 1 ]
Perform Find
# Do Something to all the records
# Reset batch
Replace Field Contents [ products::tempBatch ; substitute( products::tempBatch ; $$session ; "" ] [ no dialog ]
Set Variable [ $$session ; "" ]
DOH! I'm so sorry, I meant a portal not a container.
Here's a screengrab of the layout I envisioned.
Are you finding records listed in the portal? better to find records on a layout based on the portal's table. But I likely wouldn't perform a find at all. I'd use a relationship or Possibly ExecuteSQL to get the scanned item's ID and enter that ID into the Records for a given Batch. This to me works better with three tables, not two:
Batches---<Batch_Item>----Items (----< means "one to many")
Batches::__pkBatchID = Batch_Item::_fkBatchID
Items::__pkItemsID = Batch_Item::_fkItemID
So the scanning process uses the bar code data to get an Item ID to use to create a new record in Batch_Item in order to set up your Batch.
And you don't generally need to worry about sessions with this approach as ordinary record locking will keep users out of each other's hair as each works from the context of a different record in Batches.
A relationship for getting Item ID's (if the bar code doesn't encode the item ID) would look like this:
Batches::globalScanField = Items|Barcodes::BarcodeField
You can then scan into the globalScanField and refer to Items|BarcodeField::__pkItemID in order to get the ID needed to add a new record to Batch_ITem.
What container would that be?
Scaning a barcode should be used to put the value of the barcode as text into a text field. You'd then use that text produced by the scan to search for a matching text field with the same value.
No container used in that. (So you might store an image of the barcode into a container, but you wouldn't use it for searching.)