Detailed Changelog for Continia Document Capture 2023 R1

15/12/2023
106 minutes to read

This article lists all new features and bug fixes for each version of Continia Document Capture 2023 R1.

Tip

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 R1 Service Pack 3

Released: December 15, 2023
App version: 11.3.0
FOB version: 11.03

New or changed functionality

Functional area	Description	Id
Document and Templates	The below configurable message can now be configured as type Information: The XML Document contains [discounts and charges] elements that are not created as Fields for this Template. Please use Add Template Field to add them. In previous versions, it was only possible to configure the message type as Warning and Error.	47538
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 Continia Web Approval Portal has been updated to version 1.29.0	51759
Purchase Documents	The following feature is only available in Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC v20) 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.	49968

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: Field Journal Templ. Purch. Invoice (11310) of table Purchases & Payables Setup (312) is obsoleted, reason: Replaced by W1 field P. Invoice Template Name	51496
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: Field Allow Posting From (11300) of table Gen. Journal Template (80) is obsoleted, reason: Replaced by W1 field Allow Posting Date From	51536
Document 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 (%). The filter "<value starting with %>" is not valid for the <tablefield> field on the table. The variable "<value starting with %>" was not understood. To prevent this problem, any leading percentage signs (%) are now removed from values used as filters. Several characters that hold a special meaning in filtering contexts, e.g., * \| &, are already disregarded.	43210
Document 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
Document 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
Document 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: 'Recurring must be equal to 'No' in [Journal Template]: Name=RECURRING. Current value is 'Yes'.	45076
Document and Templates	Field captions have been added to the template fields in the Purchase Order category. The following template fields have been updated: Order Date Vendor Order No. (also updated in Purchase category) Vendor Shipment No. (also updated in Purchase category) Promised Receipt Date Order (Document Type)	47452
Document and Templates	An incorrect document validation comment in the Purchase Order category for the Danish and German localizations has been corrected. The following message: WARNING: Purchase order <Order No.> <Purchase order action> already exist. <Purchase order action> Is now replaced by this message: WARNING: Purchase order <Order No.> already exist. <Purchase order action>	47562
Document 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
Document and Templates	The field Check Item Prices is now hidden from the Template Card page for the Sales category.	48632
Document and Templates	When configuring the template field Account Type to Charge (Item) and subsequently assigning a valid item charge to the Account No. template field, the following error comment was displayed: Account No. is not correct.	49304
Document 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
Document and Templates	When capturing fields, the following error could occur: The length of the string is <String Length>, but it must be less than or equal to <Maximum Length> characters. Value: <String Value>	49459
Document and Templates	When identifying the XML template for an electronic document, only the field with the code CUSTOMISATIONID was considered.	49531
Document 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
Document and Templates	Specifying Account No., VAT Prod. Posting Group, or VAT Bus. Posting Group when Account Type is blank in the Account for Amounts, the following error message will be displayed: Account Type must have a value.	49590
Document and Templates	Previously, a captured Vendor Bank Account No. containing only letters would incorrectly pass validation.	49730
Document 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
Document and Templates	You can now add empty files as attachments to the Document Journal.	49916
Document 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
Document and Templates	This only applies to Business Central 20 CU6 to CU18. When registering a document from the Document Journal, you could encounter the following confirmation dialog: This will change the dimension specified on the document. Do you want to keep the existing dimensions?	50618
Document 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
Document 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: "Imported Amount Incl. VAT does not match"	51671
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	The option Can Edit Posting Lines now allows you to update Gen. Prod. Posting Group when the document is pending approval.	49356
Document Approval	The following change only applies to Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC v20) and newer versions. When Advance Approval for purchase invoices was enabled, the Approval Flow code was not visible on the Purchase Order and Purchase Return Order pages.	50270
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
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	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	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: Approval User Group Approval Permissions Approval Forwarding Expense Management action group: Settlements Expenses Milage Per Diems Credit Cards Payment Types Vendor Card	49278
General Application	An incorrect number of attachments was shown on the Posted Sales Credit Memo page.	49821
General Application	When we released DC11.02, we forgot to write the following in the changelog. Additional conditional statements are added when using Document Search in XML files. In some cases, when using Document Search, the following error was thrown: "Unable to convert from Microsoft.Dynamics.Nav.Runtime.NavXmlNode to Microsoft.Dynamics.Nav.Runtime.NavXmlElement."	49965
General Application	When selecting what data to include in the exported configuration file using the Assisted Setup Guide, the following error could occur: The Document Storage Type field in the Document Capture Setup table cannot be changed when there are documents in the database.	50002
General Application	The Swedish translation for the field Maximum allowed difference Incl. VAT has been adjusted on the following pages: General Ledger Setup Currency Card Currencies	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	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: Caption Caption Mandatory Document Category Card page field captions: Suggest Header 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: The document will not be auto-approved as the total invoice amount (<Total Order Amount>) - matched amount (<Amount of the first matched line>) is outside the maximum allowed 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
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	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: You cannot choose Purchase Contract when creating a line translation.	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: Sorry, the current permissions prevented the action. (TableData CDC Document Document Insert)	49899
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: The length of the string is <string length>, but it must be less than or equal to 50 characters. Value: <Description value>	49959
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 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
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. The quantity (<Purchase Order Quantity>) that you are trying to invoice is greater than the outstanding quantity in order <Purchase Order No.>. You cannot invoice more than <Available Quantity> units.	49084
Purchase Documents	When registering a credit memo with a negative amount in the document lines to the General Journal, the following message was shown: Amount Incl. VAT does not match - Imported: <Imported Amount> - Assigned: <Assigned Amount> Any subsequent steps will have to be performed manually.	49235
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	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

Document Capture 2023 R1 Service Pack 2, hotfix 2

Released: September 18, 2023
App version: 11.2.2

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
Document Approval	Can Edit Posting Lines now allows you to update Job No. and other job-related fields when the document status is Pending Approval.	49564

Document Capture 2023 R1 Service Pack 2, hotfix 1

Released: September 7, 2023
App version: 11.2.1

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	During document import, the following error could occur: The length of the string is <Captured value length>, but it must be less than or equal to 20 characters. Value: <Captured value>	49375
Purchase Documents	The following only applies to app-based versions of Business Central. In Document Capture 2023 R1 Service Pack 2 (11.2.0), the Status field was set to not visible on the following pages: Purchase Invoices Purchase Credit Memos Purchase Return Order List Purchase Order List	49383

Document Capture 2023 R1 Service Pack 2

Released: August 29, 2023
App version: 11.2.0
FOB version: 11.02

New or changed functionality

Functional area	Description	ID
Country and Regional	Document Capture is now available for additional countries in Business Central online. You can view the complete list of supported countries here: Country/Regional Availability and Supported Languages	45774
Document 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: For items configured with the costing method set to Standard, the value in the field Standard Cost* is used.* For items configured with the costing method set to FIFO, LIFO, Average, or Specific, the value in the field Unit Cost* is used.* For items having a zero value in Standard Cost or Unit Cost, the value in the field Last Direct Cost* is used.* 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 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
Document and Templates	The following message has been made configurable: Warning: No lines recognized.	47451
Document and Templates	It is now possible to configure the following 3 messages as comment type "Information" Order No. = '[Order No.]' exists but outside the tolerance settings. Order No. = '[Order No.]' exists but no open receipts exist. Order No. = '[Order No.]' exists but no open return shipments exist.	48028
General Application	The Swedish translation of page CDC Purch. Approval Entries is changed from Godkännandetransaktioner. To Köpgodkännandetransaktioner.	47005
General Application	The following feature is only available in extension versions of Business Central. 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
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

