Detailed Changelog for Continia Document Capture 2020

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

Document Capture 2020, service pack 2

Released: December 22, 2020
App version: 6.5.2
FOB version: 6.50.02


Functional areaDescription
EventsThe following events are added to the solution:
  • Codeunit 6085705 CDC Purch. - Validation
    - OnBeforeTotalAmountNegCheck
  • Codeunit 6085709 CDC Purch. Doc. - Management
    - OnAfterGetIsInvoice
    - OnBeforeSplitPurchOrderLine
  • Codeunit 6085720 CDC Purch. Alloc.-Post
    - OnBeforePostGenJnlLineLoop
    - OnBeforePostGenJnlBalAcc
  • Codeunit 6085790 CDC Approvals Bridge
    - OnSendDocumentForApproval
MatchingThe match warning "No Match" has been made configurable. The message type can be changed to Information, Warning, or Error.
MatchingThe warning "Payment Terms (<Payment Term Code>) is not correct." is now configurable as information.
MatchingThe warning "Our Order No. = <Order No.> exist but outside the tolerance settings" has been made configurable. It can now be elevated to an error and thus be used for automatically delegating the document
TechnicalWith DC6.50 service pack 2, we have released objects for Microsoft Dynamics 365 Business Central Spring 2019 (BC14) on-premises update CU19.

Bug fixes for Document Capture 2020, service pack 2

Released: December 22, 2020
App version: 6.5.2
FOB version: 6.50.02


Functional areaDescription
Business CentralThe list "Approval Entries by Approver" has been split into 2 pages. One is used as a page part on the role center (page 6086078), and one available from the menu suite (page 6085708).
Client Controls & Add-insWe have corrected an issue where the Scanning and OCR page would lock and not import any files when scanning documents.
Continia Web Approval PortalThe Continia Web Approval Portal has been updated to version 1.16.0
Cloud and On-Prem OCR ServicesAfter completing a new Document Capture installation, emails containing XML-files were never received in Document Capture unless you manually exported the configuration files.
Cloud and On-Prem OCR ServicesFixed an issue where the Document Capture service would use the PDF file, instead of a skew-corrected version, to create the png-files for showing the document pages in the web client. This could cause the process of manually capturing values in the web client to produce unexpected results. The service is now changed to obtain the correct capture coordinates aligned with the web client's visual presentation.
Cloud and On-Prem OCR ServicesWhen importing documents from NAV 2009 SP1 or NAV 2009 R2 using the RTC-client, users received the following error:
  • This message is for C/AL programmers: The call to member SaveToFile failed: The file doesn't exist
Cloud and On-Prem OCR ServicesWe have optimized the import code when using Continia Online to prevent the same email file from being downloaded multiple times.
DocumentationWhen we released DC6.50, we forgot to write the following in the changelog:

If using external Office 365 accounts in the Continia Web Approval Portal, you can now specify a secondary email to use at login. The new "Office 365 Authentication Email" field has been added to the Continia User List page as a hidden field.
Documents and TemplatesDuring registration of a sales document and when a salesperson could be found from neither customer nor translations, the user was prompted with 3 options to choose from. Choosing the 3rd option ("Select from list") resulted in the document registration being aborted.
Documents and TemplatesWhen entering a fixed text with a length above 20 characters in the Formula Field on the Template Field card that has Data Type Text, the following error could occur:
  • The length of the string is <string length>, but it must be less than or equal to 20 characters. Value: <typed string>
Documents and TemplatesWe have corrected a bug that prevented QR content to be transferred on documents using the following functions: Move to/from Unidentified Company (UIC) Split/Merge Move to company.
Documents and TemplatesRecognize field on template could result in the following error:
  • 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.
This happened for documents if the following 3 criteria were met:
  1. The document had a vendor number but no template number.
  2. There were no existing templates for the vendor.
  3. More than one master template had been created for the document category.
The error occurred because a page was opened (for choosing a master template) while a write transaction was in progress. The code has now been restructured, so this no longer happens.
Documents and TemplatesIf no salesperson translation could be found, auto delegating to a user would assign the document to the first NAV/BC user with no salesperson in Continia User Setup.
Documents and TemplatesWhen using the Tab key to switch between fields in the Document Header Fields subpage, the switch was not behaving as expected.
Installation and SetupThe tile "Delegated to me" on the DC Role Center (Activities part) is now always shown.
Installation and SetupAdded the option to set up Azure Blob Storage when running the Document Capture Setup Wizard. Note, The page "CDC Doc. Capture Setup Wizard" now has a lower (NAV) version. Therefore, for clients running NAV 2017 or newer, this results in a warning during object import. You can safely choose to "Replace" for this object.
Installation and SetupFor Business Central on-premises, when only the Continia Document Capture 365 base app is installed (as opposed to the base app together with the Continia Document Capture 365 on-premises app) the File System option from the Storage Option field in the Document Capture Setup Wizard is no longer available.
Installation and SetupFor Business Central online, we have added the Azure Blob Storage option to the Storage Option field in the Document Capture Setup Wizard.
Installation and SetupThe obsolete copyright text has been removed from the "About Document Capture" page.
MatchingIn the Document Journal, when filtering the documents on Match Status = Unmatched, the following error could occur upon matching lines:
  • The Vendor does not exist. Identification fields and values: No.='' Upon returning to the Document Journal after matching lines, this error would occur: - The Document does not exist. Identification fields and values: Document Category Code='<Category Code>',Status='Open',No.='<Document No.>'
The errors could occur in any scenario where a filter was set on Match Status and the status was changed in the matching window.
MatchingWhen using the Card action to navigate to the Header (Shift-F5) from the order lines section on the Invoice Match page, the page opened showing a random return order if the order lines section did not contain any records. Now, the Card action on the order line section is disabled if there are no order lines present.
MatchingWhen a document was matched to an order line with an item with free item tracking, the following error could occur upon validation of the document:
  • The Purchase Line does not exist. Identification fields and values: Document Type='Order',Document No.='<Document No.>.',Line No.=<Line No.>''
MatchingWhen recognizing multiple order numbers, there used to be a limitation to the entire filter string to 20 characters. That limit has been increased to 250 characters - each order number is still limited to 20 characters.
MatchingIf a document had been matched to purchase receipt lines with item tracking and the lot or serial number on the item tracking had a length above 20 characters, the following error occurred when registering the document:
  • The length of the string is <string length>, but it must be less than or equal to 20 characters. Value: <string>
