Detailed Changelog for Continia Document Capture 2023 R2
This article lists all new features and bug fixes for each version of Continia Document Capture 2023 R2.
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 template with related templates, the following dialog was shown for each template field:
| 51923 |
| Document and Templates | When copying a template, the Line Recognition Method was set to Not Configured in the new template. Now, if Recognize Lines is enabled in the original template in the Template Card, the Line Recognition Method will be transferred to the new template. | 52083 |
| Document and Templates | When importing documents, the following error could occur:
| 52084 |
| Document and Templates | Added the possibility to navigate between the document header fields on XML documents using the tab key in the Document Journal and Document Card. | 52329 |
| Document and Templates | Arrow key navigation in the Value and XML-Path fields of the header template within the Document Journal and Document Card has been updated to improve user experience and interaction efficiency.
| 52925 |
| Document and Templates | When creating two or more search texts on a template, and the initial search text is of maximum length (200 characters), the document journal would display the following error message when opened:
| 52971 |
| Document and Templates | The order of the Field Translations for the Our Contact template header field have been changed, so the honorific translations are done after the delimiter translations. | 53504 |
| Document Approval | The tooltips on the Document Capture Setup / Continia Web Approval page has been updated to match the tooltips on the Continia Web Portal Card page. | 49312 |
| Document Approval | When approving documents, users could receive the following message:
| 52012 |
| Document Approval | When having multiple approval entries with the same Document Type and Document No., but different Table ID, the Web Approval Portal would occasionally show an incorrect list of approvers for a given purchase document. | 53316 |
| General Application | The Export Users action on the Continia User Setup list was not visible if both Document Capture and Expense Management were installed, and a web approval portal configuration wasn't fully completed. | 52060 |
| Platform and Technology | Fixed an issue where the template field Caption Mandatory was not respected when using AI for field recognition. | 52728 |
| Purchase Contracts | Previously, when creating a purchase contract based on the expense, the purchase contract line Start Date value was set to the expense Document Date. Now, the line Start Date is set to the Contract Start Date specified on the Create Purchase Contract page. | 52104 |
| Purchase Documents | The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The duplicate Purchase Code field was removed from the Purchase Order page. | 51393 |
| Purchase Documents | When a purchase document (order, invoice, credit memo, or return order) had a Currency Code specified and the Currency Factor was equal to 0 in the header, an error message was displayed:
| 51463 |
| Purchase Documents | The Documents factbox on the purchase order list page was only shown if the purchase order category was in use. Now, the factbox is always visible when Document Capture is activated in the current company. | 51784 |
| Purchase Documents | Previously, when the Distribute by Dimensions option was enabled in the Standard Amount Distribution Code Card and an amount distribution code was used, the Amount to Distribute field in the Get Amount Distribution page of the purchase invoice was set to the total invoice amount. With the new update, the Amount to Distribute field will be set to the purchase line amount. | 52093 |
| Purchase Documents | When opening the Posted Purchase Invoice or Posted Purchase Credit Memo pages in a company where Document Capture was installed but not not configured (no data in the Document Capture Setup), the system would display the following error message:
| 52809 |
Document Capture 2023 R2 Service Pack 1, hotfix 5
Released: February 13, 2024
App version: 12.1.5
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | When having multiple approval entries with the same Document Type and Document No., but different Table ID, the Web Approval Portal would occasionally show an incorrect list of approvers for a given purchase document. | 53316 |
Document Capture 2023 R2 Service Pack 1, hotfix 4
Released: February 8, 2024
App version: 12.1.4
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Document Approval | Configuring an approval sharing record to send the approval status email to Both Approvers would in certain situations add the wrong recipient as CC to the email. The functionality has been disabled in this version of Document Capture. Existing Approval Sharing Setup records configured to send the email to Both Approvers will be treated the same as records configured to send to Only Shared To User. The system will display an error message if the user attempts to configure an Approval Sharing Setup record to send the approval status email to Both Approvers. | 53210 |
Document Capture 2023 R2 Service Pack 1, hotfix 3
Released: February 2, 2024
App version: 12.1.3
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | With the release of Continia Document Capture 2023 R2 (DC12.00), a change was introduced, causing the document recognition to ignore the Required field option unless the Search for Value option was set to True in the Template Field Card. This meant that a document could be registered with blank values in required fields without generating an error comment. Now, the capture functionality has been updated as follows: Header field recognition:
| 52441 |
Document Capture 2023 R2 Service Pack 1, hotfix 2
Released: January 19, 2024
App version: 12.1.2
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When running Recognize Fields in the Document Journal, the formula keywords TODAY and WORKDATE specified in the Template Field Card were not converted as expected when running the Business Central client in different languages. Please note that some localized abbreviations have the opposite meaning in different languages. For example, T evaluates to TODAY in English, but in French and Spanish, it evaluates to WORKDATE. To ensure the correct result, it may be necessary (depending on the language used in the client) to type the entire keyword - e.g., when running the client in Spanish, T might not be enough to ensure that it is interpreted as WORKDATE - but entering TRABAJO will ensure that. To avoid possible mistakes or unexpected results, it is recommended to update existing template field formulas by clearing the value and entering it again. | 50407 |
| Documents and Templates | When importing documents the following error could occur:
| 52574 |
| Document Approval | Since Document Capture version 12.1, exporting users with the same email address in the Email and O365 Authentication Email fields on the Continia Users page has not been possible. The functionality has now been reverted, allowing identical emails in both fields for the same user. | 52507 |
| Purchase Contracts | Previously, when registering a document based on the purchase contract, which had a different VAT Bus. Posting Group header value than the vendor or the purchase contract line had a modified VAT Prod. Posting Group, the original vendor, and account VAT posting group values were assigned to the purchase invoice header and lines. Now, the VAT values are taken from the related purchase contract header and line fields and assigned respectively to the invoice header and lines. | 51428 |
Document Capture 2023 R2 Service Pack 1, hotfix 1
Released: December 20, 2023
App version: 12.1.1
FOB version: 12.01.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Platform and Technology | This change only applies to Expense Management. See the Expense Management 12.01 hotfix1 changelog for more details. | 52088 |
Document Capture 2023 R2 Service Pack 1
Released: December 15, 2023
App version: 12.1.0
FOB version: 12.01
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | The below configurable message can now be configured as type Information:
| 47538 |
| General Application | The right and left arrow keys can be used to move the cursor between the Field and Value columns in the Document Header section on the Document Journal and Document Card pages. | 42484 |
| General Application | A link to the Document Log has been added to the Document Journal page. | 50367 |
| Platform and Technology | The Continia Web Approval Portal has been updated to version 1.29.0 | 51759 |
| Purchase Contracts | When registering a document (invoice) based on a purchase contract, it is possible to define if a comment purchase line with a posting description should be created. To manage this, the following three new fields have been added to the Purchase Contract Card page:
| 45255 |
| Purchase Documents | Previously, the Incoming Document Files factbox was hidden if Document Capture was configured in the current company. As the incoming documents functionality is a key part of Microsoft's new Digital Vouchers feature, the factbox will not be hidden but instead showing it below the Document Viewer factbox. | 51602 |
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | During vendor identification and auto-matching, captured document values may be used as table filters. The below error could occur if a captured value, used as a table filter, started with a percentage sign (%).
| 43210 |
| Documents and Templates | When updating the field Ask to Set Default Account No. on the Master template, the sub-templates were not updated with new value. Now, updating the Ask to Set Default Account No. on the Master template updates all the sub-templates. | 43647 |
| Documents and Templates | In Business Central 2020 release wave 2 and later, activating the Create Vendor action in the Document Journal without available vendor templates, nothing would have happened previously. Now, selecting the action always prompts the Create Vendor guide. | 44237 |
| Documents and Templates | Recurring Journal was selectable on the Document Category page in the field Journal Template Name even though it was not supported. Now, the Recurring Journal option is filtered away, and if typed directly into the input field, this error is thrown:
| 45076 |
| Documents and Templates | An incorrect document validation comment in the Purchase Order category for the Danish and German localizations has been corrected. The following message:
| 47562 |
| Documents and Templates | When filling in the Translate To No. value in the line section on the Document Card, the OK field value was not set to true. This applied to the web client only. | 47780 |
| Documents and Templates | When deleting a Master template without any related templates, the following dialog was shown for each template field:
| 49163 |
| Documents and Templates | When configuring the template field Type to Charge (Item) and subsequently assigning a valid item charge to the Account No. template field, the following error comment was displayed:
| 49304 |
| Documents and Templates | The Match Lines action in the Document Journal has been disabled for purchase invoice or credit memo documents when template Invoice Reg. Step 1 or Credit Memo Reg. Step 1 on the Template Card is set to Create Journal Line. | 49447 |
| Documents and Templates | On 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 a fixed value. Now, header fields that are configured with a field reference formula are locked to prevent editing. Note This note was added later, on February 2, 2024, as it was unintentionally left out of the changelog when Document Capture 2023 R2 Service Pack 1 (DC12.01) was released. | 49508 |
| Documents and Templates | When identifying the XML template for an electronic document, only the identification template field with the code CUSTOMISATIONID was considered. Now also the identification template field with code VERSIONID is considered when identifying the XML format. | 49531 |
| Documents and Templates | In the Documents factbox on both posted and unposted purchase documents, the Rename and Delete actions are now disabled for attachments referencing the original document. | 49576 |
| Documents and Templates | Specifying No., VAT Prod. Posting Group, or VAT Bus. Posting Group when Type is blank in the Account for Amounts, the following error message will be displayed:
| 49590 |
| Documents and Templates | Previously, a captured Vendor Bank Account No. containing only letters would incorrectly pass validation. | 49730 |
| Documents and Templates | To prevent potential errors in the Document Journal, an option to select master or ID templates in the Template No. field is removed. The restriction applies to the following document categories:
| 49817 |
| Documents and Templates | The Invoice Total, shown below the document lines on the Document Card, could show an incorrect value if one or more header fields were set up to Subtract from Amount Field. | 49853 |
| Documents and Templates | The orange and blue captured markups were not visible when viewing a registered document in the Document Journal (CDC Document List with Image). Now, the markups are always shown, no matter the document status. | 49869 |
| Documents and Templates | You can now add empty files as attachments to the Document Journal. | 49916 |
| Documents and Templates | Instead of the user name, the user ID was displayed as Category Manager in the Document Category Card. | 49961 |
| Documents and Templates | When using AI for line recognition, the line recognition did not respect the Stop Lines Recognition settings on template header fields. This has now been fixed. | 50278 |
| Documents and Templates | When configuring sharing of document assigning in the Document Sharing page, the email notification was only sent to the Owner User ID. Now, both the Owner User ID and Shared User ID users will receive email notifications. | 50282 |
| Documents and Templates | Fixed an issue for line recognition when using AI, where a calculated value would overwrite the quantity if the unit price was missing. | 50350 |
| Documents and Templates | If the Document Card was opened by selecting the document number from Document Journal instead of the dedicated action Document Card, some fields were not visible under the Lines tab. | 50678 |
| Documents and Templates | If the length of the document line description exceeded 150 characters, the following error occurred, when opening the description Line Translations page:
| 50777 |
| Documents and Templates | When a user manually imports a single document and encounters an error, attempting to import the same document again could result in the deletion of both the PDF and TIFF files. | 50810 |
| Documents and Templates | When entering a numeric value on the document lines, values were always converted to positive. | 51100 |
| Documents and Templates | When placing the cursor on a template header field of the type boolean on the Document Header table, the cursor could get stuck when navigating up and down the list using the arrows. | 51107 |
| Documents and Templates | When identifying the vendor on a document using identification templates, the Document Capture will disregard a captured identification value if it equals the VAT Registration No. in the Company Information. That functionality has now been extended to cater for values found in the following additional fields in the Company Information, but not for all localizations:
| 51192 |
| Documents and Templates | The functionality to offset a captured value in a date field with a fixed date formula, Calculate Date (Date Formula) on the template field card, was not working if the AI engine processed the document. | 51194 |
| Documents and Templates | When splitting or merging documents containing AI-recognized data, the AI result would become inconsistent, and thus, the result when recognizing fields or creating vendors would not be correct. A routine reprocessing the documents created from splitting or merging has been added. | 51241 |
| Documents and Templates | Fixed an issue where the Create Vendor action in the Document Journal would give a string overflow error. | 51373 |
| Documents and Templates | The Create Vendor guide can assist the user in quickly creating new vendors on AI-processed documents. If multiple parties are identified as potential vendors, the most likely party is presented to the user as the first suggestion. | 51596 |
| Documents and Templates | When registering documents, and the template registration step 1 was set to Gen. Journal Lines without specifying the Journal Template Name or Journal Batch Name on the category, the registration process would produce the following error:
| 51671 |
| Documents and Templates | The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. When line fields were captured using drill-down after opening the Document Card page, the values could be placed in the wrong columns. | 51681 |
| Documents and Templates | Vendors on the Source Exclusion list were not skipped when the identification was performed on the AI-generated dataset. | 51944 |
| Document Approval | When the shared-to approval user rejected a purchase document, the Owner User ID was shown in the Approval Entries instead of the Shared User ID. | 43096 |
| Document Approval | When using Approval Flow codes with a selection method other than All, the picked approvers would be wrong if the purchase order was partially invoiced. This was due to the remaining amount to be invoiced being used as the approval amount when sending the document for approval. That has been changed to always use the total order amount (LCY). | 50325 |
| Document Approval | In some instances, the Amount Excl. VAT (Assigned) and Amount Incl. VAT (Assigned) were not calculated in the Purchase Order. This resulted in issues with the approval flow, where the purchase order was sent to the incorrect approver. | 51411 |
| Document Approval | When accessing the Web Approval settings page through the Document Capture Setup card, the Azure Application Key field was not masked. | 51914 |
| General Application | When downloading a document from the Documents (attachments) factbox, the exported file will now get the same name as the display name shown in the factbox. | 45098 |
| General Application | Document Capture and Expense Management actions has been re-organized into relevant action groups in the Continia User Setup and Continia User Setup Card pages. Document Capture action group:
| 49278 |
| General Application | To avoid having an invalid storage type for Document Capture during cloud migration, we now show this confirm dialogue to warn the user about potential issues: 'There are cloud migration issues with Document Capture, because one or more companies use a document storage type that is unsupported in Business Central Online. To resolve this problem, you need to change the document storage type in your on-premises environment (to either database or Azure Blob Storage) and then rerun the data replication.'; Companies with unsupported storage type: <company name> Do you still want to continue?" If the user selects Yes, the cloud migration will continue, as blocking the completion of the migration is not desired. | 49701 |
| General Application | An incorrect number of attachments was shown on the Posted Sales Credit Memo page. | 49821 |
| General Application | The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. Context-sensitive help is now available on the Continia Users page. | 49913 |
| General Application | When selecting what data to include in the exported configuration file using the Assisted Setup Guide, the following error could occur:
| 50002 |
| General Application | The Swedish translation for the field Maximum allowed difference Incl. VAT has been adjusted on the following pages:
| 50083 |
| General Application | In the Document Capture Assisted Setup, the localization name has been changed from Germany to German (Germany). The localization list is available during configuration import from Continia Online. | 50087 |
| General Application | When using storage type File Service in combination with OnPrem OCR, the XML directories for each category weren't created correctly. | 50177 |
| General Application | The page Pre-Cloud Migration Wizard was not searchable within Business Central. | 50285 |
| General Application | Corrected an issue where selecting and importing a single XML file when using storage type File Service failed. Doing a full import (the action Import Files from the role center) wasn't affected. | 50345 |
| General Application | Copying the email address when right-clicking the Email field directly in the Document Categories page (6085575 - CDC Document Category) is now enabled. | 50348 |
| General Application | Having the Secure Archive enabled in a company, the deletion of individual pages within a document was not logged in the document log. A Document Log Entry is now created when a document page is deleted. Furthermore, several document page operations (reorder pages, rotate pages, split, and merge) would cause the system to recalculate the hash value associated with the document. The recalculation of the hash value is now reflected in the document log. | 50370 |
| General Application | When creating vendors, using the AI driven capture, the system would in certain cases mistake the companies own name and address details for the vendor details. Additional checks are now being carried out in order to prevent this scenario. | 50406 |
| General Application | Belgium and Dutch translation mistakes have been fixed in the following pages and fields: Suggest Header Field Captions page caption. Template Field Card page field captions:
| 50639 |
| General Application | When having a PDF attachment in the Document Viewer whose size exceeds the browser limit, the Document Viewer would not show the PDF. The PDF attachment will now be displayed, no matter the size. | 50749 |
| Order & Receipt Matching | The purchase order lines were not shown on the Invoice Matching page when filtering the order lines on a Vendor Order No. having more than 20 characters. | 49188 |
| Order & Receipt Matching | When manually matching multiple purchase order lines with the template setting Auto Approve Within Variance enabled, the following warning was shown, even though lines were fully matched within variance:
| 49421 |
| Order & Receipt Matching | When performing Get Order Lines in a purchase invoice for purchase orders with item tracking lines, invoice posting was not possible due to multiple error messages related to the item tracking. Purchase order item tracking lines are now hidden in the Get Order Lines to prevent any potential errors. | 50959 |
| Order & Receipt Matching | When using the Match and Update Order feature in the purchase category, the Document Viewer on the purchase order card was only visible if the purchase order category contained a document. | 51548 |
| Platform and Technology | Previously, when trying to send a test email from DC, the SMTP and Email feature were triggered, prompting two popups, once for each type. Now, sending test emails will only trigger either SMTP or Email, depending on whether the Email feature is activated and properly configured. | 50099 |
| Purchase Contracts | The Create Purchase Contract action was enabled on the Document Card and Document List pages, even though the document was not recognized and had no template assigned. | 49211 |
| Purchase Contracts | The field Purchase Contract Administrator is added to the User Setup by Company, allowing you to define users as purchase contract administrators across multiple companies easily. | 49912 |
| Purchase Contracts | When assigning a G/L Account, Item, Fixed Asset, Resource, or Charge (Item) whose description length is over 50 characters, the following error was thrown:
| 49959 |
| Purchase Contracts | When updating the Review field on a purchase contract to Date Formula, the value in the Next Review Date field was not updated if a date was already specified. Now, changing the Review Date Formula updates the Next Review Date value accordingly. | 51288 |
| Purchase Contracts | When starting, submitting, returning to the reviewer, finishing, or canceling a purchase contract review with a line whose description is over 50 characters, the following error could occur:
| 51753 |
| Purchase Documents | Clients who migrated from older versions of Document Capture (pre DC5.50) to later versions (app-based versions) were sometimes faced with blank image pages on historic documents. The problem was caused by missing PNG (image format) versions of the document pages. The Document Viewer now automatically senses if the needed image files are available. If the files are missing, they will be automatically created on the fly (only possible if the TIFF (image format) representation of the document is available). | 42567 |
| Purchase Documents | The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC v20) and newer versions. The below error message would appear when attempting to perform a partial Get Order Lines on a second purchase invoice tied to the same purchase order, after a successful action on the first invoice.
| 49084 |
| Purchase Documents | The PDF File action on the General Journal page has been moved from the Bank action group to the Line group. | 49161 |
| Purchase Documents | Registered documents in the purchase order category can no longer be re-opened once a created or updated purchase order has been posted. | 49413 |
| Purchase Documents | When registering purchase documents in the Document Journal to journal lines, the General Journal was always opened regardless of what was specified in the Journal Template Name in the Document Category. Now, the relevant journal will be opened based on the Journal Template Name setting in the Document Category. | 49427 |
| Purchase Documents | The credit memo attachments were not displayed when creating a payment suggestion in the Payment Journal. | 49867 |
| Purchase Documents | The Business Central standard actions in the Incoming Document action group on the sales order were hidden even when enabling the Show Standard Purchase UI Elements option on the Document Capture Setup page. | 50505 |
| Purchase Documents | Registering a document in the purchase order category without capturing the unit cost, the order lines were created with a unit price of 0 (zero). | 51044 |
| Purchase Documents | The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. With the release of Document Capture 2023 R2 (DC 12.0), the factboxes Attachments, Incoming Document, and the Attachments action were hidden on the following pages:
| 51417 |
Document Capture 2023 R2, hotfix 11
Released: December 6, 2023
App version: 12.0.11
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | The following only applies to the App based versions of Business Central. When line fields were captured after opening the Document Card using drill-down, the values were captured in the wrong columns. However, this issue did not occur when opening the Document Card using the Document Card action on the Document Journal. | 51681 |
Document Capture 2023 R2, hotfix 10
Released: December 4, 2023
App version: 12.0.10
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | After installing Document Capture 12.0.8, the job queue job Telemetry Management codeunit (1350) fails with the following error:
| 51569 |
Document Capture 2023 R2, hotfix 9
Released: November 30, 2023
App version: 12.0.9
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | When using Business Central 2023 Wave 2 (BC23) with the Belgian (BE) localization, users encountered the following error while posting an invoice that included purchase allocations:
| 51536 |
Document Capture 2023 R2, hotfix 8
Released: November 29, 2023
App version: 12.0.8
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | When using Business Central 2023 Wave 2 (BC23) with the Belgian (BE) localization, users encountered the following error while posting an invoice that included purchase allocations:
| 51496 |
| Documents and Templates | When using the Create Vendor guide, not all of the addresses captured from the document were made available. | 51053 |
| Documents and Templates | When manually entering values with more than two decimals into a number field, e.g., Unit Cost, in the Lines section on the Document Card, the following error could occur:
| 51101 |
| Document Approval | If the enum Purchase Line Type field was extended with additional option values by another extension, users would get the following error when opening the invoices in the Continia Web Approval Portal:
| 51400 |
| General Application | With Document Capture installed editing the VAT Registration No. on a vendor would cause the following permission error:
| 51180 |
Document Capture 2023 R2, hotfix 7
Released: November 14, 2023
App version: 12.0.7
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Fixed an issue where boolean document header fields would be shown to have the value yes, when they were initialized to false (represented by ''). | 51102 |
Document Capture 2023 R2, hotfix 6
Released: November 13, 2023
App version: 12.0.6
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | Fixed an issue where the document import would display a RunModal error. The error would occur for vendors if no default template was selected or if the category had multiple master templates configured. | 50949 |
Document Capture 2023 R2, hotfix 5
Released: November 8, 2023
App version: 12.0.5
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When you upgraded to DC v12.00 in a Belgian localization and had values that exceeded 20 characters in the Enterprise No. field for a vendor, the upgrade would fail with the following message:
| 50893 |
Document Capture 2023 R2, hotfix 4
Released: November 3, 2023
App version: 12.0.4
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | During document import, the following error could occur:
| 50798 |
Document Capture 2023 R2, hotfix 3
Released: October 24, 2023
App version: 12.0.3
Only released in Business Central online.
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | In the Document Capture 2023 R2 (DC12.00) release, a feature was introduced to automatically delete obsolete templates. Specifically, if a template was disassociated from a document (for example, if the Template No. field was emptied) and it wasn't linked to any other documents, the template would be deleted. This may have unintentionally removed new templates. The automatic deletion feature has now been disabled. | 50548 |
Document Capture 2023 R2, hotfix 2
Released: October 16, 2023
App version: 12.0.2
FOB version: 12.00.02
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| General Application | The following changes only apply to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. When advanced approval for purchase invoices was enabled, the Approval Flow field was not visible on the Purchase Order and Purchase Return Order pages. The below fields were hidden on the purchase order list and card when no documents existed in the purchase order category. Now, these fields are always displayed if Document Capture is configured for the company:
| 50270 |
| General Application | If line recognition was not enabled for a template, the following error occured when users tried to manually capture a line field value:
| 50430 |
Document Capture 2023 R2, hotfix 1
Released: October 6, 2023
App version: 12.0.1
FOB version: 12.00.01
Bug fixes
| Functional area | Description | ID |
|---|---|---|
| Documents and Templates | When you activated the Create/Select Template action in the document journal, the following error could occur:
| 50123 |
Document Capture 2023 R2
Released: October 2, 2023
App version: 12.0.0
FOB version: 12.00
New or changed functionality
| Functional area | Description | ID |
|---|---|---|
| Country and Regional | Document Capture is now available for additional countries in Business Central online. In Continia Docs, you can view the complete list of supported countries: https://docs.continia.com/de-de/continia-document-capture/development-and-administration/countries-and-languages | 45774 |
| Documents and Templates | When transferring captured values to a Purchase Header or Purchase Line field from a template field, the following error occurred if the value was too long for the destination field:
| 14763 |
| Documents and Templates | The possibility to add template header fields to the document overview in the Document Journal has been added. You can configure which master template header fields to show as sortable and filterable columns. Select the Set up Custom Columns action in the Document Journal to configure which template header fields to display. This will open the Custom Fields Card page, where the following fields can be configured:
| 35148 |
| Documents and Templates | You can now enter the date keywords TODAY, WORKDATE, T, and W in the Formula field on the Template Field Card. When activating the Recognize Fields action, the keywords will be converted to today's date or working date, respectively. | 39550 |
| Documents and Templates | A new field, Number of Templates Available, has been added on the page CDC Document List With Image, with the following tooltip:
| 39605 |
| Documents and Templates | When creating a purchase credit memo in the Document Journal, the Due Date is set to the Document Date if a Due Date is not specified. Previously, the workdate was used. | 40349 |
| Documents and Templates | A new template line field, Unit of Measure Code, has been added to the PDF master templates in the Sales, Purchase, and Purchase Order categories. This new field allows you to specify each item's unit of measure code on the sales and purchase document lines. | 43366 |
| Documents and Templates | The below error comment:
| 43512 |
| Documents and Templates | Color mode for TIFF files in Business Central online is now available as Microsoft has addressed the related performance issues. | 45445 |
| Documents and Templates | For the Norwegian localization, two new captions are added in the PDF identification template "KJØP-ID".
| 45668 |
| Documents and Templates | A new field, Prioritize Prepayment as Document Type, has been introduced on the Template Card. This field plays a significant role in determining the document type based on the captions found in the PDF. By default, the document type is identified by the highest-placed caption found in the PDF. Enabling Prioritize Prepayment as Document Type option precedes any prepayment captions found in the PDF, classifying the document as a prepayment invoice, irrespective of other higher-placed captions that otherwise would identify it as an invoice. | 45701 |
| Documents and Templates | By enabling the option Check Item Prices on the template, the item's recognized unit cost is validated against the price specified on the item card. Depending on the costing method specified for the item, the price comparison is conducted in the following manners:
Should the unit cost of the recognized item differs from the special price or unit cost calculated from the item card, a warning is displayed in the comment section. If the Line Discount % template line field contains a valid value or a special discount is configured for the item, the discount percentage is included in the unit cost comparison. | 45706 |
| Documents and Templates | The following fields on the Template Card page are set as additional (hidden by default) and can be displayed by selecting Show more:
| 45719 |
| Documents and Templates | You can now change the configurable message, shown below, to comment type Information.
| 46077 |
| Documents and Templates | When in the Document Journal updating an existing purchase order that has the status Released, a dialog box will now be displayed:
| 46377 |
| Documents and Templates | When in the Document Journal updating an existing purchase order that has the status Pending Approval in the Document Journal under the Purchase Order category, a dialog box will now be displayed:
| 46379 |
| Documents and Templates | When updating an existing purchase order with a status of Pending Prepayment in the Document Journal under the Purchase Order category, a dialog box will be displayed:
| 46706 |
| Documents and Templates | When documents are automatically or manually moved to another company with Document Capture activated, the receiving company automatically completes the vendor identification, template selection, and field recognition steps. This streamlines the workflow, reducing manual steps and ensuring a consistent process. | 46883 |
| Documents and Templates | To prevent the accumulation of unprocessed documents in the Document Journal, a new notification feature has been introduced in Continia Document Capture 2023 R2. Designated administrators, such as an Accounts Payable manager, will receive email alerts regarding unregistered documents, encouraging timely registration and streamlined operations. This proactive approach ensures that the right individuals are alerted at the right time, facilitating a smoother workflow and preventing potential delays. The new functionality allows for proactive management through the following:
| 46884 |
| Documents and Templates | For the North American localization (NA), the PDF master template has been enriched with two new header template fields. The Vendor Remit-To field has been added to the PURCHASE and PURCHORDER categories, and the Customer Ship-To field has been added to the SALES category. | 46885 |
| Documents and Templates | When updating the Quantity, Unit Cost, or Promised Receipt Date in a purchase order, a configurable comment in the Documet Journal is now displayed:
| 46898 |
| Documents and Templates | On the Document Category page, the following changes have been applied:
| 47100 |
| Documents and Templates | In the Document Category page, the tooltips for the following fields have been improved: Image Resolution Tooltip Specifies the DPI resolution for the document image files created from the OCR processing. The image files are copies of the original PDFs received and are used to browse individual PDF pages easily. A higher resolution yields clearer details but increases the file size, potentially affecting loading times. A recommended resolution is 300 DPI (default), which ensures good resolutions and acceptable file sizes. The archived PDF maintains its original colors and resolution and can be accessed whenever needed. Image Color Mode Tooltip Specifies the color mode for the document image files created from the OCR processing. The image files are copies of the original PDFs received and are used to browse individual PDF pages easily. For a swifter display, choose a simpler color mode. Black & White (default): Minimal file size, fastest load. Grey: Moderate file size, balanced load time, and detail. Color: Largest file size, slower load, maximum detail. Lowering the color level in the image file to make them appear faster is recommended. The archived PDF maintains its original colors and resolution and can be accessed whenever needed. | 47101 |
| Documents and Templates | In the Accounts for Amounts page, the following captions have been changed. From:
| 47371 |
| Documents and Templates | The following message has been made configurable:
| 47451 |
| Documents and Templates | The following user interface changes have been applied to the Document Category page:
| 47573 |
| Documents and Templates | Added the possibility to enter incomplete date words (e.g., 'Tod', 'Workd', 'wor', 'to', etc.) for the keywords TODAY and WORKDATE in the Formula field on the Template Field Card. When recognizing fields in the Document Journal, keywords will be converted to today's date or working date, respectively. | 47986 |
| Documents and Templates | It is now possible to configure the following 3 messages as comment type "Information"
| 48028 |
| Documents and Templates | A new field, Business ID, has been added to the Document Journal. The field is hidden by default. Depending on the localization of Business Central, the field displays the following information:
| 48505 |
| Documents and Templates | All localization captions in Template Field Captions for Template Field 'DOCTYPE' have been combined and added to every localization. | 49815 |
| Document Approval | A new option field, Send Email To, replacing the field Forward Emails, has been implemented on the Approval Sharing (DC) page. The following options are available:
| 35032 |
| Document Approval | A new field, Keep On Hold, has been added to the Document Capture Setup / Purchase Approval page. When enabling this, the Remove On Hold dialog won't be displayed to approvers when approving documents that were previously put on hold. Instead, the on-hold status will be kept on the approved documents. | 41835 |
| Document Approval | The possibility to sort by Due Date field in the Purchase Approval Entries page has been added. | 43892 |
| Document Approval | A new action, Put on Hold and Approve, combining two previously separate actions, is added to the Continia Web Approval Portal menu bar. This combined action allows you to put a document on hold and approve it in a single operation. | 44655 |
| Document Approval | The tooltip for the Max. Allowed Approval Date Variance field in the Purchase Contracts Setup page has been updated. The tooltip text is improved and now includes a description of the the default field value: Specifies the maximum allowable deviation between the actual document date and the expected document date for automatic approval of invoices. The expected document date is calculated based on the posting date of the last posted invoice and the price period specified in the purchase contract. If the actual document date deviates beyond this specified threshold, the invoice will not be automatically approved and will require manual approval. When no value is entered, 3 days (3D) is used as the default value. | 45762 |
| Document Approval | When submitting a purchase invoice for approval, an integration with Payment Management that performs payment validation before sending the document for approval has been implemented. | 45823 |
| Document Approval | The action Approval Forwarding has been added to the pages Continia User Setup List and Continia User Setup Card, making it possible to view or edit the approval forwarding setup for the selected user. The action is only visible if all of the following criteria are met:
| 46039 |
| Document Approval | When forwarding a shared approval, the following forwarding options are now available:
| 46419 |
| Document Approval | The Swedish translation of page CDC Purch. Approval Entries is changed from
| 47005 |
| Document Approval | To easily look up posted documents that have been forced or automatically approved, a new field Forced Approval has been added to the Posted Approval Entries page. | 47765 |
| Document Approval | A new field, Include Approval Entries On Hold, has been added to the Document Capture Setup / Purchase Approval. If activated, the reminder and status emails will include approval entries related to the purchase documents put on hold. | 47980 |
| General Application | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The Change Imported Amounts action has been added to the General Journal and Purchase Journal pages. | 30557 |
| General Application | For better readability, the teaching tips have been enhanced by using text emphasis. The text now features bold and italic formatting to highlight key points, ensuring a more effective learning experience. | 32784 |
| General Application | The following tooltips in the Continia Web Portal Card page have been updated. Page field: Code: Specifies the unique code of the Continia Web Portal record, which allows you to use specific Continia websites for selected companies in the same database. Welcome Emails Specifies whether welcome emails for the web approval portal should be sent automatically or manually when exporting the users to the Web Approval Portal. This setting does not affect the welcome email for Expense Management if installed. Web Site URL: Specifies the URL address of the web approval site provided in the approval notifications when sending status emails to the approvers. The Business Central Service Tier account must have access to the URL specified to export the users to the Web Approval Portal. Use Continia Online Web Portal: Specifies whether to use the Continia Online Web approval portal (similar to the cloud OCR capability). Activating the Continia Online Web Portal skips the requirement of installing and supporting an on-premises website. Please note, if you're using Business Central online, you can't use the locally hosted version of the Web Approval Portal – only the Continia-hosted version can be used. Windows Web Service URL: Specifies the Business Central Windows web service URL authenticating users through Windows credentials. Note that if all users in Business Central are Windows users, you only need to specify this URL. However, if you have mixed authentications, you must set up individual Business Central service tiers and enter the URLs for the relevant web service fields. The Windows Web Service URL is the address used for communication between the Continia Web Approval Portal and the Business Central service tier. When using the hosted portal (Continia Online), enter the external address that allows Continia Online to access the Business Central service tier through the firewall/router. Database Web Service URL: Specifies the Business Central Database web service URL authenticating users through database logins (or NavUserPassword). Note that if all users in Business Central are database users, you only need to specify this URL. However, if you have mixed authentications, you must set up individual Business Central service tiers and enter the URLs for the relevant web service fields. The Database Web Service URL is the address used for communication between the Continia Web Approval Portal and the Business Central service tier. When using the hosted portal (Continia Online), enter the external address that allows Continia Online to access the Business Central service tier through the firewall/router. Office 365 Web Service URL: Specifies the Business Central Office 365 web service URL authenticating users through Office 365 logins. Note that if all users in Business Central are Office 365 users, you only need to specify this URL. However, if you have mixed authentications, you must set up individual Business Central service tiers and enter the URLs for the relevant web service fields. The Office 365 Web Service URL is the address used for communication between the Continia Web Approval Portal and the Business Central service tier. When using the hosted portal (Continia Online), enter the external address that allows Continia Online to access the Business Central service tier through the firewall/router. Local Domain Name: Specifies the domain under which the Windows users are created. This parameter only applies to on-premises Business Central environments with the Continia Web Approval Portal installed locally. Filling in the local domain field allows you to log on to the Continia Web Approval Portal using only the username (without typing the Windows domain prefix). Web Service Tenant: Specifies the tenant ID of the current database. This parameter is only required when running in a multi-tenant environment. You can look up the tenant ID in the Business Central server configuration or on the Help and Support page in your Business Central. Azure Tenant ID: Specifies the ID of the Azure AD tenant used for allowing the Continia Web Approval Portal to authenticate users with Office 365 credentials. You can look up the Azure Tenant Id in the Azure Active Directory under the App Registrations section in the Azure Portal. Azure Application ID: Specifies the ID of the Azure AD application used for allowing the Continia Web Approval Portal to authenticate users with Office 365 credentials. You can look up the Azure Application ID in the Azure Active Directory under the App Registrations section in the Azure Portal. Azure Application Key: Specifies the key of the Azure AD application used for allowing the Continia Web Approval Portal to authenticate users with Office 365 credentials. You can create the Azure Application Key in the Azure Active Directory under the App Registrations section in the Azure Portal. Default User Language Name: Specifies the default language for web approval portal users. Users can individually change their settings in the web approval portal to their preferences. Default User Formatting: Specifies the default unit formatting for web approval portal users. Users can individually change their settings in the web approval portal to their preferences. Default Time Zone: Specifies the default time zone for web approval portal users. Users can individually change their settings in the web approval portal to their preferences. Page action Create Web Portal Setup: Create a setup entry with suggested URL values based on the active Dynamics 365 Business Central service tier connection. | 41143 |
| General Application | The Document Viewer factbox has been added to the Document Search page. | 43759 |
| General Application | Two new actions, Include All and Exclude All, have been added to the Document Capture Assisted Setup Guide. These will select/deselect all configuration elements in the Select what to include page when exporting/importing a Document Capture configuration. | 43808 |
| General Application | This feature applies to Business Central on-premises only. A new notification feature has been introduced for users of Document Capture in an on-premises environment. This feature is designed to alert you when the number of pages in your on-premises OCR license approaches its limit, allowing you to take timely action and avoid potential disruptions. For On-Premises OCR:
| 43963 |
| General Application | When copying a company in an on-premises environment, all Continia solutions are automatically deactivated in the new company copy. | 46852 |
| General Application | With the release of Business Central 2023 R1, Microsoft introduced standard functionality to synchronize master data between companies. Certain master data tables in Document Capture are not suited for synchronization between companies since they hold company-specific relations to standard data entities (e.g., Vendors, Customers, Dimension Values, etc.) or posted data. Setting up master data synchronization of the following tables will invoke an error message:
| 47221 |
| General Application | The page/attachment navigation field above the Document Viewer has been enhanced: A new input field allows users to directly select the desired document page in Document Capture or the attachment number in Expense Management. The text/numbering in the navigation field is now formatted as:
| 47442 |
| General Application | Secure Archive in Document Capture and Expense Management assures that digital documents foundational to a company's bookkeeping are preserved in their original form, safe from alterations and deletion, and are traceable throughout the secure retention period defined by the company, in line with the respective country's legislation. This feature includes a built-in log functionality that systematically records each stage a document undergoes, from reception to its conclusive posting in the bookkeeping. If you only want the logging functionality but not the restrictions that come with the Secure Archive, you can activate it independently, thereby providing the flexibility to track document processing without additional secure archive restrictions. | 48491 |
| General Application | It is now possible to enable document logging in Document Capture Setup. Enabling this feature will record the following document-related changes:
| 48612 |
| General Application | Files imported using Document Capture, i.e. imported through categories or added using drag'n'drop, will have a hash (SHA1) associated with them. When running Secure Archive, this information will help determine if the files related to a given historic posting are identical (unchanged) to the time of posting. The hash value is calculated whenever one of the following events occurs:
| 48613 |
| General Application | The following feature is only available in extension versions of Business Central. The action Continia Hub has been added to the home tab for the following pages:
| 48801 |
| General Application | When enabling the Secure Archive functionality, you can define a period in which the posted purchase invoices and posted purchase credit memos can't be deleted. | 48949 |
| Order & Receipt Matching | When a document in the Document Journal cannot be auto-matched because the order/receipt already has been (partly) matched to another document, the following configurable message will be shown:
| 43691 |
| Order & Receipt Matching | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The following user interface improvements have been implemented in the Invoice Matching and Credit Memo Matching pages:
| 45402 |
| Order & Receipt Matching | A new filter action, Filter on Matched Only, has been added to the Invoice Matching and Credit Memo Matching pages. This new feature enables the users to filter on matched purchase order, purchase return order, posted receipt and posted return shipment lines. | 46027 |
| Order & Receipt Matching | The following feature is only available in App based versions of Business Central. The variable IsStrong on page 6085749 CDC Purch. Match Subpage has been changed to a protected variable in order to enable its use in page extensions. | 46407 |
| Platform and Technology | With Document Capture 2023 R2 (12.00), we have released Document Capture for Microsoft Dynamics 365 Business Central 2023 release wave 2 (BC23). Document Capture 2023 R2 (12.00) in Business Central online will not be available for Microsoft Dynamics 365 Business Central 2023 release wave 1 (BC22). You will only be able to use Document Capture 2023 R2 (12.00) in Business Central online when you have upgraded to Microsoft Dynamics 365 Business Central 2023 release wave 2 (BC23). | 32408 |
| Platform and Technology | With the release of Document Capture 2023 R2 (12.00), we have released an upgrade tool that enables direct upgrade to Document Capture 2023 R2 (12.00) from the following versions:
For details, please see Upgrading to Continia Document Capture 2023 R2 (12.00) for FOB versions. | 41919 |
| Platform and Technology | The following feature is only available in Business Central online. In a multi-company environment, you can now activate several companies in one go using Continia Solution Management. | 44226 |
| Platform and Technology | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The permission sets in Document Capture have been migrated from XML format to the Permission Set object. As a result, there is no longer a requirement to assign CSC Basic and CDC-ALL to individual users, as these permissions are now encompassed within the CDC-Capture and CDC-Approval permission sets. | 46197 |
| Platform and Technology | When a company creates a mail account used for forwarding e-mails (e.g. invoice@company.com) to a category end-point in Continia Online, the From Email Address field on the imported documents could, in some situations, contain the forwarding email address and not the original sender email. In order to ensure the From Email Address field is populated with the correct information, please ensure that the forwarding rules are configured on the mail server. Forwarding rules configured in mail clients (e.g. Outlook) may not work. When Microsoft Exchange Server is in use, the guides listed below specify the configuration needed:
| 46878 |
| Platform and Technology | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. On several pages, legacy views have been replaced by modern views. | 47976 |
| Platform and Technology | The Continia Web Approval Portal has been updated to version 1.28.0 | 49897 |
| Platform and Technology | With the release of Document Capture 2023 R2 (12.00), support is provided for the following versions (BC v14 and the three latest versions of Business Central):
| 54580 |
| Purchase Contracts | A new field showing the assigned amount has been added to the Create Purchase Contract page, thus replacing the Default Line details functionality. Selecting the field opens an overview of the lines that will be created for the purchase contract, allowing you to edit the lines before creating the purchase contract without modifying the Accounts for Amounts values on the template. | 42788 |
Added support for defining tax differences on the purchase contract lines using the Statistics page on the Purchase Contract page. The tax differences defined on the purchase contract are currently for information purposes only and are not transferred when registering a document related to this purchase contract. | ||
| Purchase Contracts | Previously, the Contract End Date value was not considered when approving a document (invoice) based on a purchase contract. Now, for a document to be auto approved based on a contract, which has a Contract End Date specified, the document's Invoice Date must be before the contract's end date. | 47367 |
| Purchase Documents | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The Attachments and Incoming Email actions have been added to the pages Sales Invoice, Sales Order, Sales Credit Memo, Posted Sales Invoice, and Posted Sales Credit Memo. | 46061 |
| Purchase Documents | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The Incoming Email action has been added to the Posted Purchase Invoice and Posted Purchase Credit Memo pages. The Attachments action has been added to the Purchase Invoice and Purchase Credit Memo. | 46455 |
| Purchase Documents | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. When you post a purchase order, the related attachments are now available in the Document Viewer on the Posted Purchase Invoice page. | 47825 |
| Purchase Documents | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The additions from Document Capture, like the Amount field on the purchase order list and card, are only active when documents exist in the purchase order category. | 47983 |
- Unfortunately, this feature wasn't included in this release as previously announced, but it will become available with the release of Document Capture 2023 R2 Service Pack 1.
Bug fixes
| Functional area | Description | Id |
|---|---|---|
| Documents and Templates | After merging and resplitting documents, the link to the original email was sometime lost, causing the document to be linked to an incorrect email. | 30275 |
| Documents and Templates | To prevent an overflow error that sometimes occured when recognizing OIOUBL documents configured with the payment method Nemkonto, the following is updated in the config file. For the XML master template OIOUBL the XML Path for the field KORTARTSKODE has been changed: From
| 42889 |
| Documents and Templates | A new table, Business Identification Fields, has been introduced. The table is automatically populated with a refined representation of the following fields from the vendor table:
| 43054 |
| Documents and Templates | The caption of the page CDC Template Subpage was changed from:
| 45734 |
| Documents and Templates | Field captions have been added to the template fields in the Purchase Order category. The following template fields have been updated:
| 47452 |
| Documents 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, and are now configured with Case Sensitive set to TRUE. | 47809 |
| Documents and Templates | In some cases when using Document Search on XML files, the below error was thrown. To ensure a proper result, additional conditional statements are added to the search function.
| 47905 |
| Documents and Templates | The field Check Item Prices is now hidden from the Template Card page for the Sales category. | 48632 |
| Documents and Templates | The following text updates have been applied to the Description field on the Purchase and Sales document categories for the Belgian configuration file:
| 49116 |
| Document Approval | The option Can Edit Posting Lines now allows you to update Gen. Prod. Posting Group when the document is pending approval. | 49356 |
| General Application | The Document Capture Assisted Setup Guide now includes the CDC Data Translation Dimension table when executing the export/import function. Adding the table to the setup guide enriches the export data with the configured dimension values from the Accounts for Amounts page. | 21500 |
| General Application | When the document type (e.g., invoice or credit memo) was mentioned in comments and prompts (errors and confirms messages), the document type was sometimes capitalized. To enhance readability, document types mentioned in comments and prompts will now be displayed in lowercase when more appropriate and logical. | 44903 |
| General Application | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The Payable Account (Allocation) and Purch. Account (Allocation) fields in the Vendor Posting Groups and Vendor Posting Groups (DC) pages in the WebClient were editable in View mode. This issue has been resolved; now, you must switch to Edit mode to modify the contents of these fields. | 45566 |
| General Application | Expanded the progress text variable from 30 to 100 chars in the Storage Migration Status page to prevent the below error in setups with a large number of documents pending migration:
| 46765 |
| General Application | This information only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. If an error occurs while updating the document cues on the role center, the notifications are now only displayed once. | 47791 |
| General Application | This information only applies to Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. When registering documents to a general journal, the Document Viewer was undersized, and it was not possible to adjust the size. | 49147 |
| General Application | When selecting what data to include in the exported configuration file using the Assisted Setup Guide, the following error could occur:
| 49808 |
| Order & Receipt Matching | Removed the Translations action from the Template actions group on the Credit Memo Matching page. | 45584 |
| Order & Receipt Matching | Added new tooltips for the following four fields on the Invoice Matching and Credit Memo Matching pages:
| 47445 |
| Purchase Contracts | When selecting the Translate to Type value for Line Translations, it was possible to choose Purchase Contract. Now, when selecting this value, the following error is shown:
| 49222 |
| Purchase Contracts | When the Purchase Contracts configuration file was not downloaded properly, the no. series code for purchase contracts was blank. | 49748 |
| Purchase Contracts | When uploading an attachment to the purchase contract, using the Web Approval Portal as a reviewer, the following error occurred:
| 49899 |
| Purchase Documents | The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC v21) and newer versions. The Document Viewer factbox and the PDF File action have been added to the General Journal and General Ledger Entries pages. | 43644 |
| Purchase Documents | Previously, when adding attachments on pages such as Posted Purchase Invoice, Posted Purchase Credit Memo, Posted Sales Invoice, and Posted Sales Credit Memo, the documents did not appear in the dropdown menu in the Document Viewer. Now, all attachments are correctly displayed in the dropdown menu. | 46693 |
| Purchase Documents | When running the Batch Post Purchase Invoices function, the VAT Reporting Date will now be updated accordingly on the matched purchase orders. | 47580 |
| Purchase Documents | The following Document Capture related functionality has been made available in the Business Central standard Purchase Journal (page no. 254, Purchase Journal):
| 48521 |
| Purchase Documents | The Business Central Find Entries function did not include purchase documents posted via a general journal when the General Journal Batch was configured with two different number series in the No. Series and Posting No. Series fields. | 48953 |
- Unfortunately, this bug fix wasn't included in this release as previously announced, but it will become available with the release of Document Capture 2023 R2 Service Pack 1.