Bug fixes

Functional area	Description	ID
Document and Templates	When capturing a new search text to a template where one search text already exists, the new search text would overwrite the existing one. Now, you are presented with the following two options: "Keep the existing search text and add the selected text." "Replace the existing search text."	43801
Document and Templates	The vendor was not identified if VAT Registration No. contained spaces both on the vendor and in the document.	45667
Document and Templates	When validating the recognized lines in the Purchase Order category and the Translate to Type or Translate to No. are missing in the document line, the following error comment is now shown. Line <Line No.> must be translated. Please add a translation of No. (<No.>) or Description (<Description>).	45700
Document and Templates	When adding a line of type item to a Std. Amount Distribution, Document Capture would display the following error message if Inventory Posting Group was not populated on the Item Card: Inventory Posting Group must have a value in Item: No.=<Item No>. It cannot be zero or empty. This has now been changed so that only items with Type = Inventory need to have Inventory Posting Group populated.	47373
Document and Templates	In some localizations, the name of the template fields GTIN No. and VAT Prod. Posting Group was not translated.	47443
Document and Templates	Corrected an issue that would prevent standard functionality (CheckCreateSalesRecurringLines) to be executed when a Sales Order was created by Document Capture.	47614
Document and Templates	Only the first document was recognized when importing an XML document and the document was automatically split.	47666
Document and Templates	When registering a document using a template that would create journal lines and a template field had a value specified in the Field in Purchase Header or Field in Purchase Line, an error message was displayed: <Destination Field Caption> must be equal to <Journal Table Id> in Document Category: Code=<Document Category Code>. Current value is <Table Id>.	47784
Document and Templates	Corrected an issue that would cause the Remove Template Field action to fail with the error message shown below if the template contained a template field with a Field Name exceeding 45 characters. The length of the string is 55, but it must be less than or equal to 50 characters. Value: [Long template field name]	47969
Document and Templates	Auto-assign on error was only executed when performing Recognize Fields on a document. The same functionality is now invoked when activating the Validate action.	48357
Document Approval	When changing the account type in a purchase document line for a document with status pending approval and the Can Edit Posting Lines in the Continia User Setup was enabled for the approver, the following message was displayed: Status must be equal to 'Open' in Purchase Header: Document Type=<Document Type>, No.=<Document No.>. Current value is 'Pending Approval'.	43335
Document Approval	When canceling an approval flow for a purchase document, the cancel request was not issued to the Workflow Webhook integration. In some cases, this could prevent approval using Power Automate flows not to function as expected.	47600
Document Approval	The hidden field 4-eyes, 2nd Approver ID has been removed (deprecated) from the Continia User Setup Card.	48314
General Application	To improve the shown order of the approvers when using the Contina Web Approval Portal, sorting has been added to page 6086004 - Purch. Doc. Appr. En. (WS).	29537
General Application	In the CDC-ALL permission set, the read permissions for the G/L entry and G/L register have been changed from Read to Indirect Read.	45449
General Application	When changing Document Storage Type, the confirm message text could sometimes contain incorrect storage parameters. It now always displays the correct values.	46835
General Application	The XML-type identification processing time has been significantly improved by reducing the number of calls to the document storage.	47323
General Application	If a vendor number contained filter characters and the length of the vendor number equals 19 or 20 characters, the Documents Factbox on the Vendor list page displayed the following error: Error: The length of the string is 22, but it must be less or equal to 20 characters. Value: '<vendor no.>'.	47578
General Application	The following feature is only available in extension versions of Business Central. The Business Central standard actions in the Incoming Document action group on the purchase order card and purchase order list were hidden even when enabling the Show Standard Purchase UI Elements option on the Document Capture Setup page.	47866
General Application	In some cases, the attached document was not displayed in the document viewer on the Vendor Ledger Entries page.	48533
Order & Receipt Matching	In a matching scenario where you don't use the price as a line-matching criterion, you could have prices in the invoice differing from the prices specified in the order without any notice from Document Capture. Now, a configurable message is shown in the comment section if the amount difference of the matched lines exceeds the tolerance specified in the Max. Variance Amount Allowed or Max. Variance % Allowed fields on the template card. The difference <Amount> between Line Amount on the matched order/receipt lines and the document lines is outside the allowed document variance.	39399
Order & Receipt Matching	Matching to a purchase order line of type Charge (Item) is only supported when Invoice Reg. Step 1 on the template is set to Match and update Order. If the template is configured to create a separate invoice or credit memo, the following document comment of type error is shown: With the current template settings, lines can't be matched to item charge order lines. Please change "Invoice Reg. Step 1" to "Match & Update Order" or recieve the order and match to receipt lines. For return order lines the following error is shown: With the current template settings, lines can't be matched to item charge return order lines. Please change "Invoice Reg. Step 1" to "Match & Update Order" or ship the return order and match to shipment lines.	43510
Order & Receipt Matching	When applying Our Order No. to a prepayment invoice, and the referenced order contained comment lines, the following error was displayed: Attempted to divide by zero	47903
Purchase Contracts	Previously, when clearing or changing the value in the header field Account Type from Purchase Contract, the document line relation to purchase contract lines was not removed. The line relation is now updated, but due to technical limitations, the field Purchase Contract Line No. value is visually not updated on the page when performing this action from the Document Card. You must therefore reopen the page to see the updated line value.	47478
Purchase Contracts	When creating a purchase contract, the following error occurred when the Purchase Contract Nos. code on the Purchase Contracts Setup had more than 10 characters. The length of the string is <String Length>, but it must be less than or equal to 10 characters. Value: <Field Value>	47569
Purchase Contracts	When having purchase contracts of both the type purchase and expense, the Purchase Contract Cues on the Document Capture Activities included all types of contracts. The cues are now filtered only to show the purchase contract of type purchase.	47589
Purchase Contracts	When selecting purchase contract as the Account Type and specifying a contract number in the Account No. field in the Document Journal, the values were not stored in the Accounts for Amounts.	47835
Purchase Documents	When trying to distribute an amount lower than the total unit cost of the Standard Amount Distribution Code lines on the document on the Get Std. Purch. Amt. Dist page, the following error was shown: The Purchase Line does not exist. Identification fields and values: Document Type=[Document Type],Document No.=[Document No.],Line No.=[Line No.] Now, if the total unit cost of the std. amount distribution lines are higher than the amount to distribute, the following error is shown: The total unit cost, [Total unit cost], of the line(s) on the Std. Amount Dist. Code is greater than the amount to distribute, [Amount To Distribute].	44611
Purchase Documents	When registering a document with negative amounts in the document lines to the General Journal, the following message was shown: Amount Incl. VAT does not match - Imported: <Imported Amount> - Assigned: <Assigned Amount> Any subsequent steps will have to be performed manually.	46515
Purchase Documents	The proper font styling was not applied to the Status field in the Purchase Orders, Purchase Invoices, Purchase Return Orders, and Purchase Credit Memos pages. This only applies to the extension versions of Business Central.	47440
Purchase Documents	The Get Order Lines action on the Purchase Invoice page failed with the following error message if the Prices Incl. VAT on the purchase order was set to true, and the purchase order had posted prepayments: Prices Including VAT must be equal to 'Yes' in Purchase Header: Document Type=Invoice, No.=<Invoice No.>. Current value is 'No'.	48070
Purchase Documents	When registering a purchase document using an Amount Distribution code and the account, the Line Posting Description header field would overwrite the description specified in the Amount Distribution Code.	48207