MatchingWe have corrected an issue that would prevent auto-match from matching one DC Document Line to two different order lines having the same line no, but different order nos.
MatchingWhen matching receipt lines, the following error could occur:
  • You do not have the following permissions on TableData CDC Match Tracking Spec.: Read.
MatchingWhen matching, the following error could occur:
  • The length of the string is <string length>, but it must be less than or equal to 21 characters. Value: <string value>
Purchase approvalIn NAV 2013, NAV 2013 R2, and NAV 2015 when submitting an invoice or credit memo for approval that was created in the following context: Matching against an order "Auto approve within variance" = yes the following error occurred:
  • The Purch. Rcpt. Line does not exist. Identification fields and values: Document No.='ORDER',Line No.='0'
Purchase approvalFor NAV 2018 (11.00.00) and newer versions, the Cancel Approval Request button on page 6085706 CDC Purch. Invoice With Image and 6085707 CDC Purch. Cr. Memo With Image was not shown, even though a Document Capture workflow was active and an Approval Request had been sent. For BC14 (14.00.00) and newer versions, the Cancel Approval Request button on page 6085706 CDC Purch. Invoice With Image was not calling Document Capture approval code.
Purchase approvalIn DC6.50, checking "Allow Register without Amounts" would also allow the approval of documents without amounts. This has now been fixed, so the check is again performed when approving (depending on the selected option in "Check Amounts on Approval" in Document Capture - Purchase Approval Setup)
Purchase approvalThe Reason Code description has been extended to 100 characters to support BC14 and newer versions.
Purchase DocumentsWhen opening the Document Capture Purchase Invoice list or Purchase Credit Memo list, the following error could occur:
  • Purchase Header: The VAT Amount Line does not exist. Identification fields and values: VAT Identifier='',VAT Calculation Type='Normal VAT',Tax Group Code='',Use Tax='No',Positive='Yes'
The error was caused by purchase lines (created by the intercompany functionality) with blank number and type, but with quantity <>0.
Purchase DocumentsWhen using DrillDown on the field Attached Documents in the Purch. Cr. Memo page, the DC Document was shown, and not the Attachment list.
TechnicalCodeunit 6085791 "CDC Create eDocuments Category" has been removed in the Danish packages as it is now obsolete.
TechnicalLicense information was not shown on the "About Document Capture" page.
TechnicalThe Document Capture changes in table 39 were not included in the release packages for the following versions: NAV 4.00 to NAV 2015 for DE, AT, and GB.
TranslationsThe SE caption for the "Continia Userlist" page has been changed from "Användarlista" to "Continia Användarlista" to reflect its use better.
TranslationsCaptions in wizards have been aligned with standard BC guidelines.
UI SimplificationThe "Approval Flow Code" visibility on page 138 "Posted Purchase Invoice" and page 140 "Posted Purchase Credit Memo" is now dependent on whether or not approval is activated in the given company.
UI SimplificationThe mail settings on the Document Category Card were not shown in NAV 2013.
UI SimplificationThe "Web Approval" captions in Document Capture pages have been renamed to "Continia Web Approval".
Users and PermissionsAdded full permissions to table 2000000076 "Web Services" for the "CDCSUPER" permission set.
Users and PermissionsTo increase the general performance, we now cache the result when determining if a user is using a Team Member license.
Web ApprovalIf a Web Menu with an Approval Code Filter had been set up in a company, this could cause the "Documents for Approval" in the web portal to be incorrect (often zero).
XML ImportWhen using Norwegian regional settings, the XML fields that have the SUM() operator was not returning any value.
XML ImportWhen a new XML document was imported, Document Capture always chose the template based on the XML identification field on the XML Identification Template, therefore, the search text on the templates was not taken into consideration.

Bug fixes for Document Capture 2020, service pack 1, hotfix 2

Released: December 7, 2020
App version: 6.5.1.1

Only released in Business Central online.


Functional areaDescription
Documents and TemplatesRecognize field on template could result in the following error:
  • 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.
This happened for documents if the following 3 criteria were met:
  1. The document had a vendor number but no template number.
  2. There were no existing templates for the vendor.
  3. More than one master template had been created for the document category.
The error occurred because a page was opened (for choosing a master template) while a write transaction was in progress. The code has now been restructured, so this no longer happens.
Documents and TemplatesThe following occurred when using auto-split on PDF-files containing invoices from several vendors.

Previously, the source and template would be determined based on the document's first page, resulting in the wrong source and template being applied to trailing invoices in the document.

Now, the templates (and sources) are being determined per page, so the correct source and template will be found, even when the same document contains invoices from more than one vendor.
Purchase DocumentsWhen opening the Document Capture Purchase Invoice list or Purchase Credit Memo list, the following error could occur:
  • The Purchase Header: The VAT Amount Line does not exist. Identification fields and values: VAT Identifier='',VAT Calculation Type='Normal VAT',Tax Group Code='',Use Tax='No',Positive='Yes,
The error was caused by purchase lines (created by the intercompany functionality) with blank number and type, but with quantity <>0.

Document Capture 2020, service pack 1

Released: October 1, 2020
App version: 6.5.1
FOB version: 6.50.01


Functional areaDescription
Business CentralMicrosoft Dynamics 365 Business Central 2020 release wave 2 (BC17) includes the following feature:
  • Feature Update: Write longer item references
Unfortunately, the feature is not yet supported when using Document Capture. We will support the feature in an upcoming service pack.
EventsThe following events are added to the solution:
  • Codeunit 6085575 CDC Capture Engine:
    - OnBeforeCaptureField2
    - OnAfterCaptureField2
    - OnBeforeBufferWords
  • Codeunit 6085576 CDC Capture Management:
    - OnBeforeUpdateFieldValue
    - OnAfterUpdateFieldValue
  • Codeunit 6085704 CDC Purch. - Line Validation:
    - OnBeforeLineValidation
  • Codeunit 6085706 CDC Purch. - Register
    - OnAfterCreateWithoutMatchSetAccountRequired
  • Codeunit 6085709 CDC Purch. Doc. - Management
    - OnBeforeCheckMatchToWithTrack
  • Page 6085593 CDC Doc. Capture Client Addin:
    - OnBeforeCaptureEnded
