Detailed Changelog for Continia Document Capture 2024 R1
This article lists all new features and bug fixes for each version of Continia Document Capture 2024 R1.
Tip
As a Continia partner, you can be notified of new Document Capture versions and service packs whenever they're released. To sign up for this service, go to this page in the Continia PartnerZone (only available to partners).
Important
Currently, Document Capture supports BC v14 and the three latest versions of Business Central. This will change with the release of Document Capture 2025 R1 (26.00) in April 2025. Document Capture 2025 R1 (26.00) and all future versions from then on will only support the three latest versions of Business Central.
The next version of Document Capture – Document Capture 2024 R2 (25.00) – is the last version with support for Business Central April 2019 (BC v14).
Document Capture 2024 R1 Service Pack 3
Release date, online: January 17, 2025
FOB version: 24.03
Only released in Business Central on premises.
New or changed functionality
Functional area | Description | ID |
---|---|---|
Documents and Templates | Using the Create Lines action to create the first allocation line on the Purchase Allocations page could result in allocation lines with an incorrect document type. To prevent this, the Create Line action is now only enabled if at least one allocation line has already been created. | 53361 |
Platform and Technology | Events have been added to the solution. For more information, see Event Publishers for Document Capture 2024 R1 (24.00). | 55364 |
Purchase Contracts | The Submit Review action on the Purchase Contracts and Purchase Contract pages is now only visible to users with sufficient permissions to review a purchase contract. | 54051 |
Purchase Documents | The following only applies to the Swiss (CH) localization. When creating a vendor bank account from a QR code, the following fields are automatically populated from the bank directory:
| 59483 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | Zero amounts in document lines on the document card weren't displayed when the Blank Zero setting on the template field card was set to False. | 51260 |
Documents and Templates | When updating a purchase order from the document journal under the Purchase Order category, the Quantity and Unit Cost fields in the purchase order were incorrectly set to zero when registering the document – despite the values not being captured or recognized. | 53522 |
Documents and Templates | Previously, the XML master templates had the Ask to Set Default Account No. option set to No by default. This setting has been changed to Yes, prompting users to confirm whether they want to set an account as the default when entering an account type and account number. | 53638 |
Documents and Templates | Document lines in the document card with validation errors were mistakenly marked as OK. | 54221 |
Documents and Templates | It's now possible to use the formulas TODAY and WORKDATE in the Formula field on the template field card. In combination with the Calculate Date field, this allows template date fields to be configured to use today's date or the work date – adjusted by a positive or negative date value. | 55821 |
Documents and Templates | When using a formula on the No. Series template header field to define the number series for created purchase documents, an error occurred when recognizing fields in the document journal for credit memo documents. The following error message was displayed in the comments section:
| 56198 |
Documents and Templates | The Search for Value setting on the template field card was previously disabled by default for newly created template line fields. | 57178 |
Documents and Templates | When unchecking a Boolean (i.e.: yes/no) master template field and confirming updates to templates created from that master template, the update didn't apply if the language in use wasn't English (ENU). This issue has been resolved, and the update now applies correctly – regardless of the selected language. | 57388 |
Documents and Templates | When the blank (space) character was configured as a decimal separator in the User Defined Decimal Separator setting on the template field, the decimal part of a detected number wasn't recognized. | 57476 |
Documents and Templates | When users attempted to split multiple pages within the same document, the error message below was displayed – requiring the Split and Merge Documents page to be closed and reopened between each split action.
| 57519 |
Documents and Templates | Previously, the asterisk (*) character wasn't included in the automatic rule creation when Enable Rule Generation was enabled for a template field. Now, the asterisk is included in the automatically created expression, along with the required escape character (\). See examples below.
| 57534 |
Documents and Templates | Previously, deleting a captured line on the document card caused the add-in and the document lines to become out of sync in the web client. This has been resolved, and both remain in sync. | 57574 |
Documents and Templates | Performing a lookup of the Customizable Columns on the Document Category page and selecting a column had no effect. | 57710 |
Documents and Templates | In some cases, the following error message appeared during document recognition using relative line capture:
| 57750 |
Documents and Templates | When moving XML documents to another company, the preview in the Document Viewer FactBox is now automatically shown. | 57868 |
Documents and Templates | The heading Advanced Recognition Settings on the template field card is now only visible when selecting Show More Fields. | 58100 |
Documents and Templates | When adding the template header field Vendor Shipment No., the option Match Vendor Shipment No. is now visible on the template card. Additionally, when adding the template header field Vendor Order No., the option Match Vendor Order No. is now visible on the template card. | 58728 |
Documents and Templates | An empty configurable message was generated when the Multi-Entity Management (MEM) app wasn't installed in Business Central. | 58762 |
Documents and Templates | When using AI as the document line recognition method, the Search for Value setting wasn't respected. The columns were still recognized, even when Search for Value was set to False. | 59854 |
Documents and Templates | When using the Create Vendor guide, the configured number series from the vendor template wasn't applied to the newly created vendor. | 59925 |
Documents and Templates | When capturing a value exceeding 200 characters in the template header field Our Contact, the following error message was displayed:
| 60155 |
Documents and Templates | The following issues were observed in certain cases when recognizing document lines in a PDF:
| 60508 |
Documents and Templates | During document import, if a template was already available in another company for the same vendor, the user was prompted with the following dialog:
| 60513 |
Documents and Templates | When using an XML path in a template field, an error occurred when capturing a value exceeding 1,024 characters:
| 60545 |
Documents and Templates | If an email containing both XML and PDF files had one of its attachments deleted, the related email could also be deleted – even if the other attachment remained in Document Capture. | 62164 |
Document Approval | To maintain the approval flow integrity, inserting an approver in an approval flow now requires selecting an approver ID. | 57099 |
Document Approval | This update only applies to Business Central app versions supported by this Document Capture release. These can be found in Supported On-Premises Versions for Document Capture. When deleting an approval sharing configuration record created via the Set up Out of Office feature, the following error message was displayed:
| 57893 |
Document Approval | When sending the status email to approvers, the column Amount Incl. VAT showed zero for the purchase orders. | 58523 |
Document Approval | An overflow error occurred when users opened the Purchase Approval Entries page if the vendor name contained 99 or more characters. | 59610 |
Document Approval | When the Type was set to Resource on the Approval User Group Permissions page, the permission type would be displayed as 7 in the permissions FactBox on the Continia User Setup Card. As a result, if you sent an approval request and then tried to open the document in the Web Approval Portal, the following error message appeared:
| 59713 |
eDocuments | When handling XML files containing a lot of lines (i.e.: more than 1,000), the Document Viewer FactBox wouldn't display the HTML representation of the file. | 61168 |
General Application | The values in the Approval Administrator and Allow Force Registration fields weren't transferred to other companies when configuring approval users through the User Setup by Company page. | 40901 |
General Application | On the Document Capture Setup page, when disabling Use Cloud OCR and using the Continia File Service, users received the following error message:
| 55882 |
General Application | When updating storage settings on the Document Capture Setup page and selecting Azure Blob Storage, the page now only displays fields related to the configuration of the Azure Blob storage. Previously, fields related to file system storage were also visible. | 57183 |
General Application | If the Template Nos. field on the Document Capture Setup page had no value, the related company was skipped during the upgrade process. | 61229 |
Order & Receipt Matching | When manually matching to a receipt line with item tracking configured and then updating the quantity, the following error appeared when attempting to preview post the registered document:
| 55660 |
Purchase Contracts | Previously, it was possible to manually enter a purchase contract number for a vendor other than the one specified in the document and still register the document. Now, a check ensures that the vendor in the selected purchase contract matches the vendor in the document. | 59183 |
Purchase Documents | When attempting to view the document attachments using the View in List action in the Documents FactBox, the following error message was displayed:
| 51330 |
Purchase Documents | This update only applies to Business Central app versions supported by this Document Capture release. These can be found in Supported On-Premises Versions for Document Capture. When downloading a file from the below mentioned application areas, the filename didn't adhere to the Purchase File Display Name setting on the Document Capture Setup page:
| 54447 |
Purchase Documents | When registering a purchase document to a general journal from the Purchase category, the VAT Prod. Posting Group and VAT Business Posting Group fields on the Accounts for Amounts page weren't copied to the created general journal line. The issue also affected the VAT Prod. Posting Group field on the Line Translation page. | 56620 |
Purchase Documents | This update only applies to Business Central app versions supported by this Document Capture release. These can be found in Supported On-Premises Versions for Document Capture. Attachments were missing on general ledger entries when postings were made through the General Journal or Purchase Journal using General Journal Batch with differing No. Series and Posting No. Series. | 57664 |
Purchase Documents | In some cases, when using Customizable Columns in the document journal and importing a purchase XML document, the following error message was shown:
| 57909 |
Purchase Documents | On the General Ledger Entries page, it wasn't possible to delete attachments that were added on General Journal or Purchase Journal lines before posting. | 58492 |
Purchase Documents | The following error no longer occurs when more than one drag-and-drop category is in use and you attempt to open a purchase order:
| 58808 |
Purchase Documents | When registering a prepayment invoice from the document journal, the Posting Date setting on the template card wasn't considered. Instead, the value from the Document Date field in the document header was used to set the Posting Date in the posted prepayment invoice. | 58990 |
Purchase Documents | When creating a purchase order via the document journal, the following error message was displayed if an order line had a 100% line discount:
| 59177 |
Purchase Documents | The Document Viewer and Documents FactBoxes weren't displayed on the General Ledger Entries page. | 59356 |
Purchase Documents | If Amount Validation on Post is enabled on the Document Capture Setup page, and the Purchase category has the Journal Template Name and Journal Batch Name fields filled out, posting a manually created general journal entry with drag-and-drop attachments for a vendor account type would display the following error:
| 60204 |
Purchase Documents | Previously, if you had more than one drag-and-drop category configured and tried to register a document in the Purchase Order category, you would get the following error:
| 60840 |
Purchase Documents | When enabling Check for Attachment Before Posting on the Document Capture Setup or Expense Management Setup pages, attempting to post a payment journal line with a document type of Payment or Refund would result in the following error message:
| 62335 |
eDocuments | The following UI changes have been applied to eDocuments:
| 57957 |
eDocuments | When importing an eDocument or using the Recognize Fields action for an eDocument, the following error could occur:
| 59408 |
eDocuments | The following error could occur when sending a sales invoice through the Continia Delivery Network:
| 59493 |
eDocuments | When importing electronic documents using Continia eDocuments, the document lines were recognized even when the values captured weren't valid or no value was found for a field configured as required. | 60191 |
eDocuments | Previously, when sending an invoice with Procurement-BilSim selected as the network profile for the OIOUBL invoice in the XML structure, an error occurred if the receiver was only registered to receive invoices with the NES5 profile. The error message displayed was:
| 60266 |
eDocuments | Additional documents are now correctly attached when sending eDocuments. | 60267 |
eDocuments | When sending a Peppol sales invoice with negative line quantity or price, the validation would fail. | 60360 |
eDocuments | When sending a Peppol eDocument from a Swedish identifier (SE:ORGNR) via the Continia Delivery Network, a validation error was shown in the Validation Log on the eDocument card. The log can be accessed via the eDocument Status field.
While the code fix addresses the issue for new data, you may need to correct existing mappings manually. Follow these steps to resolve incorrect data:
| 60688 |
eDocuments | When sending a posted credit memo through the Continia Delivery Network as a Peppol credit note (BIS 3.0) document, validation errors were shown in the Validation Log on the eBilling Outgoing Document card. The log can be accessed via the eDocument Status field.
| 60950 |
eDocuments | When sending a sales invoice as a Peppol or OIOUBL electronic document, empty fields of the type GUID were exported in the XML document, causing the eDocument validation to fail. | 61144 |
eDocuments | Sending an OIOUBL sales invoice through the Continia Delivery Network could result in document transmission failure due to the following validation errors:
| 61210 |
eDocuments | When sending an invoice through the Continia Delivery Network, the XML element Invoice/cac:AccountingCustomerParty/cac:PartyName/cbc:Name incorrectly displayed the Customer No. instead of the Customer Name. | 61235 |
eDocuments | When sending an invoice through the Continia Delivery Network, the following validation error appeared in the Validation Log on the eBilling Outgoing Document card:
| 61242 |
eDocuments | When sending an invoice via the Continia Delivery Network in the Netherlands localization, the following error appeared:
| 61331 |
eDocuments | When sending an eDocument using a network profile (cbc:ProfileID) other than the one set as default in the XML structure, the profile wasn't updated in the XML document – and the default profile was used instead. The cbc:ProfileID in the XML document is now correctly set based on the network profile used to send the eDocument. | 61432 |
eDocuments | Multiple issues related to OIOUBL credit note and invoice validation when sending documents through the Continia Delivery Network have been resolved. These include:
| 61450 |
eDocuments | The following document reference-related issues have been addressed:
| 61555 |
eDocuments | Import of regional payment IDs is now supported in the localizations mentioned below:
| 61607 |
eDocuments | When sending a Peppol BIS3 electronic invoice through the Continia Delivery Network, the Invoice/cac:PaymentMeans/cbc:PaymentMeansCode value was incorrectly set to 31 when using bank account payment. This has been corrected, and the value is now set to 30. | 61700 |
eDocuments | When recognizing field values from eDocument sources, no template field translations were applied to the captured value. | 61766 |
eDocuments | When importing XML files through eDocuments, additional document attachment would in some cases be stored without a complete file name causing the file not to be properly available in Business Central. | 61777 |
eDocuments | When opening the Role Center, the number shown in the Document Capture eDocuments Requiring Attention cue was incorrect. | 61843 |
eDocuments | Switching from demo credentials to production credentials and running the Continia Delivery Network onboarding could result in duplicate metadata records being created. | 61905 |
eDocuments | When importing a document with multiple tax specifications on the document lines – each having the same Tax Percentage and Tax Category ID – the following error message was displayed:
| 62053 |
Document Capture 2024 R1 Service Pack 2, hotfix 1
Release date, online: September 26, 2024
App version: 24.2.1.0
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Purchase Documents | The following error no longer occurs when more than one drag-and-drop category is in use, and you attempt to open a purchase order:
| 58808 |
eDocuments | When enabling Continia eDocuments from the Continia Feature Management page or running the Continia eDocuments Wizard from search with the Copy and convert existing customer and vendor templates setting enabled, the following error no longer occurs:
| 59579 |
eDocuments | When importing an eDocument or using Recognize Fields on it, the following error no longer occurs:
| 59408 |
eDocuments | When sending an invoice via the Continia Delivery Network, the following error no longer appears:
|
Document Capture 2024 R1 Service Pack 2
Release date, online: August 23, 2024
Release date, on-premises: August 23, 2024
App version: 24.2.0
FOB version: 24.02
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | When using the standard functionality Merge duplicate records available in Business Central, any Document Capture documents associated with Vendors or Customers being merged are included in the merge process. Note that moving Document Capture documents is supported in BC 24.00 and newer versions. | 54671 |
Platform and Technology | Events have been added to the solution. For details, see Event Publishers for Document Capture 2024 R1 (24.00). | 55364 |
Platform and Technology | The Continia Web Approval Portal has been updated to version 24.0.3. | 57382 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | This change only applies to the BE localization: In the list of template field Document Type, all captions that previously started with "O:" have been changed to start with "V:". | 54471 |
Country and Regional | In some localizations, an incorrect Account Type was potentially selected when using the Recognize Fields action. | 56942 |
Document and Templates | When using File Service as a Document Storage Type in the Document Capture Setup, the Document Categories were made inaccessible if an imported filename exceeded 100 characters. The following error message was returned:
| 50565 |
Document and Templates | When doing line recognition, template suggestions were in some cases unintentionally shown – even if they where previously applied. Accepting the suggestion again produced the error message Record in the table Template Suggestion already exists. | 55042 |
Document and Templates | During document import, a new template was wrongly created for the document when there was already a template available in another company for the same vendor. Now, a new template won't be created – and the template number won't be populated in the document journal. Instead, you must run Recognize Fields manually in the document journal. This triggers the following dialog:
| 55407 |
Document and Templates | When the Secure Archive feature was enabled and either Auto Split or Merge From Same E-mail were used, these actions were incorrectly regarded as file changes – resulting in the following error when posting an invoice:
| 55986 |
Document and Templates | When filtering document lines in the Document Card, the highlighted field in the document viewer didn't correspond with the actual line selected in the Document Lines subpage. To address this, the Line No. column is shown on the lines subpage, if not already present, when filtering. The column is removed automatically when the filter is released. | 56132 |
Document and Templates | When registering a document in the Contact category using the Register & Show option, the following error message was displayed:
| 56559 |
Document and Templates | When using document search in environments with XML documents, users could experience a degraded performance caused by unnecessary external calls to Continia Online. These external calls have been removed, resulting in a better search performance. | 56889 |
Document and Templates | The Sales category Force Register action used to require a value in Account for Amount Excl. VAT. This has been changed, so the Sales category Force Register action works in the same way as the Purchase category Force Register action. | 57512 |
Document and Templates | Attachments weren't displayed when using Find Entries, nor were they displayed in the Documents FactBox and Document Viewer in the General Journal and General Ledger Entries pages. | 58058 |
Document and Templates | The Document Viewer and Documents FactBox wasn't shown in the General Ledger Entries. | 58385 |
eDocuments | The currency CHF has been added as a Translate From value in the template field translation for all localizations. | 56774 |
General Application | These two issues related to attached files have been corrected:
| 53168 |
General Application | When using the Line Capture Version 2.0 codeunit to recognize line values, the auto calculation of missing line values isn't done for zero-values if a zero-value is captured in the document. | 55041 |
General Application | When capturing an MEM entity value longer than 20 characters, the following overflow error message was returned:
| 56954 |
General Application | When switching document storage type from File System to File Service, the following error was returned:
| 57182 |
General Application | This change only applies to the AT, CH, and DE localizations' master template BESTELLUNG-DE,CH,AT:
| 57528 |
Order & Receipt Matching | This change only applies to the DK localization: When registering a purchase document with the Payment ID (FIK-kode), using the Invoice Reg. Step 1 setting as Match and Update Order in the Template Card, the Payment Method Code, Payment Reference, and Creditor No. weren't populated in the matched purchase order. | 47894 |
Platform and Technology | The field Web Site URL on the Continia Web Portal Card is now hidden, as it shouldn't be used. | 51051 |
Platform and Technology | If the Show Embedded PDF as Default field is marked but there is no PDF, the HTML is displayed – instead of no visualization at all. | 57113 |
Purchase Documents | When registering a purchase document as a prepayment, it was possible to select a fully invoiced purchase order. Now, when selecting purchase orders, the fully invoiced purchase orders are hidden. Attempting to specify fully invoiced purchase order manually results in an error comment, and the registration of the document is prevented. | 45585 |
Purchase Documents | On a purchase order line, you can now only change its line's Type if the purchase order status is Open or Pending Approval and you're allowed to edit pending documents. Previously, any user could change the line type to comment (which ultimately deletes the line) – even after a document had been released. This left room for mistakes. | 53734 |
Purchase Documents | The action Change Imported Amounts has been moved to the action group Credit Memo on the the Purchase Credit Memo page. | 54044 |
Purchase Documents | Previously, the Vendor Create function in the document journal would sometimes return the overflow error The length of the string is XX, but it must be less than or equal to YY characters when the field value was longer than YY. | 54450 |
Purchase Documents | The Create Digital Vouchers for Document Capture Documents has been added to allow existing customers who chose to enable the Enhanced Digital Vouchers feature to post invoices created before the enabling. This report identifies purchase invoices that lack an entry in the Incoming Document table. It tries to find a corresponding Document Capture document and copy this to the Incoming Document table. | 57521 |
Platform and Technology | Fixed an issue where the document import could fail, resulting in the following error message:
| 57844 |
Purchase Documents | In some cases when no lines were recognized, the line field values in the created purchase invoice could have been overwritten with false data if the template line field had a value in Field in Purchase Line under the Transfer Value to... group on the General FastTab. | 53707 |
Document Capture 2024 R1 Service Pack 1, hotfix 6
Release date, online: August 7, 2024
App version: 24.1.6
Only released in Business Central online.
New or changed functionality
Functional area | Description | ID |
---|---|---|
eDocuments | The field Order Line No. has been added to the eBilling Lines, though by default it's not visible. The Order Line No. is required when sending eDocuments to Dutch customers. | 57907 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | The following issues have been fixed:
| 53168 |
Document Capture 2024 R1 Service Pack 1, hotfix 5
Release date, online: July 18, 2024
App version: 24.1.5
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Purchase Documents | In Document Capture 24.00 Service Pack 1, hotfix 2 (task ID 56612), changes were implemented to ensure that documents attached to a purchase or sales order are also visible on the corresponding posted invoice. These changes unwantedly caused documents added to a posted invoice via drag and drop to be attached to the originating order instead. To address this, the code introduced in the original bug fix (ID 56612) has been removed. A better solution to this issue is being actively sought, but there's currently no estimated release date for the fix. | 57907 |
Document Capture 2024 R1 Service Pack 1, hotfix 4
Release date, online: July 5, 2024
App version: 24.1.4
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | When customers try to upgrade to Document Capture 24.1.3, they could encounter this error:
| 57539 |
Purchase documents | Document preview was missing from the General Ledger Entries when sales or purchase documents were registered in the document journal, and the corresponding sales or purchase documents in Business Central were created and posted. | 56931 |
Document Capture 2024 R1 Service Pack 1, hotfix 3
Release date, online: July 3, 2024
App version: 24.1.3
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | Registering documents in companies, where:
| 57484 |
Documents and Templates | When customers try to upgrade to Document Capture 24.1.2, they could encounter these errors:
| 57495 |
Document Capture 2024 R1 Service Pack 1, hotfix 2
Release date, online: July 2, 2024
App version: 24.1.2
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | When the Secure Archive feature was enabled and either of the following features were used:
| 55986 |
Purchase Documents | When creating Purchase Order with attachments from the Purchase Order category, the attachments were later not available in the Posted Purchase Invoice. | 56612 |
Purchase Documents | Relevant only to Danish cloud-based production tenants: With the mandatory enforcement of digital vouchers starting on July 1, 2024, Document Capture automatically generates digital vouchers based on Document Capture files. Before this date, many customers could have registered documents and created purchase documents without any automatically generated digital vouchers. The posting of these documents is therefore blocked. When this hotfix is installed, Document Capture searches for all purchase documents in the Purchase Header table and check if they originate from Document Capture. If so, a digital voucher is created. | 57438 |
Document Capture 2024 R1 Service Pack 1, hotfix 1
Release date, online: June 4, 2024
App version: 24.1.1
Only released in Business Central online.
Bug fixes
Functional area | Description | ID |
---|---|---|
Documents and Templates | When registering a document, with lines recognized, in the Sales category, the unit price on the created Sales Order or Sales Credit Memo was unintentionally taken from the DC document. This behavior has been changed to use the default sales prices as specified in Business Central. | 56645 |
Document Approval | After migrating from Business Central on-premises to Business Central online, the Delegate to me link in the email could sometimes wrongly point to the old on-premises server, preventing users from being able to open the link. | 56646 |
General Application | When completing the cloud migration, users got the following error:
| 56738 |
Platform and Technology | When upgrading to Document Capture 24.00, users might encounter the following error:
| 56737 |
Document Capture 2024 R1 Service Pack 1
Release date, online: May 28, 2024
Release date, on-premises: May 29, 2024
App version: 24.1.0
FOB version: 24.01
New or changed functionality
Functional area | Description | ID |
---|---|---|
Documents and Templates | Added vendor bank account validation for Australian bank accounts (EFT BSB). | 40793 |
Documents and Templates | The event OnBeforeSetRetentionPeriod(ToDate,Handled) is added in the codeunit CDC Data Maintenance Mgt. This makes it possible to bypass the 2 year limit on deletion of document words and document values specified in the Retention Perion (Years) field on the Document Capture Setup page | 54734 |
Document Approval | When migrating from Business Central on-premises to Business Central online and utilizing the Web Approval Portal, an invalid configuration could be migrated. This could block the export of users to Continia Online. Now, the web portal configuration is sanitized to make sure that users can be exported to Continia Online. | 54937 |
Document Approval | The following change only applies to Business Central online. When exporting users, the current Web Approval Portal setup is validated to ensure that it is supported in Business Central online. If the setup if not supported, the following error is shown:
| 54943 |
eDocuments | Added a new job queue entry, eDocuments metadata update, which is scheduled to run once a day at a random time between 06:00PM and 05:00AM. This job queue is used for updating participations and networks metadata. Two new fields have been added to the Continia eDocuments Setup page:
| 51250 |
eDocuments | Added a new job queue entry, eDocuments document update, which is scheduled to run every 30 minutes. This job queue is used for updating document statuses, download new documents and receipts. Two new fields have been added to the Continia eDocuments Setup page:
| 51251 |
eDocuments | The following changes have been made when sending Peppol and OIOUBL sales invoices and credit memos:
| 54789 |
eDocuments | Introducing two new fields:
| 54901 |
eDocuments | Added the action Open Xml File to the following pages:
| 55318 |
General Application | By enabling the Check Item Prices option on the template in the Sales category, the item's recognized unit cost is validated against the price specified on the item card. If any special prices or discounts are configured for the item, the price check is conducted against the relevant special price or special discount. Should the unit cost of the recognized item differs from the special price or unit price calculated from the item card, a warning is displayed in the comment section. If the Line Discount % template line field contains a valid value or a special discount is configured for the item, the discount percentage is included in the unit cost comparison. | 47648 |
General Application | With Binary Stream MEM installed and the entity dimension value was missing in the Document Journal, the following message was shown in the comment section:
| 54434 |
General Application | Added identification rules to the XRECHNUNG-ID XML identification template to support XRechnung version 2.3 and 3.0. | 56585 |
Platform and Technology | Events have been added to the solution. For details, please see Event Publishers for Document Capture 2024 R1 (24.00). | 55364 |
Platform and Technology | The Continia Web Approval Portal has been updated to version 24.2 | 56581 |
Purchase Documents | Previously, it was possible from a general journal or purchase journal to delete attachments associated to a posted ledger entry having the same document number as the unposted journal entry. Now, it is only possible in the journals to view the attachments that are related to the posted entries. In addition to the above change, the attachments added to an unposted general or purchase journal |