Document Capture 2023 R1 Service Pack 1, hotfix 1

Released: June 27, 2023
App version: 11.1.1

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	The process of calculating the XML master template for an XML document is now optimized to reduce the calls to the storage account.	47323
Order & Receipt Matching	When Our Order No. was applied to a prepayment invoice and the referenced order contained comment lines, the following error was displayed: Attempted to divide by zero	47903

Document Capture 2023 R1 Service Pack 1

Released: June 2, 2023
App version: 11.1.0
FOB version: 11.01

New or changed functionality

Functional area	Description	ID
Document and Templates	The below error comment: You must specify Account No. is now being suppressed when the following criteria are met: Autorun Perform Match is enabled. Either of the following two configurable messages has been configured as errors: Autorun Perform Match is enabled, but no match could be found. The template <Template No.> is configured to register with match, but the document is not matched.	43512
Document and Templates	Color mode for TIFF files in Business Central online is now available as Microsoft has addressed the related performance issues.	45445
Document and Templates	You can now change the configurable message, shown below, to comment type Information. Amount ([Amount]) does not match the rounded amount ([Amount]) calculated using Invoice Rounding Precision and Invoice Rounding Type configured for [Currency Code].	46077
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: Document Capture is enabled The approval module is activated An approval workflow is set up	46039
General Application	For the Norwegian localization, two new captions are added in the PDF identification template "KJØP-ID". Org. Nr. Org.Nr.	45668
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: Table 6085575 "CDC Document Category" Table 6085579 "CDC Template" Table 6085580 "CDC Template Field" Table 6085752 "CDC Posted Dtld. Appvl. Entry" Table 6085753 "CDC Posted Dtld App Entry Dim" Table 6085730 "CDC Purch. Allocation Header" Table 6085731 "CDC Purch. Allocation Line" Table 6085732 "CDC Purch. Alloc. Entry" It is possible to override the error message through an event subscription.	47221
Purchase Documents	When in the Document Journal updating an existing purchase order that has the status Released, a dialog box will now be displayed: The purchase order has been released. Do you want to reopen and update the purchase order?	46377
Purchase Documents	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: The purchase order has been submitted for approval. Do you want to cancel the approval and update the purchase order?	46379
Purchase Documents	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: The purchase order is currently pending prepayment. Do you want to reopen and update the purchase order?	46706

Bug fixes

Functional area	Description	ID
Country and Regional	The headline and description texts in the teaching tip for the Accounts for Amounts page have been updated to match the page name.	45879
Country and Regional	The following updates have been made to the AU and NZ Configuration file: Changed the name of the purchase master template field VAT Registration No. to ABN (template field VATNO). The Is Valid codeunit CDC Is Valid VAT No. has been updated to check against the ABN field on the vendor. On the purchase document category: Added ABN (field 11620) to the list of identification fields.	47298
Document and Templates	When recognizing fields in an XML purchase document with an embedded file where the file name contained a dot character and did not have a file extension, the following error occurred: The length of the string is <String Length>, but it must be less or equal to 30 characters. Value: <File name> Now, MimeType (MimeCode) will be used to identify the file type if the file type exceeds 30 characters or, for any other reason, can't be identified.	44535
Document and Templates	When moving a document from Documents (UIC) to the active company and the template was set to Register Documents Automatically in the Template Card, the following error occurred: The following C/AL functions are limited during write transactions because one or more tables will be locked. Form.RunModal is not allowed in write transactions. Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed. Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed. XmlPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'XmlPort.RunModal(...,FALSE)' is allowed. Use the COMMIT function to save the changes before this call, or structure the code differently.	44947
Document and Templates	When recognizing an XML document, and the currency code recognized was the same as the LCY Code on the General Ledger Setup, the following error occurred: "One or more lines have errors."	45462
Document and Templates	The field Transfer Amount to Document has been added to the template number fields on the Template Field Card for the Sales category.	45511
Document and Templates	When recognizing template fields with Data Type set to Lookup, the following error occurred in the Document Journal: The length of the string is <String Length>, but it must be less than or equal to 100 characters. Value: <Field Value>	45863
Document and Templates	The following tooltip has been added to the field Show Embedded PDF files as Default on the Template Card: Specifies the default display option in the Document Viewer for XML files. When enabled, the embedded PDF file from the XML file is shown. When disabled, the styled view of the XML data is displayed.	46186
Document and Templates	When having two or more XML vendor templates with multiple search texts and using Recognize Fields on an XML document, the following error occurred: The following C/AL functions are limited during write transactions because one or more tables will be locked. Form.RunModal is not allowed in write transactions. Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed. Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed. XmlPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'XmlPort.RunModal(...,FALSE)' is allowed. Use the COMMIT function to save the changes before this call, or structure the code differently.	47004
Document and Templates	When capturing a value containing invalid filter characters into the Document Type field in the Document Journal, the following error occurred: The filter "<filter string>" is not valid for the Rule field on the Field Rule table. An error occurred while interpreting the filter: Did not expect "<filter character>"	47022
Document and Templates	To avoid creating empty files when importing documents, additional measures have been applied to prevent multiple instances of Import Documents running simultaneously.	47052
Document Approval	When approving documents, users may receive the following message: You do not have the following permissions on TableData CDC Template Field Rule: Read. Read permissions for the table CDC Template Field Rule have now been added to the permission set "CDC ALL."	46874
Document Approval	When using Send Status email to Approvers, emails were not sent to shared users when setting Forward Emails in the Approval Sharing.	46926
Document Approval	When setting Invoice Reg. Step 2 to Release or Post in the Template Card for purchase documents, an error message was displayed even when purchase invoice approval is not enabled: The Continia User Setup does not exist. Identification fields and value: Continia User ID = '<User ID>'	47077
General Application	When exporting attachments, the following error could appear. This has now been prevented by extending the filename to 250 characters. The length of the string is <Number>, but it must be less than or equal to 100 characters. Value: <Text>	42864
General Application	When using the Export Attachments functionality, files related to XMLs had the .XML file extension incorrectly added in addition to the correct file extension.	42865
General Application	The template card's Calculate Date (Date Formula) field can now be used on line fields.	45751
General Application	Added the action Add to the context menu for the Documents factbox page (drag-and-drop).	46060
General Application	Previously, the "CDC Basic" Application Area could be enabled even when the Application Area feature was not in use. In this case, only Document Capture pages were visible. Now, the "CDC Basic" Application Area is only enabled if Basic Application Area is also enabled.	46182
General Application	Corrected a spelling mistake on the Suggest Header Field Captions. The Danish page caption "Forslå hovedfeltoverskrifter" was changed to "Foreslå hovedfeltoverskrifter".	46542
General Application	We have added a new field, Document Type, on the Field Rules page. The Document Type field was not populated with custom rules during the upgrade process. For the template field DOCTYPE ([I]nvoice / [C]redit Memo / [P]repayment), we are now updating the new field Document Type for custom-added rules based on the rule description. As not all rules can be automatically updated, the following message is now displayed when recognizing fields and the Document Type is empty: Please specify the Document Type for Field rule [Field Rule] in template [Template No.] field [I]nvoice / [C]r. Memo / [P]repayment as it is currently missing.	46797
General Application	When creating a new customer, vendor, or item without any templates and with the Document Factbox visible on the Customer Card, Vendor Card, or Item Card page, an error message is displayed: Document: There is no <Customer, Vendor or Item> within the filter. Filters: No.: ''	46946
General Application	Opening the role center, users could experience slow performance when a document category had a value in the field Get Document Status in the Codeunits section. This update only applies to Business Central 2019 release wave 2 (BC15) or newer versions.	47231
General Application	To download or open the attachments in the Documents factbox page (drag-and-drop), you can now simply select the description text.	47263
General Application	The field Translate to VAT Bus. Posting Group has been added to the Accounts for Amounts page.	47305
Order & Receipt Matching	When using the report "Delete Invoiced Purch. Orders" to batch delete orders, the following error occurred in some scenarios: The quantity (%2) that you are trying to order is lower than the quantity matched against this order. You must order at least %1 units.	44599
Platform and Technology	When opening Manual Setup in the app version of Document Capture, many duplicated records were displayed.	42928
Purchase Contracts	It is no longer possible to remove the Vendor No. filter when looking up purchase contracts from the Document Journal.	42785
Purchase Contracts	When creating a purchase contract based on a registered document (Status = Registered) the following message is now shown: Status must be equal to 'Open' in Document: No.=<Document No.>. Current value is 'Registered'.	45275
Purchase Contracts	The value in the purchase contract line field Unit Cost was always rounded to two decimal places when creating a contract from the Document Journal.	46023
Purchase Contracts	When returning a purchase contract to the reviewer, the archived purchase contract's Status is now set to Returned to Reviewer.	46178
Purchase Contracts	When creating a new purchase contract based on a document, the validation of default line information was previously performed at the end of the process, resulting in the input being lost, and an error was thrown if a contract could not be created. Now, several checks are executed before the contract creation process is initiated, and the user is immediately informed about the error.	46477
Purchase Contracts	When adding the template line field Purchase Contract Line No. to an XML document, the field was hidden by default. This change currently only applies to new implementations or if the configuration file is re-imported.	47187
Purchase Contracts	When recognizing a value or using a formula in the Vendor Contract No. template field, the functionality linking the document to the purchase contract was not triggered. Due to technical limitations, the purchase contract line number field value is not updated on the page when performing this action from the Document Card. You must close and reopen the page to see the updated purchase contract line relations.	47190
Purchase Documents	When recognizing a purchase prepayment document in the Document Journal, the document type was identified as an invoice instead of a prepayment if the document had both prepayment and invoice captions (e.g., Prepayment Invoice).	45709
Purchase Documents	To ensure better initial recognition of new documents, several field captions have been added to the master template fields in the Purchase Order and Purchase categories. The following template fields have been updated: PURCHORDER category Order Date Vendor Order No. Vendor Shipment No. Promised Receipt Date [O]rder (document type) PURCHASE category Vendor Order No. Vendor Shipment No. The template field captions have been added for the following countries/regions: Australia Canada New Zealand United Kingdom United States	45901
Purchase Documents	When creating a new purchase order in the Purchase Order category, purchase order lines were not created if only header amounts were recognized and no translations were specified in Accounts for Amounts in the Amount Excl. VAT template header field.	46085
Purchase Documents	When doing partial translation of a recognized purchase document line where the Translate to Type is specified but not Translate to No. in the Line section, the following error was shown when force registering the document: No Account has been configured for Amount Excl. VAT.	46375
Purchase Documents	When validating a purchase order document in the Document Journal and no values are recognized in the template fields Our Order No., Vendor Order No., or Vendor Shipment No., the below warning will not be shown in the Comments section. WARNING: Purchase order <Order No.> already exist. A new purchase order will be created.	46376
Purchase Documents	When in the Document Journal performing a lookup in the Our Order No. field on a purchase order, and the Our Order No. field contains a valid value, the cursor is now placed on the related line in the Purchase List.	46378
Purchase Documents	In the Purchase category: When the value of the DOCTYPE field matches a rule that does not have the field Document Type populated with the correct value (invoice, credit memo, or prepayment), any document registered in the purchase category would be created as a purchase quote.	46651
Purchase Documents	When you registered a purchase document using Line Posting Description in the Document Card, and the Line Posting Description was longer than the Description in the purchase line, additional text lines were created only for the last purchase line.	46695
Purchase Documents	When pressing "New", either on the purchase order list or the purchase order card pages, the lines subpage would contain order lines belonging to other orders.	46734

