Detailed Changelog for Continia Document Capture 2024 R2

19/12/2024
70 Minuten Lesedauer

This article lists all new features and bug fixes for each version of Continia Document Capture 2024 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 Receive a notification upon new Document Capture releases in the Continia PartnerZone (only available to partners).

Wichtig

Currently, Document Capture supports BC v14 and the three latest versions of Business Central. This will change with the release of Document Capture 2025 R1 (26.00) in April 2025. Document Capture 2025 R1 (26.00) and all future versions from then on will only support the three latest versions of Business Central.

This version of Document Capture – Document Capture 2024 R2 (25.00) – is the last version with support for Business Central April 2019 (BC v14).

Document Capture 2024 R2, Service Pack 1, hotfix 2

Release date, online: December 19, 2024
App version: 25.1.2
Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	In Document Capture 25.1.1, a regression that prevents environments with Document Capture installed from being upgraded from version 24.x to 25.x was introduced.	62348

Document Capture 2024 R2, Service Pack 1, hotfix 1

Release date, online: December 19, 2024
App version: 25.1.1
Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	When upgrading code from Document Capture 24 to Document Capture 25, the upgrade code automatically adds the template field Standard Invoice Discount to the master template in the Purchase category. If this field had already been added manually, the code would fail with a runtime error.	61750
Order & Receipt Matching	When attempting to register a purchase order, the following error could appear: The length of the string is xx, but it must be less than or equal to 80 characters. Value: <text>: <Document No.> Order No.: <Order No.>	62181
Purchase Documents	When entering a string with a length over 20 in the Our Order No. field, the following error occurred: The length of the string is <string length>, but it must be less than or equal to 20 characters. Value: <string value>.	62265
Documents and Templates	If an email had both XML and PDF files attached to it, deleting one of these files could also lead to the deletion of the related email – even when other documents still existed in the system.	62164
eDocuments	When manually importing a Document Capture configuration file, the following error would appear in certain scenarios: The Continia eDocuments Setup* does not exist. Identification fields and values: Primary Key-*	62226

Document Capture 2024 R2, Service Pack 1

Release date, online: December 6, 2024
Release date, on-premises: December 6, 2024
App version: 25.1.0
FOB version: 25.01

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
General Application	Read-links have been added to Continia Document Capture entries on the Business Central Assisted Setup page, providing direct access to the related Continia Docs article.	60550
Platform and Technology	Events have been added to the solution. For details, see Event Publishers for Document Capture 2024 R2 (25.00).	59844
Platform and Technology	The Continia Web Approval Portal has been updated to version 25.0.5.	61996
Purchase Documents	The following applies to the CH (Swiss) localization only. When creating new a vendor bank account from a QR code, the following fields are automatically populated from the bank directory: Name Address Address 2 City Post Code SWIFT Code	59483

Bug fixes

