FIX: Documents filed against incorrect record when non-matching barcode prefix present in the same batch Print ZTN4531 This Zetadocs technical note applies to: · Zetadocs Server 3.0 and 3.1 when using barcode splitting with barcode prefix · Version 3.0 of the Zetadocs Server was released 8 February 2019 Symptom After a batch split, the *.dqf files generated for the individual split files contains no barcode or barcodes from other files. The Zetadocs auto-link functionality if enabled will archive some files against the incorrect records. This impacts Zetadocs implementations using a barcode prefix with the auto-link functionality, when at least one barcode processed in the batch does not match the barcode prefix. Cause A fault was introduced during an optimisation of the barcode split process that maintains the information from one point of the batch workflow to the end. Resolution This fault was corrected in a hotfix which is available by contacting Equisys Technical Support and quoting the technote number ZTN4531. Please get in touch with support if you believe you have any records that have been impacted by the fault so that they can advise on the best recovery approach. Status This behaviour was corrected in the hotfix detailed above. Last updated: 11th July 2019 (CR/GC) Keywords: Document converter; Batch split; Barcode; dqf file; wrong barcode; NAVZetadocs Document Queues Related articles INFO: How to correctly configure Zetadocs Document Queues to avoid simultaneous processing of the same SharePoint folder PRB: 'Internet browser is not installed' error when authenticating with SharePoint Online or opening documents from the Factbox FIX: SharePoint site is currently unavailable or too busy failure when opening Zetadocs Document Queue HOWTO: Upgrading the Zetadocs Expenses Connector for Business Central and NAV on-premises PRB: Factbox returns the error message 'SharePoint authorisation was refused'