Document Capture 2023 R1, hotfix 5

Released: May 10, 2023
App version: 11.0.5

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
Document and Templates	When you had two or more XML vendor templates with multiple search texts and used Recognize Fields on an XML document, the following error occurred: The following C/AL functions are limited during write transactions because one or more tables will be locked. Form.RunModal is not allowed in write transactions. Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed. Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed. XmlPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'XmlPort.RunModal(...,FALSE)' is allowed. Use the COMMIT function to save the changes before this call, or structure the code differently.	47004
Document and Templates	When a value containing invalid filter characters was captured into the Document Type field in the document journal, the following error occurred: The filter "<filter string>" is not valid for the Rule field on the Field Rule table. An error occurred while interpreting the filter: Did not expect "<filter character>"	47022

Document Capture 2023 R1, hotfix 4

Released: May 4, 2023
App version: 11.0.4

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
Document Approval	When approving documents, users may receive the following message: You do not have the following permissions on TableData CDC Template Field Rule: Read. Read permissions for the table "CDC Template Field Rule" have been added to the permission set CDC ALL.	46874

Document Capture 2023 R1, hotfix 3

Released: April 28, 2023
App version: 11.0.3

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	Expanded the Progress text variable from 30 to 100 characters on the Storage Migration Status page to prevent the following error in setups with a large number of documents pending migration: The length of the string is <number>, but it must be less than or equal to 30 characters. Value: <Number> documents are remaining. Page View - Storage Migration Status has been closed.	46765
General Application	We have added a new field, Document Type, on Template Field Rules. The Document Type field was not populated for custom rules during the upgrade process. For the template field DOCTYPE ([I]nvoice / [C]redit Memo / [P]repayment), we are now updating the new field Document Type for custom-added rules based on the rule description. It is not all rules that we can update. When Document Type is blank, the following error now occurs when fields are recognized: Please specify the Document Type for Field rule [Field Rule] in template [Template No.] field [I]nvoice / [C]r. Memo / [P]repayment as it is currently missing.	46797

Document Capture 2023 R1, hotfix 2

Released: April 26, 2023
App version: 11.0.2

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
General Application	Added the template fields Balancing Account Type and Balancing Account No to the master template in the purchase category during upgrade.	46710
General Application	Resolved an issue that caused the upgrade to fail if no G/L setup record could be found in a company.	46711
Purchase Documents	In the purchase category: When the value of the DOCTYPE field matches a rule that does not have the field Document Type populated with the correct value (Invoice/Credit Memo/Prepayment), any documents registered in the purchase category would be created as purchase quotes.	46651
Purchase Documents	When you selected New, either on the purchase order list or on the purchase order card pages, the lines subpage would contain order lines belonging to other orders.	46734

Document Capture 2023 R1, hotfix 1

Released: April 14, 2023
App version: 11.0.1

Only released in Business Central online.

Bug fixes

