Detailed changelog for Continia Document Capture 2023 R2
This article lists all new updates, features, service packs, and hotfixes for Continia Document Capture 2023 R2.
Wichtig
This version of Document Capture is no longer supported. As a consequence of this, Continia will no longer correct any errors appearing in this version, and no further service packs relating to the version will be released. For supported versions of Document Capture, see Software lifecycle policy and Continia Document Capture on-premises.
Tipp
As a Continia partner, you can be notified of new Document Capture versions and service packs whenever they're released. To sign up for this service, go to this page in the Continia PartnerZone (only available to partners).
Document Capture 2023 R2 Service Pack 4
Release date, on-premises: January 30, 2025
App version: 12.4.0
FOB version: 12.04
Only released in Business Central on-premises.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Using the Create Lines action to create the first allocation line on the Purchase Allocations page could result in allocation lines with an incorrect document type. To prevent this, the Create Line action is now only enabled if at least one allocation line has already been created. | 53361 |
| Platform and Technology | Events have been added to the solution. For details, see Event Publishers for Document Capture 2023 R2 (12.00). | 55363 |
| Platform and Technology | The Continia Web Approval Portal has been updated to version 25.0.7. | 63251 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Previously, document categories became inaccessible if File Service was set as the document storage type on the Document Capture Setup page and a file with a filename exceeding 100 characters was imported. The following error message was displayed:
| 50565 |
| Documents and Templates | Zero amounts in document lines on the document card were not displayed when the Blank Zero setting on the template field card was set to False. | 51260 |
| Documents and Templates | When updating a purchase order from the document journal under the Purchase Order category, the Quantity and Unit Cost fields in the purchase order were incorrectly set to zero when registering the document – despite the values not being captured or recognized. | 53522 |
| Documents and Templates | Previously, the XML master templates had the Ask to Set Default Account No. option set to No by default. This setting has been changed to Yes, prompting users to confirm whether they want to set an account as the default when entering an account type and account number. | 53638 |
| Documents and Templates | Document lines on the document card with validation errors were mistakenly marked as OK. | 54221 |
| Documents and Templates | The Create Vendor action in the document journal would sometimes return the following error:
| 54450 |
| Documents and Templates | When the blank (space) character was configured as a decimal separator in the User Defined Decimal Separator setting on the template field, the decimal part of a detected number was not recognized | 57476 |
| Documents and Templates | Previously, the Force Register action in the sales category required the field Account for Amount Excl. VAT to be filled out. Now, this action functions the same way as in the purchase category. | 57512 |
| Documents and Templates | When users attempted to split multiple pages within the same document, the error message below was displayed – requiring the Split and Merge Documents page to be closed and reopened between each split action.
| 57519 |
| Documents and Templates | When moving XML documents to another company, the preview in the Document Viewer FactBox is now automatically shown. | 57868 |
| Documents and Templates | When capturing a value exceeding 200 characters in the template header field Our Contact, the following error message was displayed:
| 60155 |
| Documents and Templates | An incorrect table reference in the Unit of Measure translation occasionally caused an error message to appear. | 61978 |
| Documents and Templates | If an email containing both an XML and a PDF files had one of its attachments deleted, the related email could also be deleted – even if the other attachment remained in Document Capture. | 62164 |
| Document Approval | The Web Site URL field on the Continia Web Portals Card page is now only visible when configuring an on-premises Continia Web Portal. | 51051 |
| Document Approval | When logging in to the Continia Web Approval Portal as a user without a Salesperson/Purchaser set on the Continia User Setup Card, all purchase contracts were displayed. | 53827 |
| Document Approval | An overflow error occurred when users opened the Purchase Approval Entries page if the related vendor name contained 99 or more characters. | 59610 |
| eDocuments | When handling XML files containing a lot of lines (i.e.: more than 1,000), the Document Viewer FactBox would not display the HTML representation of the file. | 61168 |
| General Application | The values in the Approval Administrator and Allow Force Registration fields were not transferred to other companies when configuring approval users through the User Setup by Company page. | 40901 |
| General Application | On the Document Capture Setup page, when disabling Use Cloud OCR and using the Continia File Service, users received the following error message:
| 55882 |
| General Application | When switching the setting of the Document Storage Type field from File System to File Service, the following error is no longer shown:
| 57182 |
| Order & Receipt Matching | This following applies to the DK (Danish) localization only. When registering a purchase document with a Payment ID (FIK-kode) and with the Invoice Reg. Step 1 set to Match and Update Order on the template, the Payment Method Code, Payment Reference, and Creditor No. are now correctly populated on the matched purchase order. | 47894 |
| Platform and Technology | Document imports no longer fail, preventing the following error message:
| 57844 |
| Purchase Documents | When attempting to view the document attachments using the View in List action in the Documents FactBox, the following error message was displayed:
| 51330 |
| Purchase Documents | It is now only possible to change a line's type on a purchase order if the document status is either Open or Pending Approval and you have permission to edit pending documents. Previously, it was possible to change the line type to Comment even after a document was released – which resulted in the deletion of the document line. | 53734 |
| Purchase Documents | This update only applies to Business Central app versions supported by this Document Capture release. These can be found in Supported On-Premises Versions for Document Capture. When downloading a file from the below mentioned application areas, the filename did not adhere to the Purchase File Display Name setting in the Document Capture Setup:
| 54447 |
| Purchase Documents | When registering a purchase document to a general journal from the Purchase category, the VAT Prod. Posting Group and VAT Business Posting Group fields on the Accounts for Amounts page were not copied to the created general journal line. The issue also affected the VAT Prod. Posting Group field on the Line Translation page. | 56620 |
| Purchase Documents | When registering a prepayment invoice from the document journal, the Posting Date setting on the template card was not considered. Instead, the value from the Document Date field in the document header was used to set the Posting Date in the posted prepayment invoice. | 58990 |
| eDocuments | When exporting an XML document with an additional document attached, users could encounter the following error:
| 57634 |
| eDocuments | The validation rule for the Identifier Type 0208 BE:EN has been updated. The new validation rule is: 0-1]{1}[0-9]{9}. | 57702 |
| eDocuments | When receiving a Posted Sales Invoice or Purchase Order that has varying VAT percentages on different lines (e.g.: 25% and 10%) through the Continia Delivery Network, the following error appeared:
| 58107 |
Document Capture 2023 R2 Service Pack 3
Release date, on-premises: July 1, 2024
App version: 12.3.0
FOB version: 12.03
Only released in Business Central on-premises.
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Document and Templates | Added vendor bank account validation for Australian bank accounts (EFT BSB). | 40793 |
| General Application | Added identification rules to the XRECHNUNG-ID XML identification template to support XRechnung version 2.3 and 3.0. | 56585 |
| Platform and Technology | Events have been added to the solution. For details, please see Event Publishers for Document Capture 2023 R2 (12.00). | 55363 |
| Platform and Technology | The Continia Web Approval Portal has been updated to version 24.0.3 | 57382 |
| Purchase Contracts | The Continia Web Approval Portal has been extended to support the selection of purchase contracts for purchase invoices. The below three fields are added to Invoice Lines section in the Web Approval Portal enabling the approvers to select/change the associated contract number and contract line:
| 53971 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | The following change only applies to the NL localization: When registering a purchase invoice without any setup under Accounts for Amounts, the value in the Doc. Amount VAT field on the purchase invoice was not populated. | 54763 |
| Country and Regional | In some localizations, a wrong Account Type was potentially selected when activating the Recognize Fields action. | 56942 |
| Document and Templates | When a document was moved to another company, the OK field in the Document Journal was not cleared. | 52596 |
| Document and Templates | When configuring the Document Storage Type in the Document Capture Setup page as File Service and using Cloud OCR, the XML files couldn't be imported. | 52904 |
| Document and Templates | The field Line Recognition Method was wrongly shown in the Template Card for XML templates. | 53554 |
| Document and Templates | When manually entering values in the document line fields on the Document Card, you could encounter a warning indicating reduced functionality. Additionally, the document viewer could become unresponsive. | 53959 |
| Document and Templates | When importing an XML file, the following error could occur:
| 54103 |
| Document and Templates | The field Insert on new Templates was missing on the Template Field Card for the master templates. The field has now been added to the page as an additional field and is easily displayed using the Show more action. | 54126 |
| Document and Templates | The vendor creation guide now doesn't fill in the currency code if the recognized value is identical to the LCY Code configured in the General Ledger Setup page. | 54231 |
| Document and Templates | If an invoice had the same document number as a credit memo, attachments from both documents would be shown on both the documents in the drag and drop section. | 54312 |
| Document and Templates | Optimized the document import processing time by skipping merge operations when templates are not configured to automatically combine PDF files from the same email into one Document Capture document. | 54373 |
| Document and Templates | Corrected a bug that caused the Document Log Entries to be sorted in a non chronological way in the Document Log Summary page | 54831 |
| Document and Templates | Using Document Capture without having an internet connection, the user got the following error when opening the document journal:
| 54856 |
| Document and Templates | When selecting the Add Template Field action on a document that originates from Continia eDocuments, the following error message was shown:
| 55010 |
| Document and Templates | During document import, a new template was wrongly created for the document when there was already a template available in another company for the same vendor. Now, a new template won't be created and the template number won't be populated in the Document Journal. Instead the user must run Recognize Fields manually in the Document Journal. This will trigger the following dialog:
| 55407 |
| Document and Templates | When moving documents to another company, the following error could occur:
| 55515 |
| Document and Templates | When the Secure Archive feature was enabled and either of the following features were used:
| 55986 |
| Document and Templates | When filtering document lines in the Document Card, the highlighted field in the document viewer did not correspond with the actual line selected in the Document Lines subpage. To address this, the Line No. column will be shown on the lines subpage, if not already present, when filtering. The column will be removed automatically when the filter is released. | 56132 |
| Document and Templates | When registering a document with lines recognized in the Sales category, the unit prices on the created Sales Order or Sales Credit Memo were unintentionally taken from the Document Capture document. This behaviour has been changed to use the sales prices specified in Business Central. | 56645 |
| Document and Templates | When using document search in environments with XML-documents, users could experience a degraded performance caused by unnecessary external calls to Continia Online. These external calls had now been removed, resulting in a better search performance. | 56889 |
| Document Approval | When trying to assign a filter with a length over 80 characters by using lookup in Assigning Filter in the Approval User Group Permission page, the following error occurred:
| 48914 |
| General Application | The way Document Capture requests the number of files to process when opening the Document Journal has been changed. This will speed up the opening of the Document Journal immensely when using File Service as the document storage type. | 53801 |
| General Application | All supported languages have been added for the W1 localization on the following pages:
| 54376 |
| General Application | When exporting attachments using the Export Attachments report, any unregistered documents were exported without a file name. | 54701 |
| General Application | When users opened the Role Center without having an internet connection, they were presented with the following error:
| 54855 |
| Order & Receipt Matching | Previously the option fields Match on Vendor Order No. and Match on Vendor Shipment No. were only visible on the template card if the corresponding template header or line fields were added to the template. This behavior has been extended to add and show the fields on the template when creating it, if the fields on the master template are configured with the matching option Yes - Always. | 49102 |
| Order & Receipt Matching | When a matched amount was calculated during the match process, the amounts where rounded using the rounding precision from General Ledger Setup, instead of the rounding precision related to the currency involved. | 49716 |
| Order & Receipt Matching | When matching a purchase invoice having Prices Including VAT set to Yes against a purchase order having Prices Including VAT set to No, the Direct Unit Cost on the purchase order lines was copied to the invoice lines and was not recalculated (taking into account the VAT amount to be applied). | 53229 |
| Purchase Contracts | The following feature is only available for the US localization of Document Capture. Support for tax calculation has been added to the Purchase Contract Card. The following two new fields have been added to the purchase contract header:
| 32643 |
| Purchase Contracts | Previously, when registering a document linked to purchase contract and a value was specified in the Deferral Code field under the Accounts for Amounts page, the selected deferral code value was ignored. Now, the deferral code value is assigned to the created invoice/credit memo lines. | 53937 |
| Purchase Documents | The following change only applies to the US localization. Having a purchase document with Prices Including Tax set to Yes, the following error message was wrongly shown, when opening the purchase documents list for orders, invoices, credit memos, and return orders:
| 51338 |
| Purchase Documents | In some cases, when no lines were recognized, the line field values in the created purchase invoice could be overwritten with false data if the template line field had a value in field Field in Purchase Line under the Transfer Value to... group on the General FastTab. | 53707 |
| Purchase Documents | When selecting the Document Card action in the Purchase Orders page for a manually created purchase order, the eDocuments order response page was in some situations opened. This behaviour was incorrect as the order response wasn't the source of the purchase order. Now, when using the action Document Card in this scenario, an error message is shown:
| 54543 |
Document Capture 2023 R2 Service Pack 2, hotfix 2
Released: April 11, 2024
App version: 12.2.2
FOB version: 12.02.02
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When you imported documents in an on-premises version of Document Capture with no license access to Continia eDocuments, the following error ocurred:
Due to Document Capture and Continia Delivery Network being co-built (on-premises only), no changes have been applied to Document Capture even though the version number has been increased to 12.02.02. | 54800 |
Document Capture 2023 R2 Service Pack 2, hotfix 1
App released: March 8, 2024
FOB released: March 11, 2024
App version: 12.2.1
FOB version: 12.02.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | When upgrading to Document Capture on-premises 12.2.0, the upgrade process failed with the following error:
| 53965 |
| General Application | When sales orders were released in a company where eDocuments was not activated, the following error occurred:
| 53967 |
Document Capture 2023 R2 Service Pack 2
Released: March 7, 2024
App version: 12.2.0
FOB version: 12.02
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Continia eDocuments was introduced – Continia's new system for the exchange and management of electronic business documents (XML documents), powered by the Continia Delivery Network. Continia eDocuments makes it easy to transfer virtually any type of business document from the procure-to-pay process through networks like the PEPPOL Network within Business Central. By converting Business Central documents to and from XML files that can be sent and received via such networks, it allows you to work with XML documents exactly as with other documents in Business Central. With Continia eDocuments, you can identify and fix errors in your documents before they're sent, and vendors can notify you directly about any changes using order responses. Whether you're a customer or a vendor, you can monitor the status of each document throughout the process using the eDocument Status field. For more information, see Continia eDocuments. Note This note was added later, on April 25, 2024, as it was unintentionally left out of the changelog when Document Capture 2023 R2 Service Pack 2 (DC12.02) was released. | |
| Documents and Templates | To simplify configuration, a Customizable Columns section for the custom searchable and sortable template header fields in the Document Journal's document list has been added to the Document Category card. | 49668 |
| General Application | With the introduction of Enforced Digital Vouchers in BC23.2, attaching documentation as incoming documents, prior to posting purchase document and journals, will in certain localizations become mandatory. When using Document Capture in an environment where Enforced Digital Vouchers is configured to check for attached files prior to posting, Document Capture will automatically create a digital voucher when a document in registered as a purchase document or a journal entry. The primary document (OCR processed) and any drag and drop attachments, will automatically be added to a digital voucher associated with the purchase document or journal entry. When using purchase allocations (part of the approval functionality available with Document Capture) the system can be configured to include the digital voucher, associated with the purchase document pending approval, in the G/L posting. Associating digital vouchers to purchase allocations is optional, regardless of localization and BC version. How to enable the feature:
| 50510 |
| Purchase Contracts | Multiple invoices related to the same purchase contract and within the purchase contract's invoicing period are not auto-approved. | 47823 |
| Purchase Documents | You can now enter a negative amount in the New Amount Excl. VAT field on the Change Document Amount page. The error message displayed when entering a negative number in the New Amount Incl. VAT has been changed to the following:
| 48535 |
| Purchase Documents | Added a column showing the date and time the document was imported to the Document Log Summary page. | 49582 |
| Purchase Documents | When both the standard attachment action and the Document Capture attachment action are visible on the same page, the caption for the Document Capture action is changed to Document Capture Attachments. | 52781 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | Multiple German translations have been corrected on several pages. | 51595 |
| Document and Templates | When moving an XML document to another company, the field XML Document Type would be set to empty after selecting a vendor/customer in the Document Journal. | 48071 |
| Document and Templates | With the release of DC12.01, the following note was not included in the changelog: In the Document Journal and Document Card pages, users were previously able to edit header template fields configured with a formula as either a field reference or fixed value. Now, header fields that are configured with a field reference formula are locked to prevent editing. | 49508 |
| Document and Templates | In the Document Journal, header template fields used in customizable columns and as sorting criteria are now visually cleared when trying to update the template field value. | 49966 |
| Document and Templates | To prevent unwanted translations or removals of recognized names, the Field Translations honorifics for the Our Contact template header field have been updated with an additional space at the end of the Translate From value. | 50237 |
| Document and Templates | Fixed an issue where the Customizable Columns fields in the Document Journal were not updating properly when manually capturing values. | 50366 |
| Document and Templates | Setting up a template field with a Data Type of Text as a Search Field in the Document Journal, which value exceeded 30 characters, would result in the following error message:
| 51485 |
| Document and Templates | During the purchase document import into the PURCHASE document category, if the Split PDF Document option was enabled for the Source ID, the following error message was displayed:
| 51747 |
| Document and Templates | Typing a part of the user name in the Category Manager field in document category resulted in the following error message:
| 51915 |
| Document and Templates | When deleting a Master |