MatchingWe have added the following new event in Codeunit 6085709 "CDC Purch. Doc. - Management" (also mentioned in the list above):
  • OnBeforeCheckMatchToWithTrack(PurchOrderLine : Record "Purchase Line";MatchedToDocType : 'Receipt,Return Shipment,Order,Return Order';ShowError : Boolean;VAR Handled : Boolean)
The event allows partners to circumvent the test for reservation entries by doing their own checks in the subscriber event and set Handled = TRUE.
TechnicalWith DC6.50 service pack 1, we have released Document Capture for Microsoft Dynamics 365 Business Central 2020 release wave 2 (BC17).
TechnicalWith DC6.50 service pack 1, we have released objects for Microsoft Dynamics 365 Business Central Spring 2019 Update (BC14) on-premises CU16.

Bug fixes for Document Capture 2020, service pack 1

Released: October 1, 2020
App version: 6.5.1
FOB version: 6.50.01


Functional areaDescription
Business CentralIn DC6.50, we have refactored the XML handling code.

Many of the XML handling codeunits and functions have been moved from Document Capture to Continia Core. We have also changed the signature of many functions. In Business Central Cloud, Microsoft validates against the latest Document Capture version and not the version used by the tenant, thus generating errors when tenants were CU upgraded or when extensions were installed. To work around this, we have re-added the deleted codeunits and functions temporarily but marked them as obsolete. Please note the codeunit and functions are not implemented, and they are removed in DC6.50 service pack 1. Extensions using these codeunits and functions must, therefore, be updated before upgrading to DC6.50."
  • We've added shortcuts to the "Send for approval" and "Force approval" functions the following places and NAV/BC versions.
BC version 14.00.00 (DC6.00.05 and DC6.50.01):
  • Page 6085706 "CDC Purch. Invoice With Image"
  • Page 6085707 ”CDC Purch. Cr. Memo With Image"
Send for approval: Ctrl+S
Force Approval: Ctrl+F

App (6.5):
  • Pageextension 6085581 ”CDC Purchase Invoices”
  • Pageextension 6085580 ”CDC Purchase Invoice”
  • Pageextension 6085582 ”CDC Purchase Credit Memos”
  • Pgeextension 6085578 ”CDC Purchase Credit Memo”
Send for approval: Ctrl+Shift+S
Force Approval: Ctrl+Shift+F
Business CentralWhen Document Capture was run as an app and when users with a webservice key was exported to the Continia Web Approval Portal, the webservice key was not exported.
Client Controls & Add-insIn the web client, it is not possible to set the size of the document view factbox. To work around this, we have created a page an administrator can use to set the size for the relevant users. To set the size, run page 6086077 - CDC User Property List2 (by adjusting the URL) and change ”Add-In Min Width”. We suggest you start 750 or higher in ”Add-In Min Width” if the size of the document view factbox is too small.
Continia Web Approval PortalThe Continia Web Approval Portal has been updated to version 1.15.4.
Document Analysis and RecognitionWe have corrected a bug that prevented line capture on documents with more than 100 pages.
Document Analysis and RecognitionIn DC 6.50, after removing a line field from a document template that had line recognition, the following error could occur when recognizing fields:
  • The Template Field does not exist. Identification fields and values: Template No.='<Template No.>',Type='Line',Code='<Field name>'
The error occurred if one of the following five fields was removed: QUANTITY, UNITCOST, LINEAMOUNT, DISCAMOUNT, or DISCPCT.
Document Analysis and RecognitionThe system can calculate Quantity, Unit Cost, or Line Amount when two of the three before-mentioned fields are captured. The calculation also includes Discount Amount and Discount % when these values are captured. The calculation of Quantity, Unit Cost, or Line Amount was wrongly calculated if one of the five fields (Quantity, Unit Cost, Line Amount, Discount Amount, or Discount %) had a fixed value.

Quantity, Unit Cost, or Line Amount are now not calculated if one of the five fields has a fixed value.
Documents and TemplatesThe configuration files have been updated with the following changes:

For SE
“Cloud OCR Cache Timeout” changed from 0 to 5.

For BE
“Check Amounts on Approval” changed from No to Last Approval.

For BE-FR and FR
Web Dimension 1 Code (Header) changed from blank to DEPARTEMENT.
Web Dimension 2 Code (Header) changed from blank to DOSSIER.
Web Dimension 1 Code (Lines) changed from blank to DOSSIER.

For BE-UK
Web Dimension 1 Code (Header) changed from blank to KSTNPLAATS.
Web Dimension 2 Code (Header) changed from blank to KSTNDRAGER.
Web Dimension 1 Code (Lines) changed from blank to KSTNDRAGER.

For AT, CH, and DE
Web Dimension 1 Code (Header) changed from DEPARTMENT to ABTEILUNG.
Web Dimension 2 Code (Header) changed from PROJECT to KOSTENTRÄGER.
Web Dimension 1 Code (Lines) changed from PROJECT to KOSTENTRÄGER.
Documents and TemplatesWhen a vendor had no documents and the user selected the DrillDown on the vendor card, many documents were shown.
Documents and TemplatesWhen an email that contained both a PDF file and an XML file was imported, and the template found for the PDF had the ”Merge from the same E-mail” functionality activated the following error was thrown:
  • Combine - CreateGdPictureImageFromStream1 caused an error. Status: GenericError, Page: 0.
Documents and TemplatesIn DC6.50 the Identification field 11310 ”Enterprise No.” was not included in the ACHAT document category.
Documents and TemplatesWhen pressing the Add template field button in a Microsoft Dynamics NAV 2009 R2 RTC version the following errors were thrown:
  • Function ID 2 was called. The object with ID 6085635 does not have a member with that ID.
    The identifier 'StrongColumn' could not be found.
Documents and TemplatesAdding a new field to a template could result in the following error:
  • The length of the string is 55, but it must be less than or equal to 50 characters. Value: <Field Name>
The error occurred when the length of the field name of the new field was over 45.
Documents and TemplatesAssigning a vendor to a document could result in the following error:
  • You do not have the following permissions on TableData Vendor: Read
The error occurred if the Vendor did not have a default template in the current company, but had one in another company where the user had read access to template and document category tables (CDC-ALL Permission set) and no read access to the Vendor table.
Documents and TemplatesWe have corrected an issue that allowed documents in categories without master templates to be registered without a Source ID.
Documents and TemplatesWhen trying to recognize documents from categories with a source table different from vendor, the following error occurred:
  • The Vendor does not exist. Identification fields and values: No.='<source no>'