Functional area	Description	ID
Country and Regional	When running the Document Capture setup wizard in a new company, using Swedish language, the following error occurred: Strängens längd är 252, men den måste vara mindre än eller lika med 250 tecken. Värde: Förskottsbetalningar på [Belopp] ([Pct.]%) för inköpsorder [Beställningsnr.] har redan...	46478

Document Capture 2023 R1

Released for online: April 3, 2023
Released for on-premises: April 14, 2023
App version: 11.0.0
FOB version: 11.00

New or changed functionality

Functional area	Description	ID
Document and Templates	The following template fields have been renamed: Invoice Header Posting Description to Header Posting Description Posting Description to Line Posting Description	17795
Document and Templates	A new field, Check Item Prices, has been added to the Template Card. The field allows you to compare the special prices and discounts for an item on an unregistered Document. The field can only be enabled when Recognize Lines is enabled. It checks all document lines, and if one of the lines' prices differs from the vendor's calculated item price, a comment/warning is shown. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/purchase-documents/automatic-checking-of-line-item-prices	28359
Document and Templates	The standard Business Central field, Deferral Code, has been added to Accounts for Amounts in the Document Journal. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/purchase-documents/deferral-code-on-the-accounts-for-amounts-page	28532
Document and Templates	When manually merging PDFs, you can now merge nonconsecutive documents. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/merging-nonconsecutive-documents	29448
Document and Templates	A new category has been added for creating and updating purchase orders. Most of the functionality available in the existing category for purchase invoices and credit memos is also available for the new purchase order category. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/new-category-for-creating-and-updating-purchase-orders	29744
Document and Templates	The following comment has been changed from: Fully matched to Purchase Order <Purchase Order No.> To The Amount Excl. VAT (<Amount Excl. VAT>) - Freight Amount (<Freight Amount>) - [Other amounts that are being subtracted ] (<Amount>) = <Total Amount> fully matched to Purchase Order <Purchase Order No.>. If the template is set to Auto Approve Within Variance but outside tolerance, the following comment will be added: The document will not be auto-approved as the total invoice amount (<Document Amount>) - matched amount (<Matched Amount>) is outside the maximum allowed variance.	30816
Document and Templates	A page for selecting and storing the salesperson that is to be applied when registering a document in the sales category has been added. The functionality is similar to the purchaser translation used in the purchase category.	31983
Document and Templates	You can now configure amount distribution codes to split the invoice amount by dimension while keeping the existing account number. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/purchase-documents/splitting-invoice-amounts-by-dimension-while-keeping-the-existing-account-number	38670
Document and Templates	When the cursor is focused on a specific document line in the Document Card and opening the Item Reference List, the cursor is now focused on the record in the Item Reference List that matches the document line.	38976
Document and Templates	When creating general journal lines, you can now specify the Balancing Account Type (G/L Account or Bank Account) and Balancing Account No. as template header fields. By default, the vendor is used as the balancing account when the template header fields Balancing Account Type and Balancing Account No. are empty. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/purchase-documents/creating-general-journal-lines-without-a-vendor-balancing-account	39315
Document and Templates	The Comment field has been added to page 6085600 - CDC Document List With Image and page 6086074 - CDC Delegated Documents List.	40280
Document and Templates	Support for shared mailbox with EWS has been added to the Document Category. To use a shared mailbox, populate the new Shared Email Address field on Document Category Card under the Email section.	40405
Document and Templates	The configuration file imported when setting up Document Capture has been updated with a number of changes for all localizations. Purchase PDF master template: The template header field Approval Flow has been moved below Our Contact Sales master template: The field Account No. is no longer automatically inserted when creating new templates General configuration changes: The default value in the Send Welcome Email field in the Document Capture Setup / Continia Web Approval is now set to Manually The category description for Purchase is changed to Purchase Invoices and Credit Memos The category description for Sales is changed to Sales Orders and Credit Memos The default value in the Credit Memo Reg. Step 1 field for the Sales category is now set to Create Credit Memo	40499
Document and Templates	The configuration file imported when setting up Document Capture has been updated with a number of changes for the North American localization. Purchase PDF master template: Added Spanish and French captions to numerous header template fields Added several captions to the document type header field Removed the Account Field code from Amount Excl. Tax Changed the Freight Amount template field to default not subtract from Amount Excl. Tax Renamed the Tax Amount template field to Tax Amount (BC) Added a new header template field Tax Amount (GL) The fields Account Type and Account No. are no longer automatically inserted when creating new templates Sales PDF master template: Added Spanish and French captions to numerous header template fields Added several captions to the Document Type header field Renamed the Tax Amount template field to Tax Amount (BC) General configuration changes: The default value in the Amounts on Approval field in the Document Capture Setup / Purchase Approval is now set to Every Approval The default value in the Dimension on Approval field in the Document Capture Setup / Purchase Approval is now set to Every Approval Removed all XML templates except PEPPOL in the Purchase category Removed all PDF identification templates in the Purchase category Removed all PDF identification templates in the Sales category	40499
Document and Templates	When enabling Show Embedded PDF files as Default on an XML template and importing an XML document with an embedded PDF file, the Document Viewer will display the PDF file instead of the original XML file. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/displaying-embedded-pdf-files-by-default-in-the-document-viewer	40802
Document and Templates	When using the Suggest Header Field Captions for updating the master template fields, it is now possible to ignore caption suggestions. Ignored caption suggestions won't be recreated when rerunning the Create Suggestions action. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/ignoring-caption-suggestions	41569
Document and Templates	The document comment shown below has been made configurable. Due Date was calculated based on Invoice Date.	41890
Document and Templates	A new field, Split XML Documents Automatically, has been added to the Document Category card. When populating the Split XML Documents Automatically field, XML documents are automatically split during import.	41895
Document and Templates	The following feature is only available in App based versions of Business Central. When registering a document, it is possible to validate the imported amounts against the assigned amounts on purchase documents. For several reasons, it may be acceptable to have minor differences between the imported and assigned amounts. Therefore, the following two new fields have been added to the General Ledger Setup and Currency pages. Allowed Difference Excl. VAT Allowed Difference Incl. VAT The values specified in the General Ledger Setup page are used for amounts registered in LCY (empty currency code). In contrast, the values specified on the Currency page are used for currency amounts. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/configuring-the-allowed-difference-between-imported-and-assigned-amounts	42504
Document and Templates	The field caption Ask to Set Default G/L Account has been changed to Ask to Set Default Account No. on the Template Field page.	42658
Document and Templates	The Create new Template Field action has been added to the Document Card page.	42955
Document and Templates	A new template line field, Position, has been added to the purchase and sales master templates.	43283
Document and Templates	When multiple templates have been identified using search texts, a dialogue that allows the user to select the correct template is now displayed. This only happens when recognizing fields on a single document and not during import or when batch recognizing multiple documents in the Document Journal. The dialogue is only displayed if the templates identified have more than one search text. In the case where multiple templates, only having one search text, are found, existing functionality prioritizes which one to use based on where the search text is found in the document. The search text found first (at the topmost position of the document) is used. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/dialog-listing-templates-if-multiple-templates-are-found-using-search-texts	43513
Document and Templates	Document Capture supports the automatic assignment of item charges when registering a document that contains a line of type Charge (Item). A new option field, Item Charge Assignment Method, has been added to the Template Card. The available options are: <Empty> Equally By Amount By Weight By Volume The initial option <Empty> (the default value) does not initiate the new functionality. The other four options invoke the same automatic assignment methods available in the Suggest Item Charge Assignment action in the standard Business Central application. The automatic assignment is available when Registering a document matched to receipt lines or return shipment lines (not matched to order lines or return order lines) Registering an invoice document without using match. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/support-for-assignment-of-item-charges-during-document-registration	43514
Document and Templates	Two new features have been added to document assignment: A new field, Assign to User ID, has been added to the Template Card. Documents will be automatically assigned to the user configured in Assign to User ID when the template is applied to the document. Assignees found using the Assign on Error in configurable messages will override Assign to User ID from the template. A new option field, Comment on manual assignment, has been added to the Document Capture Setup page. When manually adding a user to the field, Assigned to User ID, in the Document Journal, the user will be presented with a page to write an assignment comment depending on the option chosen. The available options are: No (default value): The comment sheet will not be displayed. Optional: The comment sheet will be displayed but can be closed without adding a comment. Mandatory: The comment sheet will be displayed. The system will show an error if no comment is added. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/new-option-to-enable-manual-assignment-comments.	43517
Document and Templates	When deleting a template field from a master template, the user is now prompted with a confirmation for also deleting the template field on all related templates if the field has not been used to capture a value. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/bulk-deletion-of-master-template-fields	43518
Document and Templates	On the Line Translations page (used for number and description translations), the following changes have been applied: The field Field Description has been removed. The caption of the field Translate from is now dynamically set to Translate from No. or Translate from Description. The field Account Type has been renamed to Translate to Type. The field Account No. has been renamed to Translate to No. The field Translate From is automatically populated with the corresponding value on the document line from which the translation was invoked. On the Unit of Measure Translations page: The field Translate From has been renamed to Translate From UOM Code. On the Accounts for Amounts page: The field Field Description has been renamed to Field.	43519
Document and Templates	When a template number field with Transfer Amount to Document set to Always or If lines are not recognized has a value, but no account has been configured for the template field, the following document comment is added: No Account has been configured for <Template Field Name>	43534
Document and Templates	Deletion of the following important and required template fields is now being prevented: Header fields: DOCNO DOCDATE AMOUNTEXCLVAT AMOUNTINCLVAT DOCTYPE Line fields NO DESC QUANTITY UNITCOST LINEAMOUNT	43688
Document and Templates	The Lines fasttab must be updated when adding or removing a template line field from the Document Card page. To ensure this, the following message is now displayed: Please close and reopen the Document Card.	43690
Document and Templates	When using line recognition, translations are automatically created when populating the Translate to Type and Translate to No. fields and when the No. field is populated. When the No. field is empty, the functionality has been expanded to create translations based on the data in the Description field on the lines.	43698
Document and Templates	For the AU and NZ localization, the localized ABN No. field on the vendor is now used as the primary validation when identifying a vendor using the identification template. If the ABN No. is not recognized, the vendor is identified using the VAT No. field.	43733
Document and Templates	XML template descriptions have been updated to include the country code of the country that uses the XML template.	44010
Document and Templates	Multiple tooltips on the Document Journal, Document Card, and Match Lines pages have been improved.	44685
Document Approval	Support for approval of purchase orders and purchase return orders using Continia approval workflows have been added. Most of the functionality available for purchase invoices and credit memos is also available for purchase orders and purchase return orders. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/document-approval/support-for-purchase-orders-and-return-orders-in-the-continia-approval-workflows	16562
Document Approval	The Continia Web Approval Portal has been extended to support the approval of purchase orders and purchase return orders. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/web-approval-portal/support-for-purchase-order-approval-using-the-continia-web-approval-portal	38943
Document Approval	On the Approval Flow lines page (Approvers), the Approver ID field has been added to show the User ID of the approver.	40331
Document Approval	When determining if a purchase document can be auto-approved, several checks are performed (e.g., if the imported amounts are equal to the assigned amounts and if matched orders have been approved). If any of these checks fail, the user who registers the document is informed about the reason, and the document is subsequently submitted into the normal approval flow. This information is now also stored as an approval comment, thus being available to the approvers. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/document-approval/displaying-automatic-approval-comments-during-the-approval-process	43520
Document Approval	It is now possible to specify per user to whom a given approver can forward. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/document-approval/user-specific-list-of-approvers-when-forwarding-approval-requests	43685
Document Approval	If the force approval workflow is not enabled, and the user enables the field Auto approve within variance on the Template Card page, the following confirmation message is displayed: Enabling "Auto approve within variance" will also enable the force approval workflow. Do you wish to continue? The force approval workflow is enabled when confirming the message, provided the user has the required permissions. If not, a permissions error occurs.	43697
Document Approval	Actions to open the Web Menus and PDF Report Setup pages have been added to the Document Capture Setup / Continia Web Approval page.	44070
General Application	The possibility to select a specific VAT Business Posting Group for the accounts for amounts translations has been added. If the Translate To Type is either Purchase Contract or Amount Distribution Code VAT Business and VAT Product Posting Group is cleared and disabled.	20148
General Application	The add-ins used by Document Capture have been updated to resemble the standard layout used in Business Central.	28329
General Application	The Document Card has been added to the repeater (shortcut) menu in the No. column on the Document Journal.	28534
General Application	When changing specific fields on the Continia Web Portal Card and Continia Web Portal List pages, the following notification is shown. You must export users after you have changed [the changed fields caption]. The notification is shown when changing the following fields: Continia Web Portal Web Site URL All Web Service Settings fields All Office 365 Authentication fields	29974
General Application	The extended text lines for items are now added when registering a document in the sales category.	38952
General Application	The Documents File Factbox has been redesigned and is now shown using a list page part. This allows for easy customizations and additions of columns.	39203
General Application	In many list pages, Microsoft has removed the word "list" and replaced it with "s" (plural) from the page caption. Similar changes have been made in Document Capture.	40539
General Application	The Use Unidentified Company Documents field on the Document Capture Setup page is now only visible when there are two or more companies with Document Capture activated.	41005
General Application	Help links referring to Continia Docs have been added to multiple Document Capture pages.	41611
General Application	The XML master template FATTURA has been added for all localizations.	41656
General Application	To comply with the Universal Code initiative, the following has been changed. A new Document Storage Type named File Service has been added. The File Service storage type is used to access locally stored files (PDFs, images, etc.) through a new Continia File Service. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/platform-and-technology/support-for-the-business-central-universal-code-initiative https://docs.continia.com/en-us/continia-document-capture/new-and-planned/platform-and-technology/support-for-local-file-system-storage-with-the-business-central-universal-code-initiative	41712
General Application	When changing the Company Code on the Continia Company Setup page, the function Export OCR Configuration Files is now automatically executed.	41735
General Application	In Business Central 2022 release wave 2 (BC v21), the standard attachment factbox is now hidden on purchase invoices and credit memos pages if Document Capture is activated and no attachments exist in the standard factbox.	41817
General Application	The Accounts for Amounts page action has been moved from the Translations category to the Template category. The page has also been renamed from Posting Setup to Accounts for Amounts, and several captions have been updated to reflect the usage better.	42059
General Application	Added validation code to the EWS Client Secret field on the CDC Document Category table to prevent common input mistakes.	42452
General Application	The OIOUTS document related to an OIOUBL invoice sent for approval was not shown in the Continia Web Approval Portal. Now the OIOUTS document is available in the attachment list, and the styled view can be shown in the document viewer or downloaded. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/web-approval-portal/displaying-oiouts-documents-in-the-continia-web-approval-portal	42701
General Application	In the Documents for Import list, a new action, Mark as Processed, has been added. This action will mark the selected network documents as processed and will prevent the marked documents from being automatically imported again.	43296
General Application	When security filters were applied on the Purchase Header table to restrict the view on Purchase Orders, the following error occurred when opening the Assign to Me page: A security filter has been applied to table Purchase Header. You cannot access records that are outside of this filter.	43357
General Application	The word Check has been removed from the captions under the Checks and Validation section on the Document Capture Setup / Purchase Approval page.	43588
General Application	The Description field has been added to the Assigned Documents and Assigned to me pages.	43649
General Application	In the Template List page, the Source ID field caption is automatically changed according to which source table (vendor/customer) the category belongs to. Besides that, the field Source Name is renamed to Name.	44139
General Application	The Continia Notifications module has been introduced, enabling you to receive notifications about operational statuses and important releases directly inside Business Central. Note that if you have a closed on-premises environment and upgrade to the latest version of Document Capture, it's important that you allow outgoing traffic to the Continia Notifications addresses specified under Firewall requirements. Otherwise, you'll be unable to receive any notifications from Continia.	45468
Order & Receipt Matching	Two new line fields have been added to the purchase master template. Vendor Shipment No. Vendor Order No. On the equivalent header fields, a validation codeunit that carries out auto match has been added. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/order-and-receipt-matching/support-for-vendor-shipment-numbers-and-vendor-order-numbers-on-lines	42120
Order & Receipt Matching	The performance of the matching process has been improved when matching header amounts (when no lines have been recognized on the document).	43031
Order & Receipt Matching	When a document is not automatically matched because the match difference exceeds the allowed variance settings on the template, the following document comment is created: WARNING: Our Order No. = '[Our Order No.]' exists but outside the tolerance settings. The best match found differs with [Match Difference Amount] but is not used as the maximum variance allowed is [Maximum Allowed Variance Amount].	43516
Order & Receipt Matching	If a value has been captured in either of the fields Vendor Order No. or Vendor Shipment No., the page Invoice Match will show the actions to filter purchase receipt lines and/or purchase order lines to only display the lines associated with documents with the specified values.	43521
Order & Receipt Matching	The page shown when doing a lookup in the template field Our Order No. has been redesigned to include the following fields: Vendor No. Vendor Name Posting Date Document Date Purchaser Code Vendor Order No. Vendor Shipment No. Currency Code Amount Excl. VAT Amount Incl. VAT	43525
Platform and Technology	With Document Capture 2023 R1 (11.00), we have released Document Capture for Microsoft Dynamics 365 Business Central 2023 release wave 1 (BC22). Document Capture 2023 R1 (11.00) in Business Central online will not be available for Microsoft Dynamics 365 Business Central 2022 release wave 2 (BC21). You will only be able to use Document Capture 2023 R1 (11.00) in Business Central online when you have upgraded to Microsoft Dynamics 365 Business Central 2023 release wave 1 (BC22).	32407
Platform and Technology	With the release of Document Capture 2023 R1 (11.00), we have released an upgrade tool that enables direct upgrade to Document Capture 2023 R1 (11.00) from the following versions: Document Capture 2021 R2 (8.00) Document Capture 2022 R1 (9.00) Document Capture 2022 R2 (10.00) The direct upgrade tool (Direct Upgrade to Document Capture 11.00 & Expense Management 11.00 - FOB), can be downloaded from PartnerZone. For details, please see Upgrading to Continia Document Capture 2023 R1 (11.00) for FOB versions.	41917
Platform and Technology	With the release of Document Capture 2023 R1 (11.00), we only support the following versions (BC v14 and the three latest versions of Business Central): Business Central April 2019 (BC v14) Business Central 2022 release wave 1 (BC v20) Business Central 2022 release wave 2 (BC v21) Business Central 2023 release wave 1 (BC v22) Even though we only support four versions of Business Central in Document Capture 2023 R1 (11.00), we will still support other versions of Business Central in future service packs for Document Capture 2022 R2 (10.00).	42558
Platform and Technology	The Continia Web Approval Portal has been updated to version 1.27.3	45904
Platform and Technology	When installing Document Capture we previously automatically installed the Continia Document Capture OnPremise app. Now, this only happens when upgrading from a previous version. For more information, see Installing Continia Document Capture On-Premises.	45930
Platform and Technology	When running Document Capture for Business Central 2023 release wave 1 (BC v22) on-premises, the following features now utilize services in Continia Online: Split and Merge Create styled XML	46051
Platform and Technology	The download packages for the OnPrem Apps have been changed, so we now only have 2 packages. The first package is the for the NA apps (this package differs from the rest, because we also include the NA apps). The second package is for all other localizations.	46135
Purchase Contracts	A new date formula field, Max. Allowed Approv. Date Var., has been added to the Purchase Contracts Setup page. The field is used to set a maximum allowed approval date variance when checking if the posting date of a document is within the invoicing period of the purchase contract and, thereby, whether the document can be auto-approved. When no value is entered, 3D is used as the default value.	41147
Purchase Contracts	When creating a purchase contract from the Document Journal, we now check if the related vendor has any existing purchase contracts and provide a list of these purchase contracts to select from.	41247
Purchase Contracts	Added support for shortcut dimensions to Purchase Contract lines.	41688
Purchase Contracts	Purchase contract lines, which relate to an approved or posted purchase invoice, can no longer be deleted. The Show Outdated Lines and Hide Outdated Lines actions have been added to the Purchase Contract subform. These actions filter purchase contract lines on the subform and show or hide outdated lines. A contract line is outdated when it has been canceled for more than one review iteration. A new configuration switch, Hide Outdated Contract Lines, has been added on the Purchase Contract Setup page. The setting specifies whether the contract lines subpage defaults to show or hide outdated contract lines.	41691
Purchase Contracts	When looking up the Vendor Name in the Purchase Contract card, the currently selected vendor is now highlighted in the opened list.	42531
Purchase Contracts	When registering a document (invoice) related to a purchase contract, the purchase contract dimensions are now applied to the purchase invoice.	42568
Purchase Contracts	A new field, Vendor Contract No., has been added to the Purchase Contract page. The field is used to specify the vendor's contract number. Additionally, a new header field Vendor Contract No. has been added to the purchase master template. A new validation codeunit has also been added. It is used to populate the Account No. field on the document header with the purchase contract number found using the Vendor Contract No. field on the Purchase Contract page. Furthermore, the codeunit links the recognized lines and the contract lines if the values for Account Type, Account No., Quantity, and Unit Cost are the same. A warning comment will be created indicating if some or no lines could be linked to the contract lines.	42597
Purchase Contracts	The Start Review Batch action is now always enabled on the Purchase Contract List page.	42629
Purchase Contracts	An action to open the related Purchase Contract has been added to Purchase Invoice and Document Journal pages.	42727
Purchase Contracts	It is now possible to create purchase contract templates, which can be used to populate purchase contract values when creating a purchase contract from the Document Journal or Document Card. You must run a few codeunits to add the permissions. For details, please see the following article. https://docs.continia.com/en-us/continia-document-capture/development-and-administration/document-capture-permissions#updating-permissions-when-implementing-service-packs	42728
Purchase Contracts	The following has only been developed in Microsoft Dynamics 365 Business Central 2022 release wave 1 (BC v20) and newer versions. The functionality to create purchase contracts has been added to the Purchase Order and Purchase Return Order pages.	44616
Purchase Contracts	When selecting the Create Purchase Contract action, the lookup list is no longer shown if only one eligible contract is available. Instead, the purchase contract is linked to the document automatically.	45336
Purchase Documents	Dimension checking has been improved when registering purchase documents. To activate the dimension check, go to the Document Capture Setup page and enable the Check Dimensions on Register option. The dimension check applies to templates with the following settings in the Purchase FastTab: Invoice Reg. Step 1 = Create Invoice or Match Order & Create Invoice Purch. Cr.Memo Reg. Step 1 = Create Credit Memo or Match Return Order & Create Credit Memo For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/documents-and-templates/checking-for-dimensions-on-document-registration	14663
Purchase Documents	Support for purchase order prepayment has been added. For further information, please see the following article on Continia Docs: https://docs.continia.com/en-us/continia-document-capture/new-and-planned/purchase-documents/support-for-prepayments	28507
Purchase Documents	The Force Approval action has been moved from the Request Approval menu group to the Approval group on the invoice and credit memo pages in the Document Capture app versions.	42459

