A more traditional print request format from early Unibar / ELS / EPP builds, but still supported in EPP 10 with File Drop, Web Service, and façade/executable call printing methods. This is a simple request format that allows building a label batch print job for a single printer destination. ULD requests can allow using different label templates in a single request, with each line following a line with parameter commands a unique label print within the batch. Only one printer can be defined withing the whole batch.
ULD Print Request Components
More details on the ULD Format and ULD Parameters & Switches are available in the published help docs portal.
| Parameter/Switch | Description |
|---|---|
| /C= | Number of label copies. |
| /DEL= | Set the data field delimiter. |
| /DR[TxData] or /DR= | /DR[TxData] Set data record layout to entry in the Label Data Dictionary (LDD). /DR= Specify the data record layout. |
| /F= | Input file to be processed. |
| /L= | Set Label Format name. |
| /OUTFILE= | Renames the output file for FILE type printers. |
| /P= | Print destination. |
| /R= | Report component. Valid values are Header, Detail, and Footer. Entries identifying the report component are not case sensitive. All three components are required for a complete report output. |
Examples
Example 1 Below example includes two copies of one label template for the printer destination:
/L=#samples\sample.lbl /P=defaultSite#FauxPrinter /C=1 /DR=ItemNumber+CustomerNumber+OrderNumber+CustomerName+ItemDescription+OrderDate
42~29~123~Arthur Dent~Don't Panic~2005/04/29
121g~88~1985~Emmett Brown~IT WORKS!~2015/10/21
The first line in a ULD request is designated for placing all of the parameter/switch definitions, like the label name, printer destination, number of copies to be printed, and the data record layout (order of variables).
Each line break represents a separate instance of the preceding label parameters, to the same printer, with individual variable assignments..*
Example 2 Below example references a TxData mapping instead of manually defining the data record layout / order of variables.
/L=#samples\sample.lbl /P=defaultSite#FauxPrinter /C=1 /DRTxData.demo
123~Arthur Dent~42~Don't Panic
1985~Emmett Brown~121g~IT WORKS!
Note that since the TxData Mapping uses a different order of the LDD variables, we also had to change the order of the variable assignments in each of the data lines of the ULD request.
Example 3 Below example includes four copies of one label template, then two copies of another label for the printer destination:
/L=ItemLabel.lbl /P=defaultSite#myLabelPrinter /C=1 /DR=ItemNumber+ItemQty+ItemDescription+ItemInstructions
0042~1~Hitchhiker's Guide to the Galaxy~Consult this manual anytime you need to understand what is going on.
6543~1~Towel, Blue~A daily necessity for interstellar travel, especially when hitchhiking.
5234~6~Bitter, Pints of~Intended to help consumer cope with the "delirious side-effects of teleportation."
0058~4~Peanuts, Packs of~Helpful for regaining energy after travelling through hyperspace.
/L=PackSeal.lbl /P=defaultSite#myLabelPrinter /C=2 /DR=CustomerNumber+OrderNumber+CustomerName+OrderDate
65432797453~413657324~Ford Prefect~2005/04/29
Each line in a ULD request containing the parameter/switch definitions, will control which label template and variable order is used in the data lines that follow it. Each line without these switches/parameters represents a separate instance of the label to be printed.
New lines containing label template definition parameters/switches will define the next label template and variable order OR TxData mapping used on subsequent data lines. The /P parameter will not allow choosing a different printer destination.