Documents and TemplatesIn NAV 2009 to NAV 2013 R2 (6.00.00 to 7.10.00) using the RTC client, you got the following message when opening Document Capture Setup:
  • The identifier AzureBlobEnabled could not be found
Documents and TemplatesIn NAV 2009 to NAV 2009 R2 (6.00.00 to 6.00.10) using the RTC client, the client would crash if you changed the Document File Storage to Azure Blob Storage.
EventsThe following Event Publishers were introduced in Codeunit 6085790 - CDC Approvals Bridge in Document Capture 6.00 service pack 4, but they were not available in Document Capture 6.50:
  • OnBeforeSendPurchDocApprovalRequest
  • OnBeforeForward
  • OnAfterRejectApprovalRequests
  • OnBeforeCancelApprovalRequest
  • OnBeforeFilterPurchAppWorkflows
  • OnBeforeIsPurchForceApprEnabledDocType
  • OnAfterSetApprovalButtons
EventsThe Event Publisher OnBeforeAdjustMissingQty in Codeunit 6085703 - CDC Purch. - Full Capture was introduced in Document Capture 6.00 service pack 4, but in Document Capture 6.50, it was by mistake renamed to OnBeforeAdjustQty. With service pack 1 for Document Capture 6.50, the Event Publisher is again named OnBeforeAdjustMissingQty.
Installation and SetupDocument Storage Type Azure Blob Storage was wrongly shown in the classic client.

When selecting Azure Blob Storage, the following error occurred:
  • You must specify Storage Account Name in Document Capture Setup Primary Key=''.
Installation and SetupWhen we released DC6.50, we wrote the following in the changelog:
  • We are now supporting Azure Blob Storage as a third Document Storage Type option. Customers must use their own Azure Storage account.
We forgot to mention that we only support Azure Blob Storage from NAV 2013 and newer versions of NAV/BC.
MatchingWhen we released DC6.50, we wrote the following in the changelog:
  • We have added support for partial matching of purchase receipt and return shipment lines with lot or serial number tracking.
    The full changelog text is available further down under New Features for DC6.50
We forgot to mention that we only support partial matching of purchase receipt and return shipment lines with lot or serial number tracking from NAV 2013 and newer versions of NAV/BC.
MatchingCorrected a bug that would prevent auto-match from matching lines with account type different from Item.
MatchingWhen an invoice has been partially matched to two or more purchase orders and when the function ”Create Line On Purchase Document” is invoked, the following has been changed:
  • All fields are populated on the purchase list lookup page.
  • If pressing cancel to the lookup, the ”Create Line On Purchase Document” function is aborted.
Purchase ApprovalUnder certain conditions when using ”Forward without approval”, the approval hierarchy was not recreated from the user to whom the document was delegated.
Purchase ApprovalThe shortcut dimension fields in Document Capture pages had names that were different from the equivalent fields in standard pages. The different naming could lead to some confusion when trying to add the fields to a page. Now, they are all named ShortcutDimCode3 to ShortcutDimCode8.

The change affects the following pages:
  • 6085701 ”CDC Purch. Line Translations”
  • 6085714 ”CDC Header Amount Posting”
  • 6085740 ”CDC Purch. App. Entries Subp.”
  • 6085776 ”CDC Std. Amt. Distr. Code Subp”
Purchase DocumentsWhen Quantity, Unit Cost, or Line Amount values were automatically calculated and resulted in values that had a 1000 separator and no decimals, the values would be misinterpreted by the system.

Where regional setting for one thousand = 1.000,00: Quantity was calculated to 1.900 and stored as 1,9

Where regional setting for one thousand = 1,000.00: Quantity was calculated to 1,900 and stored as 1.9

This was caused by an error in function AdjustmissingFields, that is now fixed.
TechnicalWhen we released DC6.50, we wrote the following in the changelog:
  • We are now supporting Azure Blob Storage as a third Document Storage Type option. Customers must use their own Azure Storage account.
We forgot to mention that we only support Azure Blob Storage from NAV 2013 and newer versions of NAV/BC.
TechnicalWe have populated the AdditionalSearchTerms property in many AL pages with the values used in the MenuSuite in RTC to allow the pages to be found when using search in BC15 and newer versions.
TechnicalWhen running RTC in NAV 2009 to 2009 R2, and doing drill down in the ”No. of Documents” field on the Vendor page, the following error occurred:
  • The table IDs do not match.
This was caused by the wrong page being opened.
TranslationsCaptions have been updated and improved.
TranslationsTranslation mistakes have been corrected.
TranslationsWrong Germany translations have been corrected.
TranslationsWe have updated NOR and ESP captions on page 6085721.
TranslationsIn the DC App, page extensions were not translated. This meant that fields and actions added to, for example, the Purchase Invoice, Purchase Credit Memo, and Vendor Card were not translated, and captions were always shown in English.
TranslationsWhen importing documents in the Norwegian and Swedish localisations, the following error occurred:
  • NOR: Finner ikke objekt-ID.
  • SVE: Det gick inte att hitta objekt-ID.
UI SimplificationWe have aligned the field cue names (in cue setup) with the captions on the role center tiles.
XML ImportAll test XML files located in the product folder had the same purchaser name (Richard Lum). Now the purchaser's name is specific to the localization and the data in the CRONUS demo databases for better demo scenarios.

Document Capture 2020, hotfix 2

Released: September 18, 2020
App version: 6.5.0.2

DC6.50 hotfix 2 has only been released for the cloud APPs. The below-listed issues will be corrected in DC6.50 SP1 for the on-premises Apps and FOB based versions of NAV.


Functional areaDescription
Business CentralIn DC6.50, we have refactored the code. Many of the XML handling codeunits and functions have been moved from Document Capture to Continia Core. We have also changed the signature of many functions. In Business Central Cloud, Microsoft validates against the latest Document Capture version and not the version used by the tenant. This meant errors occurred when tenants were CU upgraded or when extensions were installed. We have re-added the deleted codeunits and functions temporarily and marked them as obsolete to work around this. Note the codeunit and functions are not implemented, and they will be removed in DC6.50 service pack 1. Extensions using these codeunits and functions must, therefore, be updated before upgrading to DC6.50.
Document Analysis and RecognitionIn DC 6.50, after removing a line field from a document template that had line recognition, the following error could occur when recognizing fields:
  • The Template Field does not exist. Identification fields and values: Template No.='<Template No.>',Type='Line',Code='<Field name>'
