Not every barcode is printed as a correctly scannable barcode on reports. How can this be resolved?

RetailVista could not print certain barcodes correctly. As a result, these were not scannable, because a number was missing or because an incorrect checksum was added without request. An example of a 'problem' barcode is Ean13 barcodes that start with a 0 and end with a 0, such as 0629162127020.

From RetailVista 21.9 onwards, the problem of not correctly printing some barcodes has been solved. The standard reports of RetailVista that included a barcode have already been adjusted, the adjusted reports must be manually modified via the support desk of NedFox.

In the accompanying new RetailVista Report Designer version 21.9 and higher, a new report object 'NedFoxBarcode' has been added. This object should be used where barcodes need to be printed.

After adding this object to a report, the data binding to the 'Barcode' field from the report fields must be linked.

However, the most important change is in the 'Data' tab of the properties of the barcode object. There, under 'Data bindings', the property 'BarcodeType, Binding' must be linked to the report field 'BarcodeType'. This ensures that the barcode object understands what type of barcode needs to be printed from RetailVista.

By making these adjustments, RetailVista will print a correct and scannable barcode on this report.