Detailed Changelog for Continia Document Capture 2020 R2
This article lists all new features and bug fixes for each version of Continia Document Capture 2020 R2.
Important
This version of Document Capture is no longer supported. As a consequence of this, Continia will no longer correct any errors appearing in this version, and no further service packs relating to the version will be released. For supported versions of Document Capture, see Software Lifecycle Policy and Continia Document Capture On-Premises.
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 2020 R2 Service Pack 7
Released: September 26, 2022
App version: 6.5.7
FOB version: 6.50.07
New or changed functionality
Functional area | Description | ID |
---|---|---|
Documents and Templates | Added support for line translation for the sales category using the GTIN field on the Item. | 24082 |
Documents and Templates | The data caption on the Template Field Card has been changed to show the field name only. For example, Amount Excl. VAT. Previously the following was shown at the top of the Template Field Card page: Template number, Type, Code, and Field name. | 39185 |
General Application | When translating No. and Description, the system has been changed to prioritize exact values over values containing the asterisk (*) symbol. With the following configuration for the No. field,
Support has also been added for enclosing search terms in single quotes (') when the value includes characters that are reserved for use in Business Central filter-notation (i.e. the characters ( ) | < > = .. ? &). It is, however, not possible to wrap the asterisk (*) and the Ignore case-sensitivity operator (@). The priority order is:
| 32564 |
Order & Receipt Matching | The Special Sales Order No. field is now available on the Purch. Invoice Match Subpage. | 39228 |
Platform and Technology | Several events have been added to the solution. For details, please see https://continia.zendesk.com/hc/en-us/articles/360016212240-Document-Capture-6-50-Event-Publishers | 26956 |
Bug fixes
Functional area | Description | Id |
---|---|---|
Documents and Templates | When batch registering documents from the GLDOC category, none of the documents were registered. | 27400 |
Documents and Templates | In the Portuguese configuration file, rules and captions changed to the following for the DOCTYPE field on master templates:
| 38421 |
Documents and Templates | When importing the first document from the Document Categories lookup from the Document Journal page, all the actions were disabled until the Document Journal page was reopened. | 38493 |
Documents and Templates | The Order/Return Order field always showed false on the Assigned Documents page. | 38682 |
Documents and Templates | When using a field translation with stars (*) at both the beginning and the end of the translation, the word was not translated correctly. | 38978 |
Documents and Templates | The Delete after Download field was wrongly hidden after selecting an EWS protocol on Document Category Card. | 39102 |
Documents and Templates | In Classic Client, when selecting more than 100 pages to split, the following error could occur:
| 39200 |
Documents and Templates | The copy template action was disabled on identification templates. Now it is enabled. | 39325 |
Documents and Templates | For the German localization, no stylesheet was shown when opening an XRechnung CII document. | 40286 |
Documents and Templates | For the German localization, the XRechnung CII XML master template did not recognize the document type correctly. | 40297 |
Documents and Templates | When using "Use Vendor/Customer Item Nos." on sales documents, the system continued to look for translations even when the item translation was found, | 40870 |
General Application | The value in the following fields has been masked:
| 38741 |
General Application | When exporting configurations through the Document Capture Assisted Setup Guide, decimal values were converted to integers (e.g., 22,5 was converted to 225). | 38812 |
Order & Receipt Matching | When Invoice Reg. Step 1 was set to Match & Update Order or Credit Memo Reg. Step 1 was set to Match & Update Return Order, it was possible to register the document without any warning message. Now, the following warning message is shown, when registering an invoice without matching:
| 39334 |
Platform and Technology | When the template field code was more than 15 characters long, the following error occurred during field recognition:
| 39544 |
Document Capture 2020 R2 Service Pack 6
Released: June 28, 2022
App version: 6.5.6
FOB version: 6.50.06
New or changed functionality
Functional area | Description | ID |
---|---|---|
Documents and Templates | All fields and actions were the same for master and identification templates. Now for only identification templates, the field Data Type and the Fields section are visible and actions are disabled. | 14803 |
Documents and Templates | For localization DK, three new template fields added to PEPPOL3 template to support FIK.
| 32731 |
Document Approval | We have added the Document Card and Match Lines actions to the Assigned To Me page. | 28013 |
General Application | The sorting of the comments on the Document Card was not the same as the sorting on the Document List: This has been changed, so the comments on the Document Card are now sorted the same way as on the Document List. | 14670 |
General Application | The OCR configuration file is now exported when changing relevant fields and using on-prem OCR, including modifying the Process PDF files with XML files field. Previously the OCR configuration file was only automatically exported when using cloud OCR. | 28627 |
General Application | When changing the Company Code, the following message was previously shown:
| 31997 |
Platform and Technology | The Continia Web Approval Portal has been updated to version 1.24.1 | 32639 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | When registering a document while applying Amount Distribution code on negative amounts, the following error occurred:
| 21762 |
Documents and Templates | The Delete button on the Split and Merge Documents page was enabled, even though the "Allow Deleting Documents" option was not activated on the Document Category page. | 27408 |
Documents and Templates | When selecting more than 100 pages to split, the following error still occurred:
| 30090 |
Documents and Templates | The setting "Change Sign" on template fields did not change the sign as expected in some situations. | 30347 |
Documents and Templates | The 'Stop Recognition' field is now hidden when the template type is Line or when Allow Line Recognition is not activated. | 30823 |
Documents and Templates | The KID field is now copied to the created purchase header during document registration. | 31841 |
Documents and Templates | Calculations did not work when a template field code contained a space or certain special characters. Therefore, it is now being prevented that template field codes include a space or the following special characters: (/*-+()|<>%^&=.?$#@'"). | 31969 |
Documents and Templates | While registering a sales document and if there was a difference between the imported and assigned amounts, the created sales document was not rolled back and the DC Document status stayed open. | 32064 |
Documents and Templates | A line translation was not found when the Vendor Item No. on the item was not uppercase. | 32721 |
Documents and Templates | When using an amount rounding precision different from the invoice rounding precision defined in General Ledger Setup and recognizing lines, the following error occurred in some situations:
| 34575 |
Documents and Templates | When registering a document and Transfer Value to Header Table or Transfer Value to Line Table was blank, the following error occurred in some situations:
Now, the field ID is shown when Transfer Value to Header Table or Transfer Value to Line Table contains a field number that does not exist. | 34615 |
Document Approval | A wrong advanced approval group could be used if the purchase header filters contained the range operator "..". | 30591 |
General Application | When deleting a Continia User Setup record, the related record from the standard User Setup table was also deleted if the standard Business Central fields not shown on the Continia User Setup page were empty. The record from the standard User Setup table is now only deleted if fields added by extensions also are empty. | 28070 |
General Application | When activating both "Use Cloud OCR" and "Export OCR Configuration Files", it was not possible to deactivate "Export OCR Configuration Files" until "Use Cloud OCR" was deactivated. | 30449 |
General Application | When accessing the template field card, the fields Type and Code are now only visible when creating a new template. | 32265 |
Purchase Documents | Document Capture fields were shown on page 51 even when Document Capture was not activated. | 32441 |
Document Capture 2020 R2 Service Pack 5
Released: March 10, 2022
App version: 6.5.5
FOB version: 6.50.05
New or changed functionality
Functional area | Description | ID |
---|---|---|
Documents and Templates | On page 6085600 - CDC Document List With Image, the following actions are now hidden if no XML documents exist or when using Document Capture without access to the XML import module.
| 27110 |
General Application | A new page showing files related to payments has been developed. The page can be added to the Payment Journal and will show the related posted purchase invoices.
The new page is Page 6085663 - CDC Purchase Journal File FB.
When adding the page as a factbox, the following filters must be set.
| 28130 |
General Application | To optimize the performance when running Business Central, we are now caching if a user is a Team Member. | 29227 |
General Application | We have optimized the performance in CDC Log Mgt. when determining if records should be checked for modifications. | 29229 |
General Application | When registering a sales order, the following error occurred in some situations:
| 29768 |
Platform and Technology | Several events have been added to the solution. For details, please see https://continia.zendesk.com/hc/en-us/articles/360016212240-Document-Capture-6-50-Event-Publishers | 26956 |
Platform and Technology | The following Event Publisher in Codeunit 6085576 CDC Capture Management is obsolete as the Word parameter is not a VAR parameter:
| 29420 |
Platform and Technology | The Continia Web Approval Portal has been updated to version 1.23.0. | 31352 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | The flowing fields are now excluded when exporting configuration files using the Document Capture Setup Wizard. Document Capture Setup:
| 28764 |
Country and Regional | An error comment is created when the same external document number is used more than once. However, in the Spanish localization, Business Central can be configured to allow the same external document number to be used several times by populating the "Same Ext. Doc. No. in Diff. FY." field in Purchases & Payables Setup. This is now supported in the Spanish localization. | 30669 |
Documents and Templates | When recognizing fields on a document with Intercompany fields and Amount Distribution, the following error occurred.
| 17870 |
Documents and Templates | When importing documents in a system without access to the Document Capture XML module, all XML files were skipped. Now, the following message is shown when importing a specific XML document in a system without access to the Document Capture XML module.
| 22487 |
Documents and Templates | The "CDC Document List" page now includes XML file type documents. | 29080 |
Documents and Templates | Captions for Salespersons, Sales People and Purchaser(s) have been updated. | 29345 |
Documents and Templates | On a template with "Prices Incl. VAT" set to yes, populating "Validate VAT Calculation" did not work as intended. | 29586 |
Documents and Templates | Added the following template field to FR, NL, BE-UK, BE-FR, BE-BE purchase master templates. Header Field:
| 29769 |
Documents and Templates | It is now only possible to have one default vendor template. Setting a vendor template to default will remove the default setting from other vendor templates. | 29961 |
Documents and Templates | Fixed an issue where it was not possible to recognise any fields on a document after performing split and merge. | 30352 |
Documents and Templates | Multiple look-up's in rules could lead to unintentional modification of the rules on the master template. | 30934 |
Documents and Templates | The validation of the FIK number was not correct. For example, when the FIK number started with 71, 73, or 75, the system wrongly only accepted vendor numbers beginning with 7, 8 or 9. | 31615 |
Document Approval | Nothing happened when trying to open a credit memo from the "Document Archive" page 6085798 - CDC Approver Role Center. | 28748 |
Document Approval | In some situations, the company name was not encoded correctly in the link to the Business Central client when sending out approval e-mails. | 30240 |
Document Approval | When a user with NAV Login Type "No NAV Login" or Database tried to log in on the Continia Web Approval Portal, the following error occurred if the user had been exported without WebService Key:
| 30509 |
Document Approval | We have fixed an issue where the number of documents was not correct in the Approval Portal. | 31573 |
General Application | When importing a configuration file, include Document Capture Setup, into a company containing documents and where Document Capture already have been set up, the following error message is now displayed:
The error is displayed if one of the following fields is changed during the import:
| 28662 |
General Application | When using Unidentified Company (UIC), the incoming emails were not copied to the destination company. | 29108 |
General Application | When moving a document to another category and using "File System" as "Storage Type", the PDF and TIFF files were moved, but the PNG file was not transferred together with the other files. Instead, the PNG file wrongly stayed in the old category folder. | 29489 |
Order & Receipt Matching | When matching against a receipt or return shipments line for a G/L Account or Charge Item, the following error occurred in NAV3.70 to BC14:
| 28944 |
Order & Receipt Matching | When capturing lines and matching against order numbers with the matching option "Always", no filter would be applied on the order number if the captured order no was blank. | 30695 |
Platform and Technology | When activating the Microsoft EWS download of mails to the OCR service, the following error occurred:
| 28857 |
Platform and Technology | When importing a configuration file containing a vendor name of more than 50 characters, the following error occurred.
| 29331 |
Purchase Documents | The following error:
For example, when the header total was 100,00, and the sum of all line amounts was 100,001 on a document, the following error comment was shown:
| 26219 |
Purchase Documents | To avoid unnecessary write transactions for Team Members, we now check if purchase lines exist before attempting to delete these in the PurchLineOnDelete function in codeunit 6085709 - CDC Purch. Doc. - Management. | 29370 |
Purchase Documents | When using batch post on page 6085933 - CDC Pg Purch. Cr. Memos Subs, the following error occurred:
| 29893 |
Document Capture 2020 R2 Service Pack 4
Released: October 14, 2021
App version: 6.5.4
FOB version: 6.50.04
New or changed functionality
Functional area | Description | ID |
---|---|---|
Country and Regional | The ENC, ESM, FRC, FRA, and ESP languages have been added to the NA localization. Note, when running the application in:
| 25015 |
Documents and Templates | The identification of the XML format was not working properly when the XML header tag contained XML attributes. | 25733 |
Documents and Templates | On page 6085581 "CDC Document Comment Sheet", the automatic population of the "Date" field has been aligned with standard Business Central. The field "Code" is now hidden by default. | 28313 |
Platform and Technology | Several events have been added to the solution. For details, please see https://continia.zendesk.com/hc/en-us/articles/360016212240-Document-Capture-6-50-Event-Publishers | 26956 |
Platform and Technology | When getting the error message about missing server components, the message has been changed. The following has been added to the error message: "Remember to restart the service tier after installing the components."
| 27887 |
Platform and Technology | The Continia Web Approval Portal has been updated to version 1.20.0 | 28294 |
Platform and Technology | Procedure BreakDownPaymentId in Codeunit 6085738 "CDC Is Valid Payment-Id (DK)" is now external. | 28578 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | In the CH localization, table 6086201 "CDC Vendor Identifiers" was missing. | 26324 |
Country and Regional | In the Document Journal, a spelling mistake has been corrected for the German caption of the Purch. Match Credit Memo option field. | 26416 |
Country and Regional | On the Template Field Card, a spelling mistake has been corrected for the Dutch caption for the Stop Lines Recognition option field. | 26603 |
Country and Regional | The following BE & FR translations have been changed in the Document Journal.
| 26818 |
Country and Regional | In the Document Journal, a spelling mistake has been corrected for the German caption of the Delegate to User field. | 26882 |
Country and Regional | The following missing German caption has been translated on the "How-to submit documents" page (page 6085788 CDC Document Category Wizard). Changed from:
| 27853 |
Documents and Templates | When using the Document Capture service 6.04 or a newer version, when using the classic client, and when importing a document containing a QR code, the following error occurred:
| 20641 |
Documents and Templates | Field translations containing an asterisk (*) now correctly upholds the case sensitivity setting. Before, they were always case sensitive, even when "Case-sensitive" was unchecked. | 21242 |
Documents and Templates | In the Document Category Wizard (How-To Submit Documents), the text regarding where to find the email addresses has been updated, as some users found it confusing. | 22206 |
Documents and Templates | When Make Absolute Number was populated on a Template Field, the result calculated based on the formula on the field was not converted to an absolute number. | 23148 |
Documents and Templates | When recognizing fields on an XML document that could not be identified, the following error occurred:
| 23302 |
Documents and Templates | In BC14 the Approvals on action on page 6085706 "CDC Purch. Invoice With Image" opened the wrong page. | 24112 |
Documents and Templates | Line translation for the sales category now works similarly to the purchase category. It is now possible to translate from the Description field, and it is now possible to use wildcards(*) on the No. and Description field. | 24114 |
Documents and Templates | The filter actions "Unmatched Only" & "Match Differences" have been copied from the Invoice matching page to the Credit Memo Matching page. The actions have also been created on the corresponding forms for the classic client. | 24875 |
Documents and Templates | The description field is now visible on the Template card for the XML identification templates. | 25192 |
Documents and Templates | Adding a template field with the same value in "Sort Order" as an existing template field prevented the "Move up / Move down" functions from working as intended. | 25469 |
Documents and Templates | When a template is configured to "Use Vendor/Customer Item Nos." and the captured Item No. is longer than 20 characters, you got the error:
| 25687 |
Documents and Templates | For XML documents that have discount or charges names containing filter characters, the following error occurred when pressing the "Add Template Field" button:
| 26166 |
Documents and Templates | We have updated the German translation of the comment autogenerated in the Document Journal when changing the document status. | 26663 |
Documents and Templates | After using the "New" option on the Document File FactBox on sales documents, any subsequent drag and drop would result in the following error message:
| 26935 |
Documents and Templates | When importing an XML document for a category with "Register Documents Automatic." = true, the following error occurred:
| 27276 |
Documents and Templates | XML documents with embedded documents will no longer recreate (duplicate) the embedded documents when reopening a document and recognizing fields. | 27416 |
Documents and Templates | When creating a new template (activating Recognize Fields) and accepting that the template is copied from another company, a field with a fixed value and Data Type = Lookup could be wrong on the copied template. | 27437 |
Documents and Templates | When recognizing fields and capturing a long string into a date field, the following error occurred in some situations:
| 27445 |
Documents and Templates | In the Sales Document Category, we have changed the field caption on the following document header fields: Previous captions:
| 27926 |
Documents and Templates | For the Document Category GLDOC, we have changed the caption for Document No. in all languages. Changed from:
| 28285 |
Documents and Templates | When recognizing fields in the App version of DC, the system partially matched the rules against the value. This meant that longer values were marked as valid. Example: The rule "[0-9]{3}" used to mark the value of '123456789' as valid. | 28356 |
Document Approval | A wrong error message was shown when a user without approval admin permissions tried to change the approver on an approval entry. | 22431 |
Document Approval | In NAV/BC versions up to and including Business Central 2019 release wave 2 (BC15), it was possible to delete an approval entry if the following 2 conditions were met:
We have circumvented this by adding the delete permission to the page property. | 22432 |
Document Approval | In a scenario with:
When User B forwarded the purchase document without approval to User C, the system created an approval entry for User D (4-eyes approver of User C). That is unnecessary since User A already approved the document. The approval by User A and User C is sufficient to meet the 4-eyes approval criteria. | 24275 |
Document Approval | Refactored the functionality that executes when approving an approval entry, so amounts are only calculated when needed, thus increasing approval performance. Added the event OnBeforeAutoArchive to allow suspension of the "Auto Archive" functionality of purchase documents executed when approved. | 25653 |
Document Approval | When exporting users and a user existed with Login Type = No BC User and Client Type = Continia Web Approval, the following error occurred:
| 26767 |
Document Approval | When a user with NAV Login Type "No NAV Login" or Database tried to log in on the Continia Web Approval Portal, the following error occurred if the user had been exported without WebService Key:
| 26883 |
General Application | The field "Unidentified Company File Path" in Document Capture Setup is now only editable if "Use Unidentified Company Documents" is activated. | 22124 |
General Application | When pressing New in the Drag & Drop file box, it's now possible to select a category code. In addition, the category code will default to the Drag & Drop category if it exists. Previously, the category code was blank. | 24132 |
General Application | It is now possible to approve purchase documents when using Microsoft Power Automate (Microsoft Flow). | 24596 |
General Application | All Document Capture tables are now added to the "CDC-SUPER" permission set. You must run codeunits to get the added 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 | 24956 |
General Application | When selecting a scanner in Business Central, the following error occurred if the scanner name was longer than 20 characters:
| 25504 |
General Application | Storage migration only moved one UIC document per execution. Therefore, migration had to be restarted for each document. | 25831 |
General Application | The following error occurred when rotating documents, when running the classic client, and using the file system as the storage type.
| 26099 |
General Application | The following error occurred when using the NAV 2009 R2 RTC client and when opening the pages listed below.
| 26194 |
General Application | When exporting two or more users with the same email address, the following error occurred:
| 26573 |
Order & Receipt Matching | The "Auto Delegate" function is now executed when using the "Perform Match" action on the Matching page. | 21846 |
Order & Receipt Matching | In DC6.50, we changed the code in the function (IsFirstDocLineused) used for showing and hiding the Order No field in the "CDC Purch. Match Subpage" page part and Return Order No. in "CDC Purch. Ret. Shpt. Match Sp". The change was made because the old code was not working correctly when the sorting order was changed on the pages. The new code behaved better when changing sorting but unfortunately caused the pages to update much slower in some databases with many records in the Purchase Line or Return Shipment Line tables. In order to fix this issue, we have changed the code back to the old version, with the addition that if the sorting is changed away from the default sorting, the Order No./Return Order No. is shown on every line. This fix was applied to the "CDC Purch. Invoice Match Subp." page in 6.50 SP3, but we forgot to fix these additional pages at that time. | 25594 |
Order & Receipt Matching | From NAV 3.70 to NAV 2017, the following occurred. When using the register option "Match and Update Order", and having an order line with quantity = 0, the following error occurred in register process:
| 26021 |
Order & Receipt Matching | Auto-match did not work for vendors with "Pay-to Vendor No." populated. | 26723 |
Order & Receipt Matching | Fixed an issue with a partial match on purchase receipt/return shipment lines resulting in wrong value entries and closing of the item ledger entry. In the following CU's, Microsoft changed the code in the "Get Receipt Lines" and "Get Return Shipment Lines" functions, which trigger the error:
| 26992 |
Order & Receipt Matching | When we released DC6.50 SP3 and DC8.00, we failed to include the updated version of codeunit 6086027 "CDC Unit of Measure Mgt." for Business Central 2020 release wave 1 and newer versions (BC16 and newer versions). This resulted in the "old" functions (CalcBaseQty and CalcQtyFromBase) in codeunit 5403 being called from codeunit 6086027 "CDC Unit of Measure Mgt.". Since the old functions only take two parameters, the raised events (OnAfterCalcBaseQtyPerUnitOfMeasure and OnAfterCalcQtyFromBasePerUnitOfMeasure) ended up with blank values in the three missing parameters (ItemNo, VariantCode, and UOMCode). | 27625 |
Order & Receipt Matching | When matching an item on a purchase receipt or return shipment line with lot tracking and unit of measure calculations, the following error could occur:
| 27676 |
Platform and Technology | When moving documents to other companies and using Azure Blob Storage in some of the companies, the related files were lost. When migrating to another storage type, the files used for showing the document were lost for UIC documents. | 25866 |
Platform and Technology | Embedded files in an XML Document in the OIOXML format were not getting the .tiff extensions.Improved the recognition of the embedded file extension in an XML document. | 25991 |
Purchase Documents | The Attachments action on page 6085706 "CDC Purch. Invoice With Image" in Business Central Spring 2019 (BC14) now opens the Document list instead of the Document card. | 22683 |
Purchase Documents | Added missing "Attachments" actions in BC13 page 6085706 "CDC Purch. Invoice With Image". The action was missing in the following localized versions of the page: AU, BE, CH, ES, GB, NA, NL, NO, NZ, SE. | 26706 |
Purchase Documents | The "Amount Excl. VAT (Imported)" and "Amount Incl. VAT (Imported)" fields have been added to "CDC Purchase Credit Memo With Image" page for Business Central 2019 Spring (BC14) and newer versions. | 26751 |
Document Capture 2020 R2 Service Pack 3
Released: May 18, 2021
App version: 6.5.3
FOB version: 6.50.03
New or changed functionality
Functional area | Description |
---|---|
Business Central | Document Capture now supports the new "Item Reference" table introduced as a feature in BC17 |
Business Central | Document Capture now supports the "Feature Update: Conversion templates to convert contacts to vendors and employees" feature introduced in Microsoft Dynamics 365 Business Central 2020 release wave 2 (BC17) when creating new vendors or customers from the Document Capture Journal. |
Cloud and On-Prem OCR Services | Altered EWS setup for document categories enabling you to configure one authentication email for all email accounts checked by the Document Capture service. |
Cloud and On-Prem OCR Services | Fixed an issue where the Document Capture service failed when running EWS and checking an email with no attachments. |
Continia Web Approval Portal | The Continia Web Approval Portal has been updated to version 1.18.0 |
Events | The following events are added to the solution: Codeunit 6085706 CDC Purch. – Register
|
Technology | It is now possible for limited users and team members to write to specific Document Capture tables without this counting towards the maximum of three permitted tables. This means that limited users and team members can use Drag and Drop, Advanced Approval, and create comments in Document Capture and still write to three additional tables. The following tables do not count towards the maximum of three permitted for Limited Users when using the Microsoft Dynamics NAV Perpetual product line and for Team Members in Dynamics 365 Business Central on-premises.
|
Bug fixes
Functional area | Description |
---|---|
Business Central | Action "Upgrade Data to Latest Version" has been removed in App versions of Document Capture because the upgrade is handled automatically. |
Cloud and On-Prem OCR Services | The wording of the match message created for a document with lines recognized and matched within document-wide (total amount) variance has been changed. Message before:
|
Document Analysis and Recognition | When capturing lines, the system calculated Line Amount wrongly (Line Discount % was ignored) for lines with Line Discount % = 100, and Total Cost = 0. |
Document Analysis and Recognition | Having auto-generation of rules enabled on a template field and recognizing a value exceeding 250 characters could cause an error message similar to:
|
Documents and Templates | When capturing a barcode in NAV 2013 and NAV 2013 R2, the following error occurred:
|
Documents and Templates | When we released DC6.50.02, we forgot to write the following in the changelog: The 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, sometimes 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 multiple vendors. |
Documents and Templates | Fixed an issue where split and merge did not work when using Azure Blob storage. When merging, you got an error that the PDF file did not exist. Note, this was only an issue when using the on-premises app. |
Documents and Templates | The lookup from the "No. Series" template field on documents with category PURCHASE and type C (Credit Memo) has been corrected. The lookup displayed No. Series for Purchase Orders. Now it shows the correct No. Series for Credit Memos. |
Documents and Templates | When using the rotate functionality, the document was not rotated when running as App and using File System as the storage type. |
Documents and Templates | When performing drill-down in Files for OCR/Import/Error in the Category List, the import action has been disabled (greyed out) for files with the status Pending OCR or Error. |
Documents and Templates | Corrected tooltip for Document Status Text on Page "CDC Document List With Image" |
Drag & Drop | When using Drag & Drop for an email from Outlook into Business Central, the email got deleted in Outlook |
Drag & Drop | When using Drag and Drop, while having the XML Import XMLATTACH Document Category imported, the user had to choose between the DRAGNDROP and the XMLATTACH category. |
Installation and Setup | We have improved the performance when importing configuration files containing many templates. |
Matching | When trying to match order lines that had order tracking or reservation entries, the following error occurred:
|
Matching | When matching against purchase order lines or purchase receipt lines related to a production order, the following error occurred if the item on the line had tracking requirements:
|
Matching | To clarify which Approval Sharing page you search for, the text EM or DC has been added to the page caption. |
Matching | When using line recognition and having multiple order numbers in the template field "Our Order No.", auto-match did not work if "Match on Order No." was enabled. |
Matching | In DC6.50, we changed the code in the function (IsFirstDocLineused) used for showing and hiding the Order No field in the "CDC Purch. Invoice Match Subp." page part. The change was made because the old code was not working correctly when the sorting order was changed on the page. The new code behaved better when changing sorting but unfortunately caused the page to update much slower in some databases with many records in the purchase receipt line table. In order to fix this issue, we have changed the code back to the old version, with the addition that if the sorting is changed away from the default sorting, the Order No. is shown on every line. |
Matching | On documents with lines recognized: When enabling "Match Unit Cost" under "Line Matching" on the template card, the matching parameters, "Unit Cost - Variance Amt (LCY)" and "Unit Cost - Variance %", would not become visible until the template card was closed and reopened. The visibility of the two fields is now updated immediately when changing the value of "Match Unit Cost". |
Matching | When matching against a purchase receipt line with tracking, where base quantity had more than 5 decimals, the tracking was not always copied from the receipt line. Furthermore, when trying to apply the tracking, the following confirmation message would pop up:
|
Purchase Approval | When Advanced Approval was enabled, and when at the same time applying an Approval Flow code, a mixture of the two approval methods was used. It was never intended to support the combination of Advanced Approval and Approval Flow simultaneously, We have now disabled the use of Approval Flows and hidden the Approval Flow Code field on the invoice and credit memo pages when Advanced Approval is enabled. |
Purchase Approval | The Amount in approval entries could be wrongly calculated (doubled) if another add-on manipulated the VAT amount lines on the document. |
Purchase Approval | On page 6085740 "CDC Purch. App. Entries Subp.", the lookup has been removed from the Description field, and the Quantity and Direct Unit Cost fields are now visible by default. |
Purchase Approval | Added lookup functionality and validation code for the Shortcut Dimension 3 to 8 in page 6085740 "CDC Purch. App. Entries Subp.". |
Purchase Approval | When trying to approve entries in the approval portal, the following error could occur:
|
Purchase Approval | In some situations, the number of pending approvals was wrong. This occurred as shared approval was calculated wrong when more than one user had shared their approval. |
Purchase Approval | Fixed an issue where users could get errors regarding companies they did not have access to when setting up Out Of Office. |
Purchase Documents | On page 6085730 "CDC Purch. Allocation", the "Create Lines" and "Reverse Allocation" actions are now disabled when they can't be used. Previously, the following error was shown when using the functions:
|
Purchase Documents | When opening the Document Capture Purchase Invoice list or Purchase Credit Memo list, the following error could occur:
|
Purchase Documents | When using the "Navigate" function on an entry with a DC document attached, the following error could occur:
|
Purchase Documents | When subscribing to the event OnAfterFindVendorBeforeModify in Codeunit 6085702 "CDC Purch. Doc. - Identificat.", the following error could occur:
|
Technology | In Dynamics NAV versions 6.00 and 6.10 (2009 and 2009 R2), the Company GUID field was not shown correctly on the "CDC Web User Company (WS)" page. Because of this, the approvers were not able to log in to all the companies they had access to. |
Technology | We have added more Document Capture menu items to the page opened when using "Try Exploring" from "Tell me..." (search) in Business Central. |
Technology | The migration between document storage types has been made more robust, and it is now possible to use the system while files are being moved from one storage type to another storage type. When changing storage type, you are now asked if you want to start the migration immediately or start it via the job queue (you must have a running job queue for the second option to work). Previously, when an error occurred during the migration, the process stopped and rolled back the changes. The migration process will now resume from where it stopped when it is restarted after an error occurred. When migrating many documents to Azure blob, the process may still be interrupted because the Azure Storage REST API sometimes refuses the connection. In this case, you must resume the process from the "Storage Migration Status" page or the job queue. The "Storage Migration Status" page now shows migration status by companies and how many documents are waiting to be moved. |
Translations | When viewing the attached files on a Credit Memo, the Drag and Drop page title was Invoice instead of Credit Memo. |
Translations | Multiple German translations on the master template and in the matching area have been corrected. |
Translations | The German captions in Text024 in CU 6085709 now refer to %1 as all the others, and not %2. |
Translations | The French caption "Exportation fichiers de OCR configuration" has been changed to "Exportation de fichiers de configuration OCR". |
Translations | Captions on the "CDC Update Storage Settings" page was wrong in languages different from Danish, English, and Norwegian. |
Translations | On the Document Category Card, the caption of the EWS group was wrongly shown as IMAP in multiple languages. |
Users and Permissions | The following error message was displayed when using Approval Flow codes and when the user only had access to one company.
|
Users and Permissions | When a user tried to recognize fields, and when the related vendor did not have a template, and when the users' permission was limited to the current company only, the following error occurred:
|
Web Approval | When trying to save the settings in the Continia Web Approval Portal and when a Share-To User was filled out, the system displayed the following error message:
|
Web Approval | When exporting users to the Continia Web Approval Portal and one of the companies was not activated, the following error occurred:
|
XML Import | When using Dynamics NAV 2015 or an older version, the path for attributes (Type=Attribute) shown in the XML Viewer was wrong. This meant that when you used the XML viewer to return a value, the wrong attribute value was returned. |
XML Import | When importing an XML file using the classic clients where the NATHash.dll standard component is not installed or properly registered, the client crashed. The event viewer showed an Application error specifying the NATHash.dll component. |
Document Capture 2020 R2 Service Pack 2
Released: December 22, 2020
App version: 6.5.2
FOB version: 6.50.02
New or changed functionality
Functional area | Description |
---|---|
Events | The following events are added to the solution:
|
Matching | The match warning "No Match" has been made configurable. The message type can be changed to Information, Warning, or Error. |
Matching | The warning "Payment Terms (<Payment Term Code>) is not correct." is now configurable as information. |
Matching | The 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 |
Technical | With DC6.50 service pack 2, we have released objects for Microsoft Dynamics 365 Business Central Spring 2019 (BC14) on-premises update CU19. |
Bug fixes
Functional area | Description |
---|---|
Business Central | The 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-ins | We have corrected an issue where the Scanning and OCR page would lock and not import any files when scanning documents. |
Continia Web Approval Portal | The Continia Web Approval Portal has been updated to version 1.16.0 |
Cloud and On-Prem OCR Services | After 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 Services | Fixed 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 Services | When importing documents from NAV 2009 SP1 or NAV 2009 R2 using the RTC-client, users received the following error:
|
Cloud and On-Prem OCR Services | We have optimized the import code when using Continia Online to prevent the same email file from being downloaded multiple times. |
Documentation | When 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 Templates | During 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 Templates | When 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:
|
Documents and Templates | We 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 Templates | Recognize field on template could result in the following error:
|
Documents and Templates | If 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 Templates | When using the Tab key to switch between fields in the Document Header Fields subpage, the switch was not behaving as expected. |
Installation and Setup | The tile "Delegated to me" on the DC Role Center (Activities part) is now always shown. |
Installation and Setup | Added 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 Setup | For 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 Setup | For Business Central online, we have added the Azure Blob Storage option to the Storage Option field in the Document Capture Setup Wizard. |
Installation and Setup | The obsolete copyright text has been removed from the "About Document Capture" page. |
Matching | In the Document Journal, when filtering the documents on Match Status = Unmatched, the following error could occur upon matching lines:
|
Matching | When 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. |
Matching | When 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:
|
Matching | When 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. |
Matching | If 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:
|
Matching | We 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. |
Matching | When matching receipt lines, the following error could occur:
|
Matching | When matching, the following error could occur:
|
Purchase approval | In 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:
|
Purchase approval | For 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 approval | In 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 approval | The Reason Code description has been extended to 100 characters to support BC14 and newer versions. |
Purchase Documents | When opening the Document Capture Purchase Invoice list or Purchase Credit Memo list, the following error could occur:
|
Purchase Documents | When using DrillDown on the field Attached Documents in the Purch. Cr. Memo page, the DC Document was shown, and not the Attachment list. |
Technical | Codeunit 6085791 "CDC Create eDocuments Category" has been removed in the Danish packages as it is now obsolete. |
Technical | License information was not shown on the "About Document Capture" page. |
Technical | The 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. |
Translations | The SE caption for the "Continia Userlist" page has been changed from "Användarlista" to "Continia Användarlista" to reflect its use better. |
Translations | Captions in wizards have been aligned with standard BC guidelines. |
UI Simplification | The "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 Simplification | The mail settings on the Document Category Card were not shown in NAV 2013. |
UI Simplification | The "Web Approval" captions in Document Capture pages have been renamed to "Continia Web Approval". |
Users and Permissions | Added full permissions to table 2000000076 "Web Services" for the "CDCSUPER" permission set. |
Users and Permissions | To increase the general performance, we now cache the result when determining if a user is using a Team Member license. |
Web Approval | If 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 Import | When using Norwegian regional settings, the XML fields that have the SUM() operator was not returning any value. |
XML Import | When 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. |
Document Capture 2020 R2 Service Pack 1, hotfix 2
Released: December 7, 2020
App version: 6.5.1.2
Only released in Business Central online.
Bug fixes
Functional area | Description |
---|---|
Documents and Templates | Recognize field on template could result in the following error:
|
Documents and Templates | The 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 Documents | When opening the Document Capture Purchase Invoice list or Purchase Credit Memo list, the following error could occur:
|
Document Capture 2020 R2 Service Pack 1
Released: October 1, 2020
App version: 6.5.1
FOB version: 6.50.01
New or changed functionality
Functional area | Description |
---|---|
Business Central | Microsoft Dynamics 365 Business Central 2020 release wave 2 (BC17) includes the following feature:
|
Events | The following events are added to the solution:
|
Matching | We have added the following new event in Codeunit 6085709 "CDC Purch. Doc. - Management" (also mentioned in the list above):
|
Technical | With DC6.50 service pack 1, we have released Document Capture for Microsoft Dynamics 365 Business Central 2020 release wave 2 (BC17). |
Technical | With DC6.50 service pack 1, we have released objects for Microsoft Dynamics 365 Business Central Spring 2019 Update (BC14) on-premises CU16. |
Bug fixes
Functional area | Description |
---|---|
Business Central | In 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."
Force Approval: Ctrl+F App (6.5):
Force Approval: Ctrl+Shift+F |
Business Central | When 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-ins | In 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 Portal | The Continia Web Approval Portal has been updated to version 1.15.4. |
Document Analysis and Recognition | We have corrected a bug that prevented line capture on documents with more than 100 pages. |
Document Analysis and Recognition | In DC 6.50, after removing a line field from a document template that had line recognition, the following error could occur when recognizing fields:
|
Document Analysis and Recognition | The 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 Templates | The 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 Templates | When a vendor had no documents and the user selected the DrillDown on the vendor card, many documents were shown. |
Documents and Templates | When 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:
|
Documents and Templates | In DC6.50 the Identification field 11310 ”Enterprise No.” was not included in the ACHAT document category. |
Documents and Templates | When pressing the Add template field button in a Microsoft Dynamics NAV 2009 R2 RTC version the following errors were thrown:
|
Documents and Templates | Adding a new field to a template could result in the following error:
|
Documents and Templates | Assigning a vendor to a document could result in the following error:
|
Documents and Templates | We have corrected an issue that allowed documents in categories without master templates to be registered without a Source ID. |
Documents and Templates | When trying to recognize documents from categories with a source table different from vendor, the following error occurred:
|
Documents and Templates | In 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:
|
Documents and Templates | In 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. |
Events | The 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:
|
Events | The 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 Setup | Document Storage Type Azure Blob Storage was wrongly shown in the classic client. When selecting Azure Blob Storage, the following error occurred:
|
Installation and Setup | When we released DC6.50, we wrote the following in the changelog:
|
Matching | When we released DC6.50, we wrote the following in the changelog:
|
Matching | Corrected a bug that would prevent auto-match from matching lines with account type different from Item. |
Matching | When 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:
|
Purchase Approval | Under certain conditions when using ”Forward without approval”, the approval hierarchy was not recreated from the user to whom the document was delegated. |
Purchase Approval | The 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:
|
Purchase Documents | When 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. |
Technical | When we released DC6.50, we wrote the following in the changelog:
|
Technical | We 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. |
Technical | When 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:
|
Translations | Captions have been updated and improved. |
Translations | Translation mistakes have been corrected. |
Translations | Wrong Germany translations have been corrected. |
Translations | We have updated NOR and ESP captions on page 6085721. |
Translations | In 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. |
Translations | When importing documents in the Norwegian and Swedish localisations, the following error occurred:
|
UI Simplification | We have aligned the field cue names (in cue setup) with the captions on the role center tiles. |
XML Import | All 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 R2, 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.
Bug fixes
Functional area | Description |
---|---|
Business Central | In 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 Recognition | In DC 6.50, after removing a line field from a document template that had line recognition, the following error could occur when recognizing fields:
|
Document Analysis and Recognition | The 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 Templates | When 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:
|
Events | The 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:
|
Events | The 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 R2, 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.
Bug fixes
Functional area | Description |
---|---|
Document Analysis and Recognition | When trying to recognize documents from categories with a source table different from vendor, the following error occurred:
|
Matching | Corrected a bug that would prevent auto-match from matching lines with account type different from Item. |
Translations | In 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. |
Translations | When importing documents in the Norwegian and Swedish localisations, the following error occurred:
|
Document Capture 2020 R2
Released: September 1, 2020
App version: 6.5.0.0
FOB version: 6.50
New or changed functionality
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 area | Description |
---|---|
Client and Company Activation | In 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 Services | Added support for Exchange Web Services (EWS) with Oauth 2.0 when running on-premises OCR processing. |
Continia Delivery Network | Unfortunately, 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 Portal | The 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 Recognition | We 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 Recognition | The 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 Recognition | Selected 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 Recognition | It’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 Recognition | A 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 Search | On the Document Search page, now the buttons are only enabled when they can be used. |
Events | The following events are added to the solution:
|
Matching | The 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. |
Matching | The following two new filter buttons are added to the matching page:
|
Matching | Transfering 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. |
Matching | A 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.,
|
Matching | To 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. |
Matching | When 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. |
Matching | When 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. |
Matching | We 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:
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. |
Matching | Previously 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. |
Matching | Automatic match can be scheduled by adding codeunit 6086022 “CDC Batch Match Document” as a recurring job queue entry. |
Matching | When using matching and line recognition, the matched document numbers are now displayed in the comment area. |
Matching | Previously 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. |
Matching | Previously 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 Approval | Advanced Approval is now supported in Business Central cloud. |
Purchase Approval | If "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 Approval | For 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 Approval | You 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 Approval | When 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 Approval | Purchase 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 Documents | When 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:
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 Documents | The 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 Documents | When a purchase invoice is created from Document Capture, the functionality for extended texts is now available. |
Technology | Please 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. |
Technology | The Document Capture service has been updated. |
Technology | We 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. |
Technology | We are now supporting Azure Blob Storage as a third Document Storage Type option. Customers must use their own Azure Storage account. |
Technology | The following events have been added, allowing partners to extend Document Capture to use other storage types: Codeunit 6085640 CDC Doc. File Events
|
UI Simplification | Informational, confirmation, and error messages have been improved. |
UI Simplification | Captions have been updated and improved. |
UI Simplification | On the “Template Card”, the following has been changed:
|
Upgrade | We 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 | With 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. |
Upgrade | If 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. |
Upgrade | With 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”. |
Upgrade | If 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 Permissions | The 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 Import | We 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
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 area | Description |
---|---|
Business Central | When importing a Zip file as a Stylesheet for an XML Master Template in the cloud versions of Business Central the following error occurred:
|
Business Central | When using a Canada, USA, or Mexico localization of Business Central cloud, the following error occurred when trying to post a purchase invoice:
|
Business Central | When 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:
|
Cloud and On-Prem OCR Services | When 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 Templates | Field 11310 (a none existing field) has been deleted from the identification fields in the configuration files. |
Documents and Templates | In some configuration files, pounds was wrongly set to GPB instead of GBP. |
Documents and Templates | When 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 Templates | Unit 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 Templates | When 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 Templates | When registering a document containing text lines (no account/item number), the following error occurred:
|
Documents and Templates | When 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 Templates | The 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 Recognition | When the PDF file had a barcode, the barcode value saved in Table 6085592 CDC Document Word was missing the last character. |
Document Analysis and Recognition | When 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 Recognition | When 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 Search | Using the Document Search functionality in Dynamics NAV versions older than Dynamics NAV 2013 (17.10.00), the following error was occurred:
|
Drag & Drop | In 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. |
Matching | When 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. |
Matching | Document lines with no number or description translations were set as not OK even though the document was matched. |
Matching | For 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. |
Matching | On 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 Approval | If 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":
|
Purchase Approval | It 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 Approval | In 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 Approval | A 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. |
Technology | Opening the Document Journal could result in the following error:
|
Technology | In 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:
|
Translations | On the page for adjusting decimals in a template field, we have updated a caption in ES localization. |
Translations | Several captions for SE localization related to Purchase Allocations are updated ("Ankomstregistrering" instead of "Förregistrering"). |
Translations | Corrected Spanish warning text the Document Journal and Card pages. |
UI Simplification | In the Classic Clients, the header fields subform was not showing the lookup and assist edit buttons for the Value and the OK columns. |
UI Simplification | For 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 Permissions | When accessing the "Continia User Setup" page for Document Capture approvals and when Expense Management was not in the license, the following error was shown:
|
XML Import | The 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 Import | Some of the template fields of the OIOXML master template had the same sort order value. |