The error occurred if one of the following five fields was removed: QUANTITY, UNITCOST, LINEAMOUNT, DISCAMOUNT, or DISCPCT.
Document Analysis and RecognitionThe system can calculate Quantity, Unit Cost, or Line Amount when two of the three before-mentioned fields are captured. The calculation also includes Discount Amount and Discount % when these values are captured. The calculation of Quantity, Unit Cost, or Line Amount was wrongly calculated if one of the five fields (Quantity, Unit Cost, Line Amount, Discount Amount, or Discount %) had a fixed value.

Quantity, Unit Cost, or Line Amount are now not calculated if one of the five fields has a fixed value.
Documents and TemplatesWhen an email that contained both a PDF file and an XML file was imported, and the template found for the PDF had the "Merge from the same E-mail" functionality activated the following error was thrown:
  • Combine - CreateGdPictureImageFromStream1 caused an error. Status: GenericError, Page: 0.
EventsThe following Event Publishers were introduced in Codeunit 6085790 - CDC Approvals Bridge in Document Capture 6.00 service pack 4, but they were not available in Document Capture 6.50:
  • OnBeforeSendPurchDocApprovalRequest
  • OnBeforeForward
  • OnAfterRejectApprovalRequests
  • OnBeforeCancelApprovalRequest
  • OnBeforeFilterPurchAppWorkflows
  • OnBeforeIsPurchForceApprEnabledDocType
  • OnAfterSetApprovalButtons
EventsThe Event Publisher OnBeforeAdjustMissingQty in Codeunit 6085703 - CDC Purch. - Full Capture was introduced in Document Capture 6.00 service pack 4, but in Document Capture 6.50, it was by mistake renamed to OnBeforeAdjustQty. With service pack 1 for Document Capture 6.50, the Event Publisher is again named OnBeforeAdjustMissingQty.

Document Capture 2020, hotfix 1

Released: September 10, 2020
App version: 6.5.0.1

DC6.50 hotfix 1 has only been released for the on-premises and cloud APPs. The below-listed issues will be corrected in DC6.50 SP1 for the FOB based versions of NAV.


Functional areaDescription
Document Analysis and RecognitionWhen trying to recognize documents from categories with a source table different from vendor, the following error occurred:
  • The Vendor does not exist. Identification fields and values: No.='<source no>'
MatchingCorrected a bug that would prevent auto-match from matching lines with account type different from Item.
TranslationsIn the DC App, page extensions were not translated. This meant that fields and actions added to, for example, the Purchase Invoice, Purchase Credit Memo, and Vendor Card were not translated, and captions were always shown in English.
TranslationsWhen importing documents in the Norwegian and Swedish localisations, the following error occurred:
  • NOR: Finner ikke objekt-ID.
  • SVE: Det gick inte att hitta objekt-ID.

Document Capture 2020

Released: September 1, 2020
App version: 6.5.0.0
FOB version: 6.50

Events and features released in service pack 1 to 4 for DC6.00 are also included in DC6.50. The description of these events and features are not all repeated in this document.


Functional areaDescription
Client and Company ActivationIn NAV 2017 and newer versions, a notification is shown in the Document Journal when an agreement (license, terms, or alike) with Continia Software is not accepted within the given timeframe.

From NAV 2016 and backward, a confirm dialog is shown to accept the missing acceptances.
Cloud and On-Prem OCR ServicesAdded support for Exchange Web Services (EWS) with Oauth 2.0 when running on-premises OCR processing.
Continia Delivery NetworkUnfortunately, the Continia Delivery Network is delayed. We are planning to release the Continia Delivery Network as soon as the development is complete and release the Continia Delivery Network as an optional feature in a future service pack.
Continia Web Approval PortalThe Continia Web Approval Portal has been updated to version 1.14.3.0.
Documents and Templates“Credit Note" has been added as a caption for the "[I]nvoice / [C]r. Memo" field in the purchase category for the following localizations: AU, NZ, BE-UK, NA, and W1.
Documents and Templates"C: Credit Memo" has been added as a caption for the "[I]nvoice / [C]r. Memo" field in the purchase category for the following localizations: GB.
Documents and Templates"K: Kreditfaktura" has been added as a caption for the "[I]nvoice / [C]r. Memo" field in the purchase category for the following localizations: SE.
Document Analysis and RecognitionWe have added support for capturing the full content of QR barcodes, which can be longer than the normal limit of 250 characters. The value is available for custom processing codeunits using the GetFullText on the "CDC Document Value" table. You must update the on-premises Document Capture service to utilize the new functionality.
Document Analysis and RecognitionThe warning message “Currency code was taken from the Vendor” has been made configurable, thus enabling the user to set the message type to Information, Warning, or Error.
Document Analysis and RecognitionSelected validation messages shown in the document journal and card have been made configurable. For these messages, it is now possible to configure if the message type should be information, warning, or error. This can, for example, be used to change a warning comment to an information comment and thereby allow batch postings when this comment is created.
Document Analysis and RecognitionIt’s now possible to delegate a DC document to a specific user. A new column, “Delegated To User ID” has been added to the Document Journal (hidden by default). The document can manually be delegated by assigning a User-ID in the field. If the system is set up to generate delegation comments automatically, the system will attempt to delegate the document to the relevant user automatically. The user is identified by the mapping of “Our Contact” to a purchaser code, which is then used to determine the User ID though “Continia User Setup”.
Document Analysis and RecognitionA new tile (“Delegated to me”) has been added to the DC role center activities, showing the no. of delegated documents. The user can open the list of delegated documents by clicking on the tile or search for “Delegated Document List”.
Document SearchOn the Document Search page, now the buttons are only enabled when they can be used.
EventsThe following events are added to the solution:
  • Codeunit 6085640 CDC Doc. File Events
    - OnHasFile
    - OnClearFile
    - OnGetFile
    - OnSetFile
  • Codeunit 6085706 CDC Purch. – Register
    - OnBeforePerformStep2
    - OnBeforeShowAfterRegister
    - OnAfterTransferPurchLine
  • Codeunit 6085709 CDC Purch. Doc. - Management
    - OnBeforeGetLineTranslAccountNo
For more information about the events, please see the Document Capture Event Publishers in Zendesk: https://continia.zendesk.com/hc/en-us/articles/360011491120-Document-Capture-Event-Publishers
MatchingThe column "Line Amount (Order)" has been added to the receipt line matching page. The field shows the calculated line amount using the matched quantity, "Unit Cost," and the discount information from the order.
MatchingThe following two new filter buttons are added to the matching page:
  • Filter on Unmatched Only
  • Filter on Match Differences
