LabelServer4j Dataset CSV

From Commander4j
Revision as of 10:03, 28 August 2024 by Dgarratt (talk | contribs)

The example CSV data shown below is automatically exported when someone assigns a Process Order to a Production line in the Pallet Label screen within Commander4j.

LabelServer4j expects the filename of the CSV to be constructed from the name of the production line and printer separated by an underscore.

CSV Dataset

LINE 1_PRINTER 1.CSV

"LINE","MODIFIED","UNIQUE_ID","LABEL_TYPE","PRINTER_ID","ENABLED","PRINTER_TYPE","IP_ADDRESS","PORT","GROUP_ID","LANGUAGE","PRINTER_DPI","PROCESS_ORDER","MATERIAL","MATERIAL_TYPE","MATERIAL_DESCRIPTION","SHELF_LIFE_UOM","SHELF_LIFE","SHELF_LIFE_RULE","BATCH_NUMBER","REQUIRED_RESOURCE","PLANT","LOCATION_ID","DATE_OF_MANUFACTURE","EXPIRY_DATE","PROD_EAN","PROD_VARIANT","BASE_QUANTITY","PROD_UOM","BASE_EAN","BASE_VARIANT","PROD_QUANTITY","BASE_UOM","CUSTOMER_ID","CUSTOMER_NAME","PRINT_COPIES","MODULE_ID","OVERRIDE_MANUFACTURE_DATE","OVERRIDE_EXPIRY_DATE","OVERRIDE_BATCH_PREFIX","BATCH_PREFIX","BATCH_SUFFIX","REPORT_TYPE","MODULE_TYPE","REPORT_FILENAME","PART_NO","LAYERS"
"LINE 1","Y","cf2a2bcf-deeb-430b-b13b-e37976004e5b","Pallet","PRINTER 1","Y","Logopak","127.0.0.1","9100","Pallet","LEAP","200","00000001","00000001","FERT","Demo Material 00000001","M","24","+","4115123401","LINE1","1234","FACTORY1","24-Apr-2024 14:28:19","30-Apr-2026 00:00:00","07613030436171","01","336.000","CS","07613030436164","01","84.000","EA","SELF","My Company","1","RPT_PALLET_LABEL","N","N","N","41151234","01","Label","REPORT","zebra_200dpi_pallet_label_a5_cdf_val.lbl","","12"


The above image is the same data as the CSV in a format which is a little easier to understand.