Barcode Config Reference
Barcode Config Fields
Every barcode the app renders is driven by a Barcode Config record (BarQR__Barcode_Config__c). Create and edit configs from the Barcode Configs tab — the New and Edit buttons open the guided editor with a live preview. See Lightning Experience Setup for a walkthrough.
| Setting | API name | Description |
|---|---|---|
| Barcode Config Name | Name |
Unique name used to reference the config from components, Flow and Apex. Letters and numbers only — no spaces or special characters. |
| Object | BarQR__Object_API_Name__c |
API name of the object to read data from, e.g. Account or Asset__c. |
| Field | BarQR__Field_API_Name__c |
API name of the field whose value is encoded, e.g. AccountNumber. |
| Barcode Type | BarQR__Barcode_Type__c |
The symbology. 100+ options; defaults to Code 128. Use the search box or the View Barcode Specifications icon in the editor to find a type. |
| Show Text Below Barcode | BarQR__Show_Text_Also__c |
Prints the human-readable value under the barcode. Not supported by every barcode type. Default: on. |
| Scale X / Scale Y | BarQR__Scale_X__c / BarQR__Scale_Y__c |
Horizontal and vertical size multiplier per module, from 1 to 20. Default: 2. |
| Download Options | BarQR__Allow_Save_to_formats__c |
Shows Download (PNG) and/or Download (JPEG) links under the barcode. |
| Image Rotations | BarQR__Image_Rotation__c |
N Normal (default), R Right, L Left, I Inverted. |
| Font Rendering | BarQR__Font_Rendering__c |
A Anti-Aliased (default) or M Monochrome. Used by the Classic / Visualforce generator page. |
Tip: Keep config names unique. Salesforce does not enforce this, but the record-page component shows an error when two configs share a name, and Flow and Apex use whichever matching config they find first.
Where Each Setting Applies
The app renders barcodes in two different ways:
- In the browser — the Lightning component, the Bulk Barcode Generator, the guided editor preview, and the Classic / Visualforce generator page. These support all 100+ barcode types and honor every setting above.
- On the server — the Flow actions, the Apex API, and the Visualforce image and PDF pages. These produce real PNG or SVG files, support the barcode types listed below, and use only the Barcode Type, Scale X and Scale Y settings. Text below the barcode, rotation and download options are ignored.
Barcode Types Supported for Server-Side Generation
Use the API value when a Flow action or Apex request asks for a Barcode Type. Values are not case-sensitive. When you use a config-based action, the config’s Barcode Type must be one of these.
| Barcode type | API value | Barcode type | API value |
|---|---|---|---|
| QR Code | qrcode |
Code 128 | code128 |
| Micro QR Code | microqrcode |
GS1-128 | gs1-128 |
| Data Matrix | datamatrix |
Code 39 | code39 |
| GS1 Data Matrix | gs1datamatrix |
Code 93 | code93 |
| PDF417 | pdf417 |
Code 11 | code11 |
| MicroPDF417 | micropdf417 |
Codabar | rationalizedCodabar |
| Aztec Code | azteccode |
Interleaved 2 of 5 (ITF) | interleaved2of5 |
| GS1 DataBar Omnidirectional | databaromni |
ITF-14 | itf14 |
| GS1 DataBar Stacked | databarstacked |
EAN-13 | ean13 |
| GS1 DataBar Stacked Omnidirectional | databarstackedomni |
EAN-8 | ean8 |
| GS1 DataBar Limited | databarlimited |
EAN-2 (2 digit addon) | ean2 |
| GS1 DataBar Expanded | databarexpanded |
EAN-5 (5 digit addon) | ean5 |
| USPS Intelligent Mail | onecode |
UPC-A | upca |
| Royal Mail 4 State Customer Code | royalmail |
UPC-E | upce |
| MSI Modified Plessey | msi |
Pharmaceutical Binary Code | pharmacode |
Any other type returns the error Unsupported barcode type: … from server-side generation, but still renders in the browser components.
Note: The data must be valid for the selected symbology. For example, EAN-13 needs 12 or 13 digits and GS1 types need application identifiers in parentheses, such as
(01)04006381333931. Invalid data returns an error instead of a barcode.