MatchingTransfering location code from a DC Document (using “Transfer value to Field” in purchase line) to an Invoice/Credit Memo, matched against an Order/Return Order, caused a recalculation of the unit cost according to standard BC/NAV setup thus losing the matched unit cost.

NB: The location code cannot be updated when matching against a receipt or return shipment due to limitations in the standard BC/NAV application.
MatchingA new function to split a line on a purchase order (PO) has been added (“Split Line” on the order lines subpage). The function is intended to be used when a PO was created with an estimated cost. As an example, imagine a small project “Exchange and calibrate new locks in building” estimated cost $10.000,00. If the project costs are split on multiple invoices. E.g.,
  • Invoice 1 - New locks = $7.300,00 and
  • Invoice 2 - Calibration and mounting = $2.700,00.
MatchingTo match the two invoices properly against the PO, it is beneficial to split the original PO line in two. That process can easily be achieved using the “Split Line” function.
MatchingWhen using order match with line recognition enabled, it's now possible to use the information on the recognized document line to add additional lines (freight and other charges) to the existing purchase order. Place the cursor on the DC Document line that is missing on the purchase order and press "Create line on Purchase Document" in the top ribbon on the Match page.
MatchingWhen matching on unit cost (for line recognition only), you can configure a variance amount, variance percentage, or a combination of both. When enabling both variance parameters, DC uses the lower of the two calculated values to match the unit cost.
MatchingWe have added support for partial matching of purchase receipt and return shipment lines with lot or serial number tracking. Previously, when trying to do a partial match to a purchase receipt or a return shipment line with multiple tracking entries, the following error occurred:
  • It is not possible to make a partial match between Document <Document No.> and Receipt Line (<Receipt Line No.> <Line No.>) as multiple tracking entries exists for the receipt line.
Partial matching is now supported for purchase receipt and return shipment lines. Tracking entries are automatically matched if all the remaining items (not already matched or linked to an existing document) on the receipt/return shipment corresponds to the items on the invoice/credit memo. This also applies to auto-matching.

When invoicing one item, and more than one lot or serial number exists, the user must perform the lot/serial number matching manually on the item tracking level before posting. The user is notified in the comment sections if manual action is required.
MatchingPreviously it was only possible to match against order/receipt lines with “Pay-To Vendor No.” that matched the vendor on the DC Document. In this version, we’ve extended the match functionality to allow for the invoice to come from either Buy-From Vendor or the Pay-To Vendor, as long as the Buy-From/Pay-To relationship can be verified on the Buy-From Vendor Card.
MatchingAutomatic match can be scheduled by adding codeunit 6086022 “CDC Batch Match Document” as a recurring job queue entry.
MatchingWhen using matching and line recognition, the matched document numbers are now displayed in the comment area.
MatchingPreviously the matching functionality checked the location card for “Require Receive” before allowing order/return order match even when the template was configured to match against orders. If “Require Receive” on the location card was enabled, the matching against purchase orders (not receipts) was skipped.

Now, when the location card is marked with “Require Receive”, matching against orders can be completed if no receipt has been created, complying with standard Business Central.

When matching against an order where no receipt has been created, the lines are now auto-matched against the order. A warning telling the user that warehouse operations might disregard the information is added. Manual matching will result in a message containing the same warning.

If a receipt has already been created, matching against an order is not possible. When trying to match, the following happens: Auto match skips the line, and when matching manually, an error is shown to the user.
MatchingPreviously when matching return orders, a check was made for “Require Receive” on the location card. Now, matching Return Orders checks for “Require Ship” on the location card instead.
Purchase ApprovalAdvanced Approval is now supported in Business Central cloud.
Purchase ApprovalIf "Allow Register Without Amounts" on a template is populated and you process a document with the assigned amount equal to zero, Document Capture does not show a confirmation message displaying the difference between the assigned and imported amounts.
Purchase ApprovalFor the modern clients only (BC15 and BC16 web client): The fields "Unit Cost (Order)" and "Line Amount (Order)" are made available on the Purchase Invoice Lines page. The fields are hidden by default.
Purchase ApprovalYou no longer have to configure an “Approval E-Mail Subject” in Document Capture Setup or an “E-mail Subject” in Reminder E-Mail Setup as the subjects have been hardcoded in a text variable in the “CDC Purch. Approval E-Mail” codeunit to allowed multi-language support for the default values.
Purchase ApprovalWhen setting up Out of Office, it was previously possible to leave “From Date” or “To Date” blank. It is now enforced that both dates are populated.
Purchase ApprovalPurchase lines shown in the Document Capture approval entries page are now editable.

Editing pending approval documents lines in Business Central is now only possible, in NAV 2016 or newer, when “Can Edit Posting Lines” in “Contina User Setup” is enabled for the current user.
Purchase DocumentsWhen recognizing lines, if either Unit Cost, Quantity, or Line Amount are not recognized, the three fields are now calculated automatically. Previously, only Quantity was calculated automatically.

Recognizing two of the three fields and if all five fields (including the Line Discount Amount and Line Discount Percentage fields) have a blank value in Formula, the missing field is automatically calculated as specified below:
  • Line Amount = Quantity * Unit Cost - DiscAmount
  • Unit Cost = (Line Amount + DiscAmount) / Quantity
  • Quantity = (Line Amount + DiscAmount) / Unit Cost
If DiscAmount is Zero after capture (either not captured or captured as zero), DiscAmount is calculated as follows: DiscAmount = Line Amount * Line Discount % / 100

When one of the three fields is calculated, an error, warning, or information comment is inserted in the comment section, depending on the comment setup.

A new integration event has been added: OnBeforeAdjustMissingFields(VAR Document : Record “CDC Document”;VAR Handled : Boolean)

If customers wish to disable the auto-calculation of the three values, you create an event subscriber that changes the handled value to TRUE.

The integration event OnBeforeAdjustQty (introduced in 6.0 SP3) is deprecated in this release and is expected to be removed in version 8.00 (due to be released one year after version 6.50).
Purchase DocumentsThe purchaser from a matched purchase document is used on the invoice if no purchaser can be found in either purchaser translation or the Salesperson/Purchaser table (filtered on name recognized in "Our Contact").
Purchase DocumentsWhen a purchase invoice is created from Document Capture, the functionality for extended texts is now available.
TechnologyPlease note, the RTM version of Microsoft Dynamics 365 Business Central 2019 release wave 2 (BC15) is not supported for Document Capture 6.50. Only CU1 and newer cumulative updates are supported.

