TABLE OF CONTENTS
You can quickly and easily add the ability to scan common barcodes and QR codes to any Form screen via the Barcode field type. This field provides the user with a "Scan" button that launches the device camera to perform barcode capture.
This is the name of the field that should be referenced in any form logic or API calls. Users will not see this name on the form.

Data names cannot contain spaces or any special characters other than an underscore and must begin with a letter. They are case-sensitive and must be referred to precisely whenever they are referenced.
This is the name of the field that will be displayed to users on the app. This property is completely optional; while a field must contain a data name, a field title is optional.

The text color may be chosen with a hex code. The text may be also formatted as Bold or Italic and given a relative size -- Small, Medium (the default) or Large.
This optional field can be used to show secondary information to the user in the app. Consider using this to provide instruction or clarification to the user as they fill out the field.

Formatting options for this property are the same as those given available for the Title Text property.
This drop-down determines the action taken when the barcode is successfully scanned. So, for example, you could launch a new Screen or you could navigate to another page in a Form when the scan occurs. This opens up many new scenarios to make your apps even more dynamic. See our Form Recipes section for Barcode-specific articles - e.g., how to repeatedly scan barcodes / QR codes in your Forms.




The geocoded coordinate result (if any) is populated into the field, with the result being "lat lon" - e.g., -13.3823724 153.9832837. The result will not be visible to the user unless the "Display Result to User" property is enabled (see Advanced Options further in this article).




For Form targets, you can preset target fields with "dataname:value," pipe-separated.
E.g., field1:{{city}}|field4:hello
For Listing and Mapping screen targets, you can pass in a formula for filtering the target rows. Use {{target[column]}} for target columns.
E.g., {{target[3]}} >= {{price}}
For Detail and Task Details targets, pass the identifier of the target data row or Task. For data rows, the identifier must match the first column's value.
E.g., {{mychoice}}
Once the user has submitted or exited the target screen, they will be returned to the original form with their progress retained.





This drop-down determines how this field is shown on the screen.



The color chosen in the hex code field here will apply to the field. The Transparent box can also be chosen instead for making this transparent instead of a solid color.

This checkbox option will embed the barcode scanner view directly into the page instead of showing a Scan button (which is the default). Rather than clicking a button to initiate the scan in a full-sized shot, a small camera window will appear inline within the field.
Note that only one inline barcode is supported per page or table.
Not Inline (Default) | Show Inline |
|
|
Checking this box will enforce validation against this field to make the field required, disallowing the user from progressing to the next page or submitting the form if it is left blank. If the user tries, they will be prompted with an error to return to the field and enter a value. When this validation occurs is determined by the "Validation Property" chosen on the page level; please see this article for more detail on this.

This property can also be made conditional based on a formula. To enable this, click "add condition" below the checkbox and enter a formula into the field that populates. The formula serves as the basic of the required-ness of this field.

Please see this article for more information on conditionally-required fields.
The contents of this field will determine whether the field will be visible to the user. For more detail on visibility rules, please see this article.

This property is used to define a calculation/formula that will populate the field's value. Often this is used in conjunction with the "Read Only" property (see below) so that the field will calculate and display to the user without the possibility of manual edits. This article is recommended as a starting point for more reading on this.

Please see this article for details on the relationship between Default Value and Dynamic Value.
If this checkbox is checked, users will be able to see the contents of the field but will be unable to make edits.

Similar to the Required property, the Read Only property also includes the ability to define a conditional formula determining whether the read-only property is enabled. Click "add condition" to define such a formula.

Add your own custom formula to this property for validating text entered into this field by users. The formula is only applied when the field has an answer. Enforcement will be done according to the "Validation Property" chosen on the page level; please see this articlefor more detail on this.

The contents of this property will serve as a custom message to display to the user if their input fails validation.

The value entered in this property serves as the initial value of the field prior to manual input. Please see this article for details on the relationship between Default Value and Dynamic Value.

This property allows for the binding of the contents of the field to a data source that is linked to either a choices field or data field on the form. For details, please see the screenshot below:

Data Source binding allows you to create forms that can load data from, and update data to, any given data source. This opens up amazing opportunities to have dynamic data that is updated on the move (e.g., adding contacts or clients). For more information, please see this article.
Global Values are a local key/value store that is available to any Screen on the app. Use this property to allow the user to view and save defaults for use across the app (e.g., a default project or customer). Please see this article for more information.

By default, every field is displayed on Form entries in the Data area, and is included in non-templated exports (e.g., generic pdf, CSV, spreadsheet, database connectors). Use this property to prevent this field from showing on all such display and exports.

Indicates that data captured in this field may contain personal or sensitive data, which in turn can be anonymized when exported from the platform when then the "Anonymize Personal Data" option is checked on a form connector. Please see this article for more on this.
NOTE: Use of this option does not grant or imply additional security, protection and privacy of data.

This multi-select field provides the option to improve accuracy by restricting scans to match specific formats only. By default, the barcode field will attempt to match all supported barcode formats; in some cases, this can result in inaccurate scans due to unrelated formats being matched.
The following commonly-used formats are supported and are available for individual selection here; select more than one by holding the Control key on Windows or the Command key on Mac:
1D Retail/Product Formats
1D Industrial Formats
2D Formats
Compared to a dedicated barcode scanner peripheral, scanning with a phone or tablet camera will always be a little slower. We provide two key options on the Barcode field that can help you improve the speed and accuracy of scans.
Bulk Scanning (External Barcode Scanners)
Our platform supports external barcode scanners, which is seen as more efficient than utilizing a mobile phone or tablet. The built-in bulk scanning function within our platform allows for the scanning of barcodes at an increased speed, simply set the Barcode Field's Scan Device property to External Barcode Reader.
Successfully tested on a 45,223-row database combined with a Choices Field and a simplified filter formula.
Example
A form build using a repeatable table that allows for a new repeat to be captured after a successful barcode capture.

Scan Device - External Barcode Reader
On Scan Action - Jump To Form Location
Target for Interaction - Add New Repeat/Row
Always Jump to New Repeat - Ticked
Maximizing the value from this feature
To maximize the value you can get from this feature, we recommend configuring your external barcode scanner to send in a keyboard "ENTER" or "DONE" keypress event after every successful scan.
By doing so, the On Scan Action configured on your barcode field will instantly trigger after every scan without needing you to interact with the app! This means you can focus on scanning while the app handles everything else automatically.
If you are using a Zebra barcode scanner then you can follow this guide to configure your scanner to send a keyboard "ENTER" keypress event after every successful scan:
More information on Capturing Repeatable Data might be of interest.