Functional area	Description	ID
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	The No. Series field in the template header for the purchase order category now supports lookup, similar to those available for invoices and credit memos in the Purchase category. If no valid document type is recognized, the lookup defaults to the number series for purchase invoices.	53126
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	The XML master templates previously had the Ask to Set Default Account No. option set to No by default. This setting has now 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 in the document card that had validation errors were incorrectly marked as valid (OK). This issue has been resolved.	54221
Documents and Templates	Previously, when using the vendor creation wizard, users could select Next Address even when duplicate addresses were detected.	54578
Documents and Templates	When using a formula on the No. Series template header field to define the number series for created purchase documents, an error occurred when recognizing fields in the document journal for credit memo documents. The following error message was displayed in the comments section: No. Series is not correct This issue occurred because the purchase document was incorrectly identified as an invoice during validation of the No. Series template header field.	56198
Documents and Templates	The Search for Value setting on the template field card was previously disabled by default for newly created template line fields.	57178
Documents and Templates	When unchecking a boolean (Yes/No) master template field and confirming updates to templates created from that master template, the update did not apply if the language in use was not English (ENU). This issue has been resolved, and the update now applies correctly regardless of the selected language.	57388
Documents and Templates	When the blank (space) character was configured as the 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	When users attempted to split multiple pages within the same document, the following error message was displayed, requiring the Split and Merge Documents page to be closed and reopened after each split action: You cannot select pages from single-page documents or pages that are the first page in a document.	57519
Documents and Templates	Previously, the asterisk (``) character was not included in the automatic rule creation when Enable Rule Generation* was activated for a template field. Now, the asterisk is included in the automatically generated expression – with the required escape character (`\`). See the examples below: Captured string 123456 generates the rule `\[0-9]{6}\` Captured string 123A456 generates the rule `\[0-9]{3}A\[0-9]{3}\*`	57534
Documents and Templates	When using the QR-Bill Management for Switzerland app in the document journal to scan a QR code containing billing information, the vendor was not identified if the IBAN/QR-IBAN in the vendor bank account card contained spaces. As a result, when registering the document in the document journal, a new vendor bank account with the same IBAN (but without spaces) was created.	57656
Documents and Templates	When performing a lookup of the Customizable Columns on the Document Category page, selecting a column had no effect.	57710
Documents and Templates	In certain cases, the following error message appeared during document recognition when using relative line capture: Overflow under conversion of Microsoft.Dynamics.Nav.Runtime.Decimal18 value to System.Int32	57750
Documents and Templates	When moving XML documents to another company, the preview in the Document Viewer FactBox is now automatically displayed.	57868
Documents and Templates	An empty configurable message was generated if the Multi-Entity Management (MEM) app was not installed in Business Central.	58762
Documents and Templates	The process when selecting Remove Template Field for multiple fields directly from the document journal or document card is now identical to using the Delete action in the Fields section on the template card. Instead of confirming the deletion of each field individually, you can now confirm to delete all selected fields in a single action.	59734
Documents and Templates	When using AI as the document line recognition method, the Search for Value setting was not respected. The columns were still recognized, even when Search for Value was set to False.	59854
Documents and Templates	When using the Create Vendor guide, the configured number series from the vendor template wasn't applied to the newly created vendor.	59925
Documents and Templates	When creating a new customer or vendor using the Create Customer or Create Vendor guide in the document journal, certain values from the newly created customer/vendor were not populated on the related contact card.	60703
Documents and Templates	When using an XML Path in a template field, an error occurred when capturing a value exceeding 1024 characters. The error message displayed was: The length of the string is <String Length>, but it must be less or equal to 1,024 characters. Value: <File name>	60545
Documents and Templates	On the Purchase Invoice page, using Next or Previous in the Document Viewer FactBox for a multi-page document did not navigate to the subsequent page as expected.	61335
Documents and Templates	The Delete Blanks field in the template field table was incorrectly displaying the Danish translation – instead of the appropriate language for the user's localization.	60806
Documents and Templates	The Set Up Template Field assisted guide has been enhanced to allow the setup of new template fields as either header or line fields. Previously, when using CTRL and selecting a value or caption in the document viewer to create a new header template, the following error message would appear: Type must be equal to 'Line' in Template Field: Template No.=T000002, Type=Header, Code=STDINVDISC. Current value is 'Header'.	60755
Documents and Templates	The following issues were observed in certain cases when recognizing document lines in a PDF: The last line of the document was not recognized. The bottom line of the document was duplicated and thereby captured twice.	60508
Documents and Templates	During document import, if a template was already available in another company for the same vendor, the user was prompted with the following dialog: A template for has been found in company , do you want to copy this template? Previously, selecting No stopped the process. This has been changed to instead create a new template from the master template in the current company.	60513
Document Approval	To maintain approval flow integrity, inserting an approver in an approval flow now requires selecting an approver ID.	57099
Document Approval	This update applies only to Business Central app versions supported by this Document Capture release. You can find the list of supported versions in Supported On-Premises Versions for Document Capture. When deleting an approval sharing configuration record created using the Set up Out of Office feature, the following error message was displayed: JIT loading of field(s): 'Display Order, Forward E-mails' failed for table: 'Approval Sharing' identification values: 'Owner User ID=<User ID>, Shared to User ID=<Shared User ID>, Sharing Type=Out of Office, Valid From=<From Date>, Valid To=<To Date>'	57893
Document Approval	An overflow error occurred when users opened the Purchase Approval Entries page if the vendor name contained 99 or more characters.	59610
Document Approval	When sending the status email to approvers, the Amount Incl. VAT column incorrectly displayed zero for purchase orders. This issue has been resolved, and the correct amounts are now shown.	58523
Document Approval	When the Type was set to Resource on the Approval User Group Permissions page, the permission type incorrectly displayed as 7 in the Permissions FactBox on the Continia User Setup Card. This caused the following error when attempting to open the document in the Web Approval Portal after sending an approval request: There is an error in XML document (1, 1544)	59713
eDocuments	When sending an eDocument using a network profile (cbc:ProfileID) different from the default one in the XML structure, the profile was not updated in the XML document – and the default profile was used instead. The cbc:ProfileID in the XML document is now correctly set based on the network profile used.	61432
eDocuments	When sending a Peppol BIS3 electronic invoice through Continia Delivery Network, the Invoice/cac:PaymentMeans/cbc:PaymentMeansCode value was incorrectly set to 31 for bank account payments. This has been corrected to 30.	61700
eDocuments	The following document reference-related issues have been addressed: The Buyers Reference on the eBilling header is now populated with the value from the Your Reference field on the posted sales invoice. Prevented a potential overflow issue on a sales invoice when populating External Document No. with more than 30 characters.	61555
eDocuments	When sending an invoice through the Continia Delivery Network, a validation error appeared in the Validation Log on the eBilling Outgoing Document Card page: Tax Scheme ID is mandatory.	61242
eDocuments	Import of regional Payment IDs is now supported in the localizations below: eBilling NO (Peppol): A new template field, KID, has been added to the master template to capture the payment reference from the XML document. eBilling DK (Peppol and OIOUBL): A new template field, FIK, has been added to capture the payment reference. Update the XML structure for OIOUBL to ensure proper capture. eBilling SE (Peppol): A new template field, OCR Nummer, has been added to capture the payment reference. All fields are created using the same field codes as in XML import, so captured values will be transferred to the purchase document in the same way.	61607
eDocuments	When sending an invoice through the Continia Delivery Network, the Invoice/cac:AccountingCustomerParty/cac:PartyName/cbc:Name XML element incorrectly displayed the Customer No. instead of the Customer Name.	61235
eDocuments	Multiple issues related to OIOUBL Credit Note and Invoice validation when sending documents through the Continia Delivery Network have been resolved. These include: Validation errors caused by incorrect formatting in the Invoice and CreditNote elements. Missing or incorrectly populated mandatory fields in the OIOUBL document structure. Validation failures for specific business rules when sending OIOUBL documents. Added support for exchange of Instruction ID and Vendor Account No. relevant for importing FIK payment IDs. These issues have been fixed to ensure OIOUBL credit notes and invoices are validated and sent correctly according to the standard requirements.	61450
eDocuments	When sending an invoice through Continia Delivery Network in the Netherlands localization, the following error appeared: Microsoft.Dynamics.Nav.Runtime.NavFieldRef variable not initialized.	61331
eDocuments	When sending a Peppol eDocument from a Swedish identifier (SE:ORGNR) through the Continia Delivery Network, the following validation error appeared in the Validation Log on the eDocument card – accessible via the eDocument Status field: <Vendor/Customer> Endpoint Scheme is mandatory. Action Required for Existing Data: While this fix addresses new data, existing mappings may need to be corrected manually. To resolve the issue, follow these steps: Go to the Continia eDocuments Setup page. Under XML Structures, select the PEPPOLBIS3INVOICE code and open the XML structure. Apply a filter to the XML Path field: cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID. Select Code Lists, find the appropriate code list value for the endpoint scheme, e.g., 0007 for SE:ORGNR. Update the Translate to Value field with the correct scheme, e.g., 0007, and then select OK.	60688
eDocuments	When opening the Document Capture role center, the number displayed in the eDocuments Requiring Attention tile was incorrect.	58852
eDocuments	When sending a posted credit memo through the Continia Delivery Network as a Peppol Credit Note (BIS 3.0) document, validation errors appeared in the Validation Log on the eBilling Outgoing Document Card page – accessible via the eDocument Status field. The errors were: VAT Amount (VAT Currency) is mandatory. VAT Currency Code is mandatory.	60950
eDocuments	When sending a Peppol sales invoice with negative line quantity or price, the validation failed.	60360
eDocuments	The template field Customer Contact (EXTCONTACT) in the sales category has been updated in the default configuration to automatically be added to new templates.	57594
eDocuments	Previously, when sending an invoice with Procurement-BilSim selected as the network profile for the OIOUBL invoice in the XML structure, an error occurred if the receiver was registered to only receive invoices with the NES5 profile. The error message was: You are trying to send a network document (Simpel Fakturaproces - Procurement-BilSim-1.0) to Customer , who does not support receiving this type of document. Please go to the Continia eDocument Setup page on the Customer to see more. It is now verified whether the selected Procurement-BilSim network profile is supported by the receiver. If not, and both the sender and receiver support NES5, this profile will be used instead.	60266
eDocuments	Additional documents are now correctly attached when sending eDocuments.	60267
eDocuments	In certain cases, when the original file type was XML, the preview image in the Document Viewer was not displayed, and the following error occurred: There is an error in XML document (1, 1544).	60847
eDocuments	The issue causing the error There is an error in XML document (1, 1544) has been resolved. The permission type is now correctly displayed on the Continia User Setup Card, allowing approval requests to be sent without errors. Additionally, when handling XML files with a large number of lines (i.e.: over 1,000), the Document Viewer FactBox now correctly displays 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	When updating storage settings in the Document Capture setup and selecting Azure Blob Storage, the page now only displays fields related to the configuration of Azure Blob storage. Previously, fields related to file system storage were also visible.	57183
Order & Receipt Matching	When manually matching to a receipt line with item tracking configured and then updating the quantity, the following error appeared when attempting to preview post the registered document: The record in table Tracking Specification already exists	55660
Purchase Contracts	The tooltip for the Send Status Email to Purchase Contract Reviewers action in the role center previously ended with the word 'null'.	57676
Purchase Documents	When attempting to view document attachments using the View in List action in the Documents FactBox, the following error message was displayed: The record is not open.	51330
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: Document journal Document card Document search Documents FactBox on the Vendor Card Documents FactBox on a posted purchase invoice	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 in the Accounts for Amounts page were not copied to the created general journal line. Additionally, the VAT Prod. Posting Group field in the Line Translation page was affected.	56620
Purchase Documents	This update applies only to Business Central app versions supported by the Document Capture release. You can find the supported versions in Supported On-Premises Versions of NAV and Business Central. Attachments were missing from general ledger entries when postings were made through the General Journal or Purchase Journal using General Journal Batch with differing No. Series and Posting No. Series.	57664
Purchase Documents	When using Customizable Columns in the document journal and importing a purchase XML document, the following error was displayed: The changes to the Document record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again.Identification fields and values:No.=''	57909
Purchase Documents	Netherlands localization only: When registering an XML purchase document in the document journal, the fields Doc. Amount VAT and Doc. Amount Incl. VAT were not populated in the purchase invoice or credit memo header. This change applies only to new installations of Document Capture. For existing installations, ensure the After Step 1 field on the Codeunit FastTab in the Template Card for all XML master templates is set to CDC Purch. Doc. - After Step 1.	58087
Purchase Documents	On the General Ledger Entries page, it was not possible to delete attachments that were added on General Journal or Purchase Journal lines before posting.	58492
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
Purchase Documents	When creating a new purchase order via the document journal, the following error message appeared if an order line had a 100% line discount: No Account has been configured for Amount Excl. VAT.	59177
Purchase Documents	Czech Republic localization only: When registering a document using the Advance Letter category, the captured value in the template header field Posting Description was not transferred to the Posting Description field on the purchase advance letter.	60149
Purchase Documents	If Amount Validation on Post is enabled in Document Capture Setup, and the Journal Template Name and Journal Batch Name fields are filled out under the Purchase category, posting a manually created general journal entry with drag-and-drop attachments for a vendor account type would result in the following error: The journal lines with Document No. are linked to Document Capture Document.	60204
Purchase Documents	Previously, if more than one Drag and Drop category was configured and you tried to register a document in the purchase order category, the following error was displayed: Document: The Document does not exist. Identification fields and values: Entry No.='2'	60840
eDocuments	When importing electronic documents using Continia eDocuments, document lines were recognized even though the values captured were not valid – or no value was found for a field configured as required.	60191

Document Capture 2024 R2, hotfix 2

Release date, online: November 7, 2024
App version: 25.0.2

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
Documents and Templates	A formula to sum or subtract other fields would result in a zero value if any of the involved fields had a zero value.	60997
eDocuments	When handling XML files containing a lot of lines (e.g.: more than 1,000), the Document Viewer FactBox would not display the HTML representation of the file.	61168
General Application	If the Template Nos. field on the Document Capture Setup page had no value, the related company was skipped during the upgrade process.	61229

Document Capture 2024 R2, hotfix 1

Release date, online: October 30, 2024
App version: 25.0.1

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
eDocuments	In some cases, the preview image didn't load on purchase invoices if the original file was an XML.	60847

Document Capture 2024 R2

Release date, online: October 1, 2024
Release date, on-premises: October 21, 2024
App version: 25.0.0
FOB version: 25.00

New or changed functionality

Functional area	Description	ID
Country and Regional	The following applies only to the Spanish localization. If you have configured payment days on the Company Information page for the selected company or vendors, the document journal now calculates the document's due date based on both the vendor’s payment terms and on the configured payment days. If payment days are not configured, the due date is calculated solely based on the vendor’s payment term. For payment days to be considered when evaluating the recognized due date, the Show Default Field Value setting must be enabled on the Document Category card. Additionally, if the Search for Value setting on the template header field Due Date is disabled, the expected due date is calculated and shown based on the document date and on the vendor's payment terms – including the configured payment days.	53256
Country and Regional	The following applies only to the Czech localization. A new category, ADVLETTER, has been added to handle advance letters, also known as prepayments. For more information, see Advance Letters for the Czech Republic.	53271
Document and Templates	It is now possible to delete multiple template fields in one go from the template card by marking the fields and selecting the Delete action on the Fields FastTab.	14724
Document and Templates	On the Document Category card, the importance of Image Resolution on the OCR Processing FastTab was changed from standard to additional.	19970
Document and Templates	The fields From Email, Recipient Date Time, and Subject have been added to the Split and Merge page. Please note that these fields are hidden by default.	24413
Document and Templates	The option Use Default from Purchases & Payables Setup has been added to the Posting Date field on the Purchase Documents FastTab in the template. This option respects the Default Posting Date setting on the Purchases & Payables Setup page and sets the posting date in the purchase document header as follows: Work Date - the current work date set in Business Central. No Date - an empty value.	24566
Document and Templates	Barcodes in the Item References (item cross references) list are now used for translating recognized item numbers in the document line on the document card.	38783
Document and Templates	Added vendor bank account validation for Australian bank accounts (EFT BSB).	40793
Document and Templates	A caption suggestion notification feature has been introduced to the document journal. Master PDF templates eligible for caption suggestions now appears in a notification specific to the document category selected in the document journal. The field Caption Suggestions Notification, with the formula data type, has been added to the Document Capture Setup page to specify how often caption suggestion notifications should be shown. For example: 1D - the notification is shown daily 2W - the notification is shown every two weeks 1M - the notification is shown monthly	40910
Document and Templates	The action Special Prices and Discounts Overview has been added to the Line action group in the Lines section on the Document Card page. This allows you to view the purchase or sales prices and discounts for the selected item line when its recognized price differs from its calculated special price.	48409
Document and Templates	The message displayed on the Configure Default Account page, when populating the template field Account No., has been simplified.	48473
Document and Templates	The Category Code setting is no longer visible on template cards because it's not possible to edit the category from these cards.	48572
Document and Templates	Templates that are no longer in use can now be hidden from the embedded template lookup in the document journal and on the document card by enabling the Blocked setting on the template card. Blocked templates are ignored when Document Capture analyzes the document to determine which template to select. Note that a blocked template still appears in the full lookup page when Select from full list is selected.	48829
Document and Templates	A new template field, Invoice Discount Amount, has been added to the master template in the Purchase invoice category. If populated during capture, the value is transferred to the standard Business Central field Invoice Discount Amount on the created invoice during registration of the document.	49611
Document and Templates	If a purchase document from Document Capture and an expense registered in Expense Management have the same Invoice Date (plus/minus 3 days), and identical Currency Codes and Amounts Incl. VAT, Document Capture displays the following warning: WARNING: A potential duplicate transaction exists in Expense Management (Expense Entry No.=[Expense Entry No.], Amount=[Expense Amount], Currency=[Currency Code], Document Date=[Expense Document Date])	53235
Document and Templates	It is now possible to view the expected default values that will be used when registering the Document Capture purchase or sales document. If a value is captured in any of the fields listed below, it is transferred to the purchase or sales document. However, these fields on the registered document may also be populated by data taken from the vendor/customer, responsibility center, purchaser/salesperson code, etc. The expected default value is displayed in brackets next to the field name in the header section for the below fields, both in the document journal and on the document card. Purchase invoice category Approval Flow Code Responsibility Center Purchaser Currency Code Vendor Bank Account No. Vendor VAT No. Vendor Phone No. Dimensions 1-8 Sales category Responsibility Center	53239
Document and Templates	When selecting the Assisted Template Field Setup Guide in the Document Journal and Document Card, you now have the option to specify the template field type as either header or line, making it easier to create new line template fields. Consequently, the Create new Template Field action and the Template action group in the Document Card Lines subpage have been removed.	53460
Document and Templates	The event OnBeforeSetRetentionPeriod(ToDate,Handled) has been added to the codeunit CDC Data Maintenance Mgt. This makes it possible to bypass the two-year limit on deletion of document words and document values specified in the Retention Perion (Years) field on the Document Capture Setup page.	54734
Document and Templates	A new translation has been created with Translate From = * and Translate To = [empty]. The above change has been applied to all localizations for the following master template headers fields: Purchase category Invoice No. Invoice Date Due Date Purchase order category Order Date Due Date Sales category External Document No. Order Date	57516
Document and Templates	The setting Blank Zero has been hidden from the Template Field Card, as values equal to zero are always blanked in Business Central. Therefore, the setting Blank Zero had no effect.	57541
Document and Templates	When selecting the Remove Template Field action in the document journal or document card, the confirmation message is now the same as when selecting the action Delete in the Fields section of the template card.	57573
Document and Templates	When processing sales documents, templates can now utilize AI data in the same way as with purchase documents. This includes line recognition suggestions on the document card and the ability to create a customer based on the document content.	57744
Document and Templates	The action Change Category has been added to the Document action group in the document journal. This action lets you change the category of open documents, provided that the categories share the same source record table, e.g., vendor or customer.	58436
Document Approval	Document comments added prior to registration are now available as approval comments on purchase invoices, credit memos, and purchase orders after the document is registered. To activate this feature, enable the Copy Document Comment to Approval Comment setting under Document Capture Setup > Setup > Purchase Approval – along with an active approval flow for the document type.	21183
Document Approval	A new cross-company dashboard has been introduced in the Continia Web Approval Portal. This feature allows users to view all approval documents from all companies they have access to, including purchase contracts.	53214
Document Approval	When using advanced approval, documents are routed to a specific approver based on the dimension values and amounts on the document lines. Depending on the approval configuration, the user could, as an example, be allowed to approve the dimensions used on document line 1 (e.g.: Department - Sales), but not the dimensions used on document line 2 (e.g.: Department - Administration). Up until now, it has not been evident what document lines the user was actually approving. With this change, the document lines that can be approved by the current user are marked in bold. The change is available on the Purchase Approval Entries page in Business Central, as well as on the Web Approval Portal.	53258
Document Approval	Approval flow codes are now supported when using advanced approval workflows. Approval flow codes can be applied to the following document types and corresponding advanced approval workflows: Purchase invoice Purchase credit memo Purchase order Purchase return order	53261
Document Approval	When migrating from Business Central on-premises to Business Central online and utilizing the Web Approval Portal, an invalid configuration could be migrated. This could block the export of users to Continia Online. Now, the web portal configuration is sanitized to make sure that users can be exported to Continia Online.	54937
Document Approval	The following change only applies to Business Central online. When exporting users, the current Web Approval Portal setup is validated to ensure that it is supported in Business Central online. If the setup if not supported, the following error is shown: Web portal code is not supported in Business Central Online.	54943
Document Approval	Pending purchase contracts approval entries can now be handled on the new cross-company dashboard in the Continia Web Approval Portal.	58411
General Application	By enabling the Check Item Prices option on the template in the Sales category, the item's recognized unit cost is validated against the price specified on the item card. If any special prices or discounts are configured for the item, the price check is conducted against the relevant special price or special discount. Should the unit cost of the recognized item differs from the special price or unit price 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.	47648
General Application	To simplify the user interface in the Document Capture Setup, the actions from the Approval Setup action group have been merged into the Setup action group.	53789
General Application	With Binary Stream MEM installed and the entity dimension value was missing in the Document Journal, the following message was shown in the comment section: Multi Entity Company is not specified. The message has been updated to include fields from the Multi-Entity Management Setup: MEM <Entity Label> is not specified (<Entity Dimension>).	54434
General Application	The following template header and line fields have been added to support the integration between Continia Document Capture and Continia Sustainability: Environmental Account Type Environmental Account No. Emission Type Emission Code Emission Unit Type Emission Unit Code Emission Quantity For more information, see Continia Sustainability and Document Capture.	54621
General Application	When using the standard Business Central functionality Merge Duplicate Records, any Document Capture documents associated with the vendors or customers being merged are also included in the merging process. Note that moving Document Capture documents is only supported in Business Central 2024 release wave 1 (BC v24.00 and newer).	54671
General Application	Added identification rules to the XRECHNUNG-ID XML identification template to support XRechnung version 2.3 and 3.0.	56585
General Application	When selecting Account Type (G/L account or item) and Account No. in the document header – or selecting Translation to Type and Translation to No. in document lines in the document journal –, the following Continia Sustainability fields are populated with values found either in the G/L account card or item card: Environmental Account Type Environmental Account No. Emission Type Emission Code Emission Unit Type Emission Unit Code Total Emission Quantity For documents with templates where Continia Sustainability template fields are not present, but the assigned G/L account or item in the document journal has values in the Continia Sustainability fields, the following configurable comment is shown: WARNING: Continia Sustainability values defined in the <Account Type> <Account No.>. Please add Sustainability template fields using Add Template Field. For more information, see Continia Sustainability and Document Capture.	57429
General Application	Lookup and validation have been implemented for the following header and line template fields to support the integration between Continia Document Capture and Continia Sustainability: Environmental Account Type - shows the available option values for an environmental account type in the purchase line. Environmental Account No. - looks up the associated values related to the environmental account type. Emission Type - shows the available option values for an emission type in the purchase line. Emission Code - looks up the associated values related to the emission type. Emission Unit Type - shows the available option values for an emission unit type in the purchase line. Emission Unit Code - looks up the associated values related to the emission type. For more information, see Continia Sustainability and Document Capture.	57431
General Application	When Continia Sustainability is activated, the following template header and line fields are created in the purchase master templates of the Purchase category in Document Capture: Environmental Account Type Environmental Account No. Emission Type Emission Code Emission Unit Type Emission Unit Code Total Emission Quantity If there are existing template fields that share the same code, a popup with the following two options is shown: Update the existing template field on the Template Field Card by updating the following fields on the page: Field Name Data Type Field In Purchase Line Codeunits (action button): Lookup Is Valid Validate Manually handle field conflicts. For more information, see Continia Sustainability and Document Capture.	57455
General Application	If the following Continia Sustainability template fields are populated in the document journal, their values are stored either in Account for Amounts (for header fields) or in Line Translations (for line fields): Environmental Account Type Environmental Account No. Emission Type Emission Code Emission Unit Type Emission Unit Code For Line Translations, only G/L accounts are supported. For more information, see Continia Sustainability and Document Capture.	57532
General Application	When using a G/L account or an item in Accounts for Amounts, all related fields from Continia Sustainability are automatically added. The same goes for line translations. When recognizing lines in a Document Capture document – and the recognized lines translate to a G/L account or item –, the default values from Continia Sustainability are automatically added to the related template fields.	58611
General Application	To align with standard Business Central, the page Document Capture Assisted Setup Guide has been renamed to Set Up Document Capture.	58705
Order & Receipt Matching	The Order Matching page is introduced to the purchase order category, and can be used when updating existing documents. Matching purchase order lines are highlighted, making it easier to see which lines will be updated.	53257
Platform and Technology	With the release of Document Capture 2024 R2 (25.00), support is provided for the following versions (BC v14 and the three latest versions of Business Central): Business Central April 2019 (BC v14) Business Central 2023 release wave 2 (BC v23) Business Central 2024 release wave 1 (BC v24) Business Central 2024 release wave 2 (BC v25)	54586
Platform and Technology	Events have been added to the solution.	59844
Platform and Technology	The Continia Web Approval Portal has been updated to version 25.0.1.	59846
Purchase Contracts	The field Configure Purchase Contract as the Default Account has been added to the Create Purchase Contract page when creating a purchase contract from the document journal or document card. Enabling this field sets the newly created purchase contract as the default account on the document's template.	56212
Purchase Contracts	The review process for purchase contracts has been completely refactored into an approval process and aligned with the approval flow for other document types. After upgrading to Document Capture 2024 R2 (25.00), the status of all existing purchase contracts that have already been reviewed will be set to Released (approval status), while all others will be set to Approval Needed and must go through the approval process.. Please refer to the article Purchase Contract Approvals for a description of the functionality.	56986
Purchase Contracts	A new action, Match To Purchase Contract, has been added to both the document journal and the document card. Selecting this action opens the Purchase Contract Selection page, which displays all of a vendor's purchase contract lines, allowing you to link the document to the related purchase contract and its lines.	56993
Purchase Documents	When selecting the Find Entries action from a purchase allocation, the related Document Capture document is now included in the search result. Previously, the search results only included the related G/L entries.	14633
Purchase Documents	The option Use same setting as Send for approval has been added to the Amount Validation on Post field on the Document Capture Setup page. If selected, the level of amount validation conducted when posting is determined by the value chosen in the template's Amount Validation option field on the Purchase Documents FastTab.	46397
Purchase Documents	When the registration of a Document Capture document updates an existing purchase order or purchase return order, the purchase document is automatically archived prior to the update. This automatic archiving happens when: Registering a Document Capture document as an invoice or credit memo using the Match & Update Order or Match & Update Return Order register options in the purchase category. Registering a Document Capture document using the Create or Update Order, Update Order, or Update Order Receipt register options in the purchase order category. The archived version of the purchase order includes a comment line specifying the document number and, if available, the vendor order number of the document that updated it.	47254
Purchase Documents	Previously, it was possible from a general journal or purchase journal to delete attachments associated to a posted ledger entry having the same document number as the unposted journal entry. Now, it is only possible in the journals to view the attachments that are related to the posted entries. In addition to the above change, the attachments added to an unposted general or purchase journal with the same document number as the posted entry are viewable from the general ledger entries but can't be deleted.	54349
Purchase Documents	With the introduction of allocation accounts in Business Central, postings from documents and journals can be split across different G/L accounts and dimensions. When recognizing lines, Document Capture now supports the registration of documents with the account type Allocation Accounts in Accounts for Amounts, Translate to Type, and Translate To No. Currently, only allocation accounts with the account type set to Fixed are supported. When registering a document, the purchase lines of type Allocation Account are automatically expanded to the underlying account types using the standard function Generate Lines From Allocation Account Line – which is available on the standard purchase document pages. Note that the validation of the total amount incl. VAT/GST is not carried out when allocation accounts are in use. This is due to Business Central not calculating the VAT/GST amount on documents containing lines with allocation accounts.	54844
eDocuments	Added a job queue entry, eDocuments metadata update, which is scheduled to run once a day at a random time between 06:00PM and 05:00AM. This job queue is used for updating participations and networks metadata. Two new fields have been added to the Continia eDocuments Setup page: Update Metadata Automatically: A boolean field for enabling or disabling the job queue entry. Metadata Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.	51250
eDocuments	Added a job queue entry, eDocuments document update, which is scheduled to run every 30 minutes. This job queue is used for updating document statuses, download new documents and receipts. Two new fields have been added to the Continia eDocuments Setup page: Update Documents Status Automatically: A boolean field for enabling or disabling the job queue entry. Documents Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.	51251
eDocuments	To better associate an eDocument with its related business document, the Source Document column has been added to the eDocument Requiring Attention page, displaying the related business document. Additionally, the Business Record ID column has been added to both the eOrder Document and eBilling Outgoing Document Card pages.	54507
eDocuments	The XML structure for XRechnung 3.0 has been added for both sales and purchase invoices and credit memos.	54785
eDocuments	The following changes have been made when sending Peppol and OIOUBL sales invoices and credit memos: Improved handling of discounts. Improved handling of multiple tax rates. Added support for comment lines.	54789
eDocuments	Introducing two new fields: Use Document Information for Customer Party on the Customer eDocument Setup page. Use Document Information for Seller Party on the Vendor eDocument Setup page. When exporting a document, you now have the option to retrieve the customer or seller party details directly from the eDocument rather than from the customer/vendor card.	54901
eDocuments	A new field has been added to the Continia eDocuments Customer Setup page to enable automatic sending of eDocuments for the customer: Send E-Documents Automatically: An option field specifying which customer's documents will be sent automatically upon posting. The available options are: [Empty] (default value): No documents will be sent automatically. All: Sales and service documents will be sent automatically. Sales Documents: Sales invoices and sales credit memos will be sent automatically. Service Documents: Service invoices and service credit memos will be sent automatically. A new field has been added to the Continia eDocuments Vendor Setup page to enable the automatic sending of eDocuments for the vendor: Send Purchase Orders Automatically: A boolean field specifying whether vendor's purchase orders will be sent automatically upon release.	55079
eDocuments	To ensure better navigation between eDocuments pages following adjustments were made: The following actions have been added on several eDocuments-related pages to help locate business records: Find entries eDocument Card Open in Document Journal To display information about the related business document, the Business Record field has been added to the General field group on the following pages: Incoming eBilling Document eBilling Response eOrder Response. You can select the value of Business Record to open the related business document, if it's available. The field Business Record ID has been renamed to Business Record on the following pages: eBilling Outgoing Document Card eOrder Document.	55317
eDocuments	Added the action Open XML File to the following pages: Incoming eBilling Document eBilling Outgoing Document Card eBilling Response eOrder Document eOrder Response	55318
eDocuments	The possibility to view customers and vendors eDocuments receiving capabilities in the network is added to Continia eDocuments: A new factbox, eDocuments Receiving Capabilities, has been added to the Continia eDocuments Vendor Setup and Continia eDocuments Customer Setup pages to display which documents the receiver can accept. A new action, ReCheck eDocuments Receiving Capabilities, has been added to the Continia eDocuments Vendor Setup and Continia eDocuments Customer Setup pages to update the receiving capabilities from the network. On the Continia eDocuments Setup page, a new Update Documents Receiving Capabilities field group has been added to the Automations FastTab. These settings allow you to enable the job queue for updating eDocuments receiving capabilities and view the job queue status. The error messages shown when attempting to send eDocuments and failing due to the receiver's eDocuments receiving capabilities have been updated: When the receiver is not registered on the network Previous message text - You are trying to send a network document (<eDocument type>) to <Customer/Vendor> <Customer/Vendor No.>, who is not registered in the network. New message text - You are trying to send a network document (<eDocument type>) to <Customer/Vendor> <Customer/Vendor No.>, who is not registered in the network. Please go to Continia eDocument Setup page on the <Customer/Vendor> to see more. When the receiver is not able to receive the type of eDocument Previous message text - You are trying to send a network document (<eDocument type>) to <Customer/Vendor>* <Customer/Vendor No.>, who does not support receiving this type of documents.* New message text - You are trying to send a network document (<eDocument type>) to <Customer/Vendor> <Customer/Vendor No.>, who does not support receiving this type of documents. Please go to Continia eDocument Setup page on the <Customer/Vendor> to see more. Microsoft introduced actionable messages in Dynamics 365 Business Central in the 2023 Release Wave 2, making it possible to directly open specific pages. The above error messages now include an Open <Customer/Vendor> eDocuments Setup action, allowing you to open the Continia eDocuments Vendor Setup or Continia eDocuments Customer Setup page for the specific recipient.	55724
eDocuments	For better traceability across eOrder and eBilling documents within the same eCase (an electronic case that groups related documents together for processing), the following fields are now being transferred: Buyer's Order Reference Line ID Buyer’s and Seller’s Item Reference This ensures that a purchase invoice received by the buyer will include relevant references to the purchase order line and the buyer's item numbers.	56618
eDocuments	eDocuments is now an integral part of Document Capture, rather than a feature package. This means that eDocuments is fully embedded, and activation of the feature is no longer needed, as the functionality is available with the Essentials module.	56641
eDocuments	The field Alternative Electronic Format has been introduced on the eDocuments Electronic Formats page. This field allows you to set an alternative electronic format code to support different document types. For example, you can now send EHF Orders and Peppol Invoices, or Peppol Orders and XRechnung Invoices.	56733
eDocuments	The field Order Line No. was added to the eBilling Lines. The field has been added with default visible false. Order Line No. is a requirement when sending eDocuments to a Dutch customer.	58109
eDocuments	The Set Up eDocument assisted guide has been made searchable. The guide helps users migrating templates created for use with Continia XML Import to templates that can be used with Continia eDocuments.	59006

Bug fixes

All relevant bug fixes released in service packs and hotfixes up to Service Pack 2, hotfix 1, for Document Capture 2024 R1 (24.00) are also included in Document Capture 2024 R2 (25.00). The description of these bug fixes is not repeated on this page.

Functional area	Description	ID
Document and Templates	In the document journal, the default setting of the comment No Account has been configured for Amount Excl. VAT (applicable to Amount Excl. VAT 2, 3, and 4) has been changed from a warning to an error.	48187
Document and Templates	The field Identified By in the document journal now shows all search texts used for identifying the vendor. Previously, the Search Text field was not populating all relevant search texts.	50332
Document and Templates	The OCR Language field on the Document Category card is now hidden if Use Cloud OCR is enabled in the Document Capture Setup.	53275
Document and Templates	It is now possible to use the formulas TODAY and WORKDATE in the Formula field on the template field card. In combination with the Calculate Date field, this allows template date fields to be configured to use today's date or the work date, adjusted by a positive or negative date value.	55821
Document and Templates	Previously, deleting a captured line in the document card caused the add-in and the document lines to become out of sync in the web client. This issue has now been resolved, and both remain in sync.	57574
Document and Templates	The heading Advanced Recognition Settings on the template field card is now only visible when selecting Show More Fields.	58100
Document Approval	The Approval Sharing page has been renamed to Approval Sharing (DC) to distinguish the Document Capture page from the Expense Management page.	57716
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: You must install the on-premises version of Continia Document Capture to use server-side resources, such as file system and assemblies. This check has been disabled because the on-premises application isn't required when using the Continia file service.	55882
General Application	The Document Sharing page has been renamed to Assigning Sharing. Additionally, the following translation changes have been made to the Continia User Setup page: Shared to this user is now Approval Shared to this User Shared to other users is now Approval Shared to Other Users Delegation shared to this user is now Assigning Shared to this User Delegation to other users is now Assigning Shared to Other Users Missing tooltips have been added to Delegation shared to this user and Delegation to other users	56940
Purchase Contracts	The following fields have been removed from the Purchase Contract card: Create Posting Description Line Posting Description Purchase Contract Description The fields are replaced by the new option field Populate Line Description From, which specifies whether a separate purchase line with description is created when registering the document – and where the description is taken from. The options are: Empty (default value) - a purchase line with the posting description is not created. Document Description - a purchase line is created with the posting description from the invoice, if it is not empty. If the invoice posting description is empty, the purchase contract description is taken instead. Contract Description - a purchase line is created with the purchase contract description.	52034
Purchase Documents	If the Secure Archive is enabled, the document control log displays the following warning on the Posted Purchase Invoice and Posted Purchase Credit Memo pages when a document attachment was deleted: One or more files have been deleted since posting. This warning has been changed to: One or more files linked to this document have been deleted.	53646
Purchase Documents	The Document Viewer and Documents FactBoxes are now visible on the General Ledger Entries page.	58385
Purchase Documents	The following error no longer occurs when more than one drag-and-drop category is in use, and you attempt to open a purchase order: The Document does not exist. Identification fields and values: Entry No.='1'	58808
eDocuments	When sending a posted sales invoice or purchase order with varying VAT percentages on different lines (e.g., 25% and 10%) through the Continia Delivery Network, the following error occurred: The record in table VAT Sub Total already exists. Identification fields and values: Header Table No.=<eDocument Header Table No.>Header Type=<eDocument Header Type>,Document No.=<eDocument No.>,Document Line No.=<eDocument Line No..>,VAT Category Id=<VAT Category ID>	56200
eDocuments	A typo in the tooltip for the Metadata Update Job Status field on the Continia eDocuments Setup page has been corrected.	56621
eDocuments	The following UI changes have been applied in eDocuments: The eDocument Card and Open in Document Journal actions on the eDocument Overview page have been moved from the New action group to the Process action group. The Find Entries and Open in Document Journal actions on eDocuments cards, such as purchase orders, have been promoted to the Process action group.	57957

Inhaltsverzeichnis

Detailed Changelog for Continia Document Capture 2024 R2

Document Capture 2024 R2, Service Pack 1, hotfix 2

Bug fixes

Document Capture 2024 R2, Service Pack 1, hotfix 1

Bug fixes

Document Capture 2024 R2, Service Pack 1

New or changed functionality

Bug fixes

Document Capture 2024 R2, hotfix 2

Bug fixes

Document Capture 2024 R2, hotfix 1

Bug fixes

Document Capture 2024 R2

New or changed functionality

Bug fixes

Ist diese Seite hilfreich?