The RTM version is not supported as we are using internal events in DC6.50, and as internal events only are supported in BC15 CU1 and newer cumulative updates.
TechnologyThe Document Capture service has been updated.
TechnologyWe have split the Document Capture app into two apps. One base app (Continia Document Capture 365), which consists of most of the functionality in Document Capture. The base app is equal to the app released in Business Central Cloud.

In addition to the base app, we have created a new app named Continia Document Capture 365 on-premises, which enables you to utilize features only available in on-premises installations of Business Central. This app is necessary if you want to use File System as Document Storage Type or utilize the on-premises OCR Service, which also requires access to the file system. This app is installed per default when installing document capture as an app from the solution package. The on-premises app requires the Document Capture Server Components (Service Tier Libraries) to be installed before publishing and installing the app.
TechnologyWe are now supporting Azure Blob Storage as a third Document Storage Type option. Customers must use their own Azure Storage account.
TechnologyThe following events have been added, allowing partners to extend Document Capture to use other storage types:

Codeunit 6085640 CDC Doc. File Events
  • OnHasFile
  • OnClearFile
  • OnGetFile
  • OnSetFile
For more information about the events, please see the Document Capture Event Publishers in Zendesk: https://continia.zendesk.com/hc/en-us/articles/360011491120-Document-Capture-Event-Publishers
UI SimplificationInformational, confirmation, and error messages have been improved.
UI SimplificationCaptions have been updated and improved.
UI SimplificationOn the “Template Card”, the following has been changed:
  • Purchase tab is only shown for Purchase categories
  • “Vendor Uses Your Item Nos” is always shown on Master Templates
  • “Vendor Uses Your Item Nos” was moved to General tab from Purchase ta
UpgradeWe have removed the following folders from the product package under Upgrade, as you still need the full Document Capture installation package for the specific subversions when upgrading:
  • Upgrade from DC3.50 to DC4.50
  • Upgrade from DC4.0x to DC4.50
  • Upgrade from DC4.07 to DC4.50
  • Upgrade from DC4.50 to DC5.00
  • Upgrade from DC5.00 to DC5.50
  • Upgrade from DC5.50 to DC6.00
UpgradeWith the release of Document Capture 6.50, the upgrade toolkit has been released for the upgrade from Document Capture 6.00 including any Service Pack for DC6.00 on the NAV version used with DC6.00. The upgrade toolkit will also upgrade Expense Management if Expense Management is used.
UpgradeIf you are upgrading from an earlier version of Document Capture such as version 3.50 or 4.0x, you must upgrade Document Capture to version 4.50 first, then upgrade to Document Capture 5.00, then upgrade to Document Capture 5.50, then upgrade to Document Capture 6.00 and finally to Document Capture 6.50. The upgrade to Document Capture 4.50 can be done using one upgrade toolkit, and this upgrade toolkit can be found in the Document Capture 4.50 product package.
UpgradeWith the release of Document Capture 6.50, we have released upgrade objects that can be used with the new Data Upgrade Tools from Microsoft. If you want to use new Data Upgrade Tools from Microsoft, you must follow the steps described in “4.1b - Data Upgrade Guide from DC6.00 and or EM4.00 to DC6.50 and or EM6.50”. If you want to use the old pre and post upgrade tools, you must follow the steps described in “4.1a - Upgrade Guide from DC6.00 and or EM4.00 to DC6.50 and or EM6.50”.
UpgradeIf you are using Document Capture in Microsoft Business Central Cloud, the main upgrade will be performed automatically when you install Document Capture 6.50 (after uninstallation of Document Capture 6.00).
Users and PermissionsThe fields "Welcome Email" and "Activation Link" have been added to the "Continia User Setup" page. The fields are added, but not visible by default. The "Activation Link" field is not editable.
XML ImportWe have added the possibility to split any XML document containing multiple invoices, as this is required by the Spanish XML format. To split an XML document, you fill in the field "Split at XML Path" on the template.

Bug fixes for Document Capture 2020

Released: September 1, 2020
App version: 6.5.0.0
FOB version: 6.50

All relevant bugfixes released in service pack 1 to 4 for DC6.00, service pack 1 to 7 for DC5.50 and service pack 1 to 11 for DC5.00 are also included in DC6.50. The description of these bugfixes is not repeated in this document.


Functional areaDescription
Business CentralWhen importing a Zip file as a Stylesheet for an XML Master Template in the cloud versions of Business Central the following error occurred:
  • Exception of type 'Microsoft.Dynamics.Nav.Types.Exceptions.NAVNCLArgumentOutOfRangeException' was thrown.
Business CentralWhen using a Canada, USA, or Mexico localization of Business Central cloud, the following error occurred when trying to post a purchase invoice:
  • Imported amount is not the same as the assigned amount.
    Amount Incl. VAT does not match
    - Imported: <Imported Amount>
    - Assigned: <Assigned Amount>
Business CentralWhen using the Business Manager profile, when having documents pending your approval, and when pressing the Set Up Cues button on the standard profile activities, 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.
Cloud and On-Prem OCR ServicesWhen pressing the Import Files button to import all documents, only documents from the first document category were imported.

This only happened when using the Continia on-premises OCR service in combination with having Storage Type set to File System.
Documents and TemplatesField 11310 (a none existing field) has been deleted from the identification fields in the configuration files.
Documents and TemplatesIn some configuration files, pounds was wrongly set to GPB instead of GBP.
Documents and TemplatesWhen selecting a Header Template Field that was captured on a different page than the currently shown page, the view of the document was not updated to displaying the page where the value or caption was captured.
Documents and TemplatesUnit of Measure translations was initially only developed for the purchase category, but access to the translation records was also enabled for other categories. The Unit of Measure translations button is now only visible on documents where the related document category has vendor as the source table.
Documents and TemplatesWhen a line translation for the No. field was created with the value "*" in the "Translate From" field, the system was always using this translation. This also happened even though there was a translation from a specific item cross reference, item vendor, the "Vendor Item No." field on the item or the actual item when using the "Use Vendor/Customer Item Nos." on the template.
Documents and TemplatesWhen registering a document containing text lines (no account/item number), the following error occurred:
  • The document is not ready to be registered. Please check the comment section.