Bug fixes

All relevant bug fixes released in service packs 1 to 2 (including hotfixes to these) for Document Capture 2022 R2 (10.00) are also included in Document Capture 2023 R1 (11.00). The description of these bug fixes is not repeated on this page.

Functional area	Description	ID
Country and Regional	Several Polish captions were wrong due to an encoding issue. This meant that some Polish letters were not displayed - instead, a random character was shown.	42234
Country and Regional	When a purchase contract has been submitted for review in the Danish localization, the caption Afsendt til gennemgang has been changed to Gennemgang indsendt. Generally, the Danish caption reviewer is changed to gennemgangsbruger.	44921
Document and Templates	When populating First Table Line Has Captions on a template, it was not possible to capture all lines.	30843
Document and Templates	To prevent fraud, the template field Invoice Reg. Step 2 for purchase documents (categories PURCHASE and PURCHORDER) can now only be updated to Release or Post by users configured as approval administrators. When changing the Invoice Reg. Step 2 option from Release or Post to Submit for Approval or [empty], a message is shown if the user is not an approval administrator. The message informs the user that after updating the value, the field can't be changed back to the previous value, and to change the field back, an approval administrator must be contacted.	39333
Document and Templates	The document header fields were not shown when opening the Document Journal page in Business Central 2021 release wave 1 (BC v18).	42215
Document and Templates	When opening the Document Journal page, the following error occurred in some situations. The SELECTSTR comma-string ,G/L Account,Item,Resource,Fixed Asset,Charge (Item),,Amount Distribution Code,Purchase Contract does not contain a value for index <index value> Page Edit - Document Journal must close The error happened due to incorrect input into the new Account Type field. Validation has been added to prevent this.	42420
Document and Templates	The below configurable message can now also be configured as Information. WARNING: Due Date = Invoice Date Previously the available options were Warning and Error.	45440
Document and Templates	After moving a document to another company, the preview was not shown for documents created from XML files.	45473
Document and Templates	An update to Business Central caused the XML Styled view to show strange characters instead of the expected special characters (e.g., æ ø å). This was caused by a wrong encoding used when showing the XML Styled view for the following XML formats: UBL OIOUBL OIOUTS OIOXML EHF SVEFAKTURA FINVOICE FATTURA FACTURAE EBINTERFACE The stylesheet files in Continia Online have been updated to correct the problem with the special characters. You can read more about how to manually change the stylesheets and correct the XML styled view for all open documents by following the instruction in the following article (available for Continia partners only): https://continia.zendesk.com/hc/en-us/articles/10444117845266-Problems-with-special-characters-in-the-XML-Styled-view	45708
Document and Templates	When having two XML Master templates with the same XML Identification Template and selecting Recognize Fields on an XML document, the following error occurred: The following C/AL functions are limited during write transactions because one or more tables will be locked. Form.RunModal is not allowed in write transactions. Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed. Report.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'Report.RunModal(...,FALSE)' is allowed. XmlPort.RunModal is allowed in write transactions only if 'RequestForm = FALSE'. For example, 'XmlPort.RunModal(...,FALSE)' is allowed. Use the COMMIT function to save the changes before this call, or structure the code differently.	45710
General Application	The arrows and the text field above the Document Viewer on the Split and Merge Documents page have been removed.	43002
General Application	The following is only relevant for the Danish localization. Corrected the value in the Status field under Købsgodkendelse on the Document Capture Setup / Purchase Approval page. From Aktiveret for fakturaerFakturaer og Kreditnotaer to Aktiveret for Fakturaer og Kreditnotaer	44130
General Application	When Use Cloud OCR is false, and when using the same file path for PDF File Path for OCR, File Path for OCR-processed files, or XML File Path, the following error is shown: [FieldCaption] ([FilePath]) must not be equal to [FieldCaption].	44380
General Application	The caption of the Document Viewer factbox on the Split and Merge Documents page has been changed from Original document to Page. On the following pages, the dropdown on the Document Viewer factbox has been removed: Split and Merge Documents Unposted and posted Purchase Invoices/Credit Memos/Orders Unposted and posted Sales Invoices/Credit Memos/Orders	45244
Order & Receipt Matching	When registering a document after matching it against purchase order lines with different Direct Unit Cost or Line Discount %, the following error occurred: Purchase Order Line (Line No, <Line No>) has been matched to two receipt lines with either a different Direct Unit Cost Excl. VAT or Line Discount %. The error message has been changed to the following: Purchase Order Line (Line No, <Line No>) has been matched to two or more order/receipt lines with either a different Direct Unit Cost Excl. VAT or Line Discount %.	41855
Order & Receipt Matching	When entering a value in Vendor Shipment No. or Vendor Order No. that exceeded 20 characters, the following error occurred: The length of the string is <string length>, but it must be less than or equal to 20 characters. Value: <vendor shipment no>	41937
Platform and Technology	When using Azure Blob storage and an error occurs during the communication with Azure Blob, the error message returned is now shown.	39213
Purchase Contracts	When using the Create Purchase Contract action from the Purchase Invoice page, the following error was thrown: You do not have the following permissions on TableData Job Task Dimension: Read.	46158
Purchase Contracts	When submitting the review of a Purchase Contract, the following error was thrown if the user had the permission sets for reviewers (https://docs.continia.com/en-us/continia-document-capture/development-and-administration/document-capture-permissions#permission-sets-for-reviewers): You do not have the following permissions on TableData CDC Review Cmt. Line Arch.: Modify.	46164

Table of Contents

Detailed Changelog for Continia Document Capture 2023 R1

Document Capture 2023 R1 Service Pack 3

New or changed functionality

Bug fixes

Document Capture 2023 R1 Service Pack 2, hotfix 2

Bug fixes

Document Capture 2023 R1 Service Pack 2, hotfix 1

Bug fixes

Document Capture 2023 R1 Service Pack 2

New or changed functionality

Bug fixes

Document Capture 2023 R1 Service Pack 1, hotfix 1

Bug fixes

Document Capture 2023 R1 Service Pack 1

New or changed functionality

Bug fixes

Document Capture 2023 R1, hotfix 5

Bug fixes

Document Capture 2023 R1, hotfix 4

Bug fixes

Document Capture 2023 R1, hotfix 3

Bug fixes

Document Capture 2023 R1, hotfix 2

Bug fixes

Document Capture 2023 R1, hotfix 1

Bug fixes

Document Capture 2023 R1

New or changed functionality

Bug fixes

Is this page helpful?