Documents and TemplatesWhen opening the Document Card from the Document Journal using drill down in "Doc. No." (not when using the shortcut Ctrl+Shift+E), it was possible to change records using Ctrl+PgUp/Ctrl+PgDown. Likewise, it was possible in the modern client to use the arrow icons on the right/left side of the page (from BC 15.01).
Documents and TemplatesThe number series template field does work when correctly set up. However, it is required that the number series configuration is related to the main number series for the document type. For example, if the document is a purchase invoice, the numbers series should appear under “relationships” for numbers series “P-INV”. It was previously possible to select any numbers series, regardless of relations. Now, when doing lookup from the field, only valid numbers series are shown. If a number series without relationships to the main number series is validated, the user will get an appropriate warning.
Document Analysis and RecognitionWhen the PDF file had a barcode, the barcode value saved in Table 6085592 CDC Document Word was missing the last character.
Document Analysis and RecognitionWhen the PDF file had multiple barcodes, the value of the second barcode also contained the value of the first barcode, the value of the third barcode also contained the value of the first two barcodes, and so on.
Document Analysis and RecognitionWhen Document Capture parses the date text, it starts with correcting capture issues, where years are captured with blanks in between the numbers (e.g., 2020 is captured as 2 020 or 20 20 or 200 2). This could result in "false" fixes. For example, "Jun 20 2017" was transformed into "Jun 202017", which would not be recognized as a date. The date text is now checked to see if a year (1991 to 2049) can be found without adjacent numbers. If a year is found, the part with year number fixes is skipped (thus avoiding "false" fixes).
Document SearchUsing the Document Search functionality in Dynamics NAV versions older than Dynamics NAV 2013 (17.10.00), the following error was occurred:
  • The XML Buffer table does not have an active key that starts with the following field or fields: Value,Document No..
Drag & DropIn the Document List form and the Document Files Factbox page, it is only allowed to delete Drag and Drop files. Now, a message informs the user that it is not allowed to delete other document types.
MatchingWhen using match with the "Match and Update Order" option, the variance amount could be miscalculated if the unit cost had more decimals than the line amount (usually 2) and if the order line was partially received.
MatchingDocument lines with no number or description translations were set as not OK even though the document was matched.
MatchingFor line matching, the setting "Purch. Match Item No." = "Yes - if present" behaved exactly as "Purch. Match Item No." = "Yes - always".

This meant that both options resulted in skipped lines when line translations could not be found even if no item number or GTIN number was found on the lines.

This bug was introduced in DC6.00 SP1.

The issue has now been fixed. When "Purch. Match Item No." = "Yes - if present" is chosen, lines will only be skipped if either item number or GTIN number is found on the line, and line translations are not found.
MatchingOn the match pages, the “Order No.” column could be updated wrongly when the user changed the sorting of the receipt and order lines (clicking on column captions).
Purchase ApprovalIf the Salesperson/Purchaser name contains illegal filter characters (=,&,<,>,@,*,(,),',",..,|) the following error was thrown when doing a lookup on the field Salesperson/Purchaser in Page 6086061 "CDC User Setup by Company":
  • The filter "@*<Salesperson/Purchaser Name>*" is not valid for the Name field on the Salesperson/Purchaser table. Did not expect '<Illegal filter character>'.
When the Page 6086061 "CDC User Setup by Company" was opened, for the users that do not have a Salesperson/Purchaser set, the field Salesperson/Purchaser showed the value of the previous user in the list.
Purchase ApprovalIt was not possible to specify "Approval client" in the Continia User Setup page in BC15 and BC16 when no Web Approval Portal was configured. This led to a wrong approval link in the status email sent to approvers.
Purchase ApprovalIn the Document Capture Setup -> Purchase Approval page, the field "Amount Validation on Post" is moved to the Document Capture Setup page to allow users to modify this field, even when Purchase Approval is not enabled.
Purchase ApprovalA confirm message displayed during auto-approve (for approval admin users) caused the database to be locked until the user took action. This could potentially cause the database to be unusable for prolonged periods. The confirm message was triggered on documents with auto-approve enabled on the template and if the invoice/credit memo was matched to orders/return orders that had status pending approval. If the user selected Yes, the document was approved. The confirm option is now removed from the code. The user still gets a message informing them that auto-approve was not done because of linked documents that are not approved. Approval, admin users, can still force approval of the document afterward.
TechnologyOpening the Document Journal could result in the following error:
  • Duplicate control IDs caused the error on page 6085600.
TechnologyIn the 6.00.00 to 7.10.00 (NAV 2009 to NAV 2013 R2) versions of the RTC clients, you would get the following message when opening the Document Card:
  • The identifier NoOfColumns could not be found
TranslationsOn the page for adjusting decimals in a template field, we have updated a caption in ES localization.
TranslationsSeveral captions for SE localization related to Purchase Allocations are updated ("Ankomstregistrering" instead of "Förregistrering").
TranslationsCorrected Spanish warning text the Document Journal and Card pages.
UI SimplificationIn the Classic Clients, the header fields subform was not showing the lookup and assist edit buttons for the Value and the OK columns.
UI SimplificationFor RTC versions of Dynamics NAV that do not support dynamic visibility of fields, the field "First Table Line Has Captions" was not visible on Page 6085584 CDC Template Card, even though Recognise Fields was enabled.
Users and PermissionsWhen accessing the "Continia User Setup" page for Document Capture approvals and when Expense Management was not in the license, the following error was shown:
  • You do not have permissions on the CEM Expense Management Setup Table:Execute
XML ImportThe XML path for the field VAT Registration No. in the EHF-ID, OIOUBL-ID, PEPPOL3-ID, UBL-ID, and XRECHNUNG-ID identification templates contained only the path "/AccountingSupplierParty/Party/PartyLegalEntity/CompanyID" which is the path to the non mandatory value according to the XML format standards. The XML path is now changed to "/AccountingSupplierParty/Party/PartyTaxScheme/CompanyID | /AccountingSupplierParty/Party/PartyLegalEntity/CompanyID".

This way, the system will try to find a VAT Registration No. from the nonmandatory path"../PartyTaxScheme/CompanyID" first, and if not found, it will take the value from the mandatory "../PartyLegalEntity/CompanyID"."
XML ImportSome of the template fields of the OIOXML master template had the same sort order value.