Detailed Changelog for Continia Document Capture 2024 R1

• Name
• Address
• Address 2
• City
• Post Code
• SWIFT Code

• No. Series is not correct.

• You cannot select pages from single-page documents nor pages that are the first page in a document.

• Captured string *123456 generates the rule *[0-9]{6}
• Captured string *123456* generates the rule *[0-9]{6}*
• Captured string 123A*456 generates the rule [0-9]{3}A*[0-9]{3}

• Overflow under conversion of Microsoft.Dynamics.Nav.Runtime.Decimal18 value to System.Int32

• The length of the string is <Number>, but it must be less than or equal to 200 characters.

• The last line of the document wasn't recognized.
• The bottom line of the document was duplicated and, therefore, captured twice.

• A template for has been found in company , do you want to copy this template?

• The length of the string is <String Length>, but it must be less or equal to 1,024 characters. Value: <File name>

• JIT loading of field(s): 'Display Order, Forward E-mails' failed for table: 'Approval Sharing' identification values: 'Owner User ID='<User ID>',Shared to User ID='<Shared User ID>',Sharing Type='Out of Office',Valid From='<From Date>',Valid To='<To Date>''

• There is an error in XML document (1, 1544)

• You must install the on-premises version of Continia Document Capture to use server-side resources, such as file system and assemblies.

• The record is not open.

• Document journal
• Document card
• Document search
• Documents FactBox on the Vendor card
• Documents FactBox in a posted purchase invoice

• The changes to the document record cannot be saved because some information on the page is not up-to-date. Close the page, reopen it, and try again.Identification fields and values:No.='<Document No.>'

• The document does not exist. Identification fields and values: Entry No.='1'

• No Account has been configured for Amount Excl. VAT.

• The journal lines with Document No. <Document No.> are linked to Document Capture Document <Document No.>.

• Document: The Document does not exist. Identification fields and values: Entry No.='2'

• It is mandatory to have either an incoming document, a Document Capture file or an Expense Management attachment associated with a vendor-related general journal.

• The eDocument Card and Open in Document Journal actions on the eDocument Overview page have been moved from the New action group to the Process action group.
• The Find Entries and Open in Document Journal actions on eDocuments cards, such as purchase orders, have been promoted to the Process action group.

• The supplied field number '<Field Number>' cannot be found in the '<Table Name>' table.

• You are trying to send a network document (Simpel Fakturaproces - Procurement-BilSim-1.0) to Customer <Customer No.>, who does not support receiving this type of document. Please go to the Continia eDocument Setup page on the Customer to see more.

• <Vendor/Customer> Endpoint Scheme is mandatory.

• VAT Amount (VAT Currency) is mandatory.
• VAT Currency Code is mandatory.

• [F-LIB306] Exactly one TaxTotal class must contain VAT (Moms)
• [F-LIB065] Invalid TaxScheme/ID. Must contain a value
• [F-LIB197] TaxTypeCode must be a value from the 'urn:oioubl:codelist:taxtypecode-1.2' codelist when TaxScheme/ID is different from '63' or 'VAT' (Moms)
• [F-LIB070] Invalid schemeID. Must be either 'urn:oioubl:id:taxschemeid-1.1', 'urn:oioubl:id:taxschemeid-1.2', 'urn:oioubl:id:taxschemeid-1.4' or 'urn:oioubl:id:taxschemeid-1.5'
• [F-LIB306] Exactly one TaxTotal class must contain VAT (Moms)
• [F-LIB065] Invalid TaxScheme/ID. Must contain a value.
• [F-LIB197] TaxTypeCode must be a value from the 'urn:oioubl:codelist:taxtypecode-1.2' codelist when TaxScheme/ID is different from '63' or 'VAT' (Moms)
• [F-LIB070] Invalid schemeID. Must be either 'urn:oioubl:id:taxschemeid-1.1', 'urn:oioubl:id:taxschemeid-1.2', 'urn:oioubl:id:taxschemeid-1.4' or 'urn:oioubl:id:taxschemeid-1.5'

• Microsoft.Dynamics.Nav.Runtime.NavFieldRef variable not initialized.

• Validation errors caused by incorrect formatting in the Invoice and Credit Note elements.
• Missing or incorrectly populated mandatory fields in the OIOUBL document structure.
• Validation failures for specific business rules when sending OIOUBL documents.
• Added support for exchange of Instruction ID and Vendor Account No. relevant for importing FIK payment IDs.

• The Buyers Reference on the eBilling header is now populated with the value from the Your Reference field on the posted sales invoice.
• Prevented a potential overflow issue on a sales invoice when populating External Document No. having more than 30 characters.

• eBilling NO (Peppol): A new template field, KID, has been added to the master template. The field is pre-configured to capture the payment reference from the XML document.
• eBilling DK (Peppol and OIOUBL): A new template field, FIK, has been added to the master template. The field is pre-configured to capture the payment reference from the XML document. To ensure proper capture of the FIK string, it's necessary to update the XML structure for OIOUBL.
• eBilling SE (Peppol): A new template field, OCR Nummer, has been added to the master template. The field is pre-configured to capture the payment reference from the XML document.

• The record in "VAT Subtotals" already exists. Identification fields and values: <record primary key fields>

• The Document does not exist. Identification fields and values: Entry No.='1'

• /???:Invoice/???:PaymentMeans/???:PaymentID[@schemeAgencyID='320'and@schemeID='urn:oioubl:\id:paymentid-1.1']" is not valid for the XML Path field on the XML Structure table. An error occured while interpreting the filter: Did not expect '=

• The supplied field number '<Field Number>' cannot be found in the '<Table Name>' table.

• The length of the string is <Length of string>, but it must be less than or equal to 30 characters. Value: <Value>

• The length of the string is <Length>, but it must be less then or equal to 100 characters. Value: <File Name>.

• A template for <Vendor No.> <Vendor Name> has been found in company <Company Name>, do you want to copy this template?

• One of the files (<Doc No.>) associated with this document has been changed since it was imported. This is not allowed when Secure Archive is enabled.

• The Interaction Log Entry does not exist. Identification fields and value: Entry No.='<Entry No.>'.

• The Attachments field on posted documents would, in certain cases, display a different number of attached files than the number of files shown in the list if the attachments page was opened.
• When registering an invoice in the PURCHASE category with the Match and Update Order register option, the name of that attachment would be "Order xxx". This has been changed to "Invoice (Order xxx)" to make it clearer that the attachment originates from an invoice.

• The length of the string is <Captured Value Length>, but it must be less than or equal to 20 characters. Value: <Captured Value>

• The path specified in Archive File Path could not be found. Please check that the folder exists and that you have access to the folder before changing Document Storage Type.

• Description changed from "Default GB" to "Standard - DE, CH and AT"
• Language Code changed from "ENG" to "DEU"

• The value "XXXXXXXXXXXXXX" can't be evaluated into type Decimal.

• The Attachments field on posted documents would in certain cases display a different number of attached files compared to what was shown in the list if the attachments page was opened.
• When registering an invoice in the PURCHASE category with the Match and Update Order register option, the name of that attachment would be 'Order xxx'. This has been changed to 'Invoice (Order xxx)' to make it clear that the attachment originates from an invoice.

• The Continia Company Setup does not exist. Identification fields and values Primary key=

• Digital Vouchers are created automatically (Enforce Digital Vouchers), and
• The field Require Approval To Create set to "Yes" in Incoming Documents Setup 

•  This incoming document requires releasing.

• This incoming document requires releasing
• The Continia Company Setup does not exist. Identification fields and values Primary key=''

• Auto Split
• Merge From Same E-mail

• One of the files (<Doc No.>) associated with this document has been changed since it was imported. This is not allowed when Secure Archive is enabled.

• The request to remove the integration runtime failed.
  Do you want to continue with disabling the replication?
  
  Error:
  The supplied field number '6085618' cannot be found in the 'Document Category' table.

• "The length of the string is <length>, but it must be less than or equal to 50 characters. Value: <Field value>“

• Web portal code <code> is not supported in Business Central Online.

• Update Metadata Automatically: A boolean field for enabling or disabling the job queue entry.
• Metadata Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.

• Update Documents Status Automatically: A boolean field for enabling or disabling the job queue entry.
• Documents Update Job Status: A text field showing the status of the job queue entry. Select the field to open the related Job Queue Entry Card.

• Improved handling of discounts.
• Improved handling of multiple tax rates.
• Added support for comment lines.

• Use Document Information for Customer Party on the Customer eDocument Setup page.
• Use Document Information for Seller Party on the Vendor eDocument Setup page.

• Incoming eBilling Document
  
• eBilling Outgoing Document Card
  
• eBilling Response
  
• eOrder Document
  
• eOrder Response
  

• Multi Entity Company is not specified.

• MEM <Entity Label> is not specified (<Entity Dimension>).
  

• Client ID must have a value in CSC Client Credential: Primary Key=. It cannot be zero or empty.

• The value of INDEXING parameter 1 is outside of the permitted range. The current value is: -1. The permitted range is: from 0 to 2.147.483.647.

• The length of the string is 11, but it must be less than or equal to 10 characters. Value: <Document No.>

• Metadata object CodeUnit <id> was not found.

• .../cac:Party/cac:PartyLegalEntity/cac:RegistrationAddress/cbc:CityName
  
• .../cac:Party/cac:PartyLegalEntity/cac:RegistrationAddress/cac:Country/cbc:IdentificationCode

• You are trying to send a network document ([eDocument format]) to [Recipient Type] [Recipient No.], who is not registered in the network.

• The supplied field number '180' cannot be found in the 'eDocument Response Header' table.

• When creating an eOrder response from a sales order, the missing value AcceptIndicator for the OIOUBL format, which is based on whether the order is accepted or rejected, has been added.
• In the creation process of an OIOUBL eOrder Response Simple eDocument, when the attempt to generate response lines was unsuccessful, the following error message was shown: 
• eDocument Line Action has no translated code list value code for <Line Response Action>.

The system now refrains from creating response lines if the eDocument format does not support them.

• When recognizing an OIOUBL eOrder Response Simple eDocument in Document Capture the following error was shown:
• The Code List does not exist. Identification fields and values: ID=''. 

• "No XML structure was found for the current XML document"

• "ID is mandatory for line 0". 

• Base Quantity Price is mandatory for line <Line No.>.
• Line Amount is mandatory for line <Line No.>.
• VAT Category ID is mandatory for line <Line No.>.

• <Another Language Option Value> is not an option. The existing options are: <Current Language Option 0 Value,Current Language Option 1 Value,Current Language Option 2 Value,...>

• The length of the string is <String Length>, but it must be less than or equal to 50 characters. Value: <String Value>

• The record in table VAT Sub Total already exists. Identification fields and values: Header Table No.=<eDocument Header Table No.>Header Type=<eDocument  Header Type>,Document No.=<eDocument No.>,Document Line No.=<eDocument Line No..>,VAT Category Id=<VAT Category ID>
  

• You do not have the following permissions on TableData CTS-CDN Document: Modify.

• AT,BE,CH,DE,DK,ES,FI,FR,NL,NO,SE

• Customer Card
• Customer List
• Vendor Card
• Vendor List
• Sales Order
• Purchase Order
• Purchase Invoice
• Purchase Credit Memo
• Purch. Cr. Memo Subform
• Posted Sales Invoice
• Posted Sales Credit Memo
• Posted Purchase Invoice
• Posted Purchase Credit Memo
• Posted Purch. Cr. Memo Subform
• Document Sending Profile
  
• Select Sending Options
  
• Service Order
  
• Posted Service Credit Memo
  
• Posted Service Invoice
  

• A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (auth.continiaonline.com:443) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

• No connection could be made because the target machine actively refused it. (<Service URL>)
  

• WARNING: Partial Match

• Prices Including Tax must be equal to 'No' in Purchase Header: Document Type=<Document Type>, No.=<Document No.>. Current value is 'Yes'.

• The quantity (<Document Line Quantity>) on line <Document Line No.> is greater than the matched quantity (<Purchase Order Line Quantity>) on the purchase order.

• You cannot attach a file to the journal line. Document no. and account no. are both required.

• This Order has not been created from Continia Document Capture.

• Sorry, the current permissions prevented the action. (TableData 6085619 CDC AI Record Tree Relation Read: Continia Document Capture)

• Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.

• The XML Document contains [discounts and charges] elements that are not created as Fields for this Template. Please use Add Template Field to add them.
  

• Document Capture documents registered to a general ledger or purchase journal are now included in the secure archive.
• Attachments (drag-and-drop) added through a general ledger or purchase journal are now included in the secure archive
• An action to access the Document Log Summary is available on the Find Entries page.

• Only Owner User
• Only Shared To User
• Both Users

• Support for the capture of document lines spanning multiple rows
  
• Relative line capture including the ability to capture field captions at line level
  
• Ability to capture only the part of the line field data that matches a specific rule
  

• Ability to combine AI with manual capture
  
• AI-based line recognition assistant notifying you about potential improvements
  

• Rejected by [ApproverID] on behalf of [Original ApproverID].

• The functionality is enabled for all supported purchase document types (invoice, credit memo, order and return order).
• The feature is supported when using Continia Standard Approval and Approval Flow Codes.
• Only approval request in a consecutive order in the approval sequence will be automatically approved.
• Approval using Account and Dimensions Approval Permissions and Advanced Approval is NOT supported.

• All versions prior to BC23.2: The feature can be enabled in Document Capture Setup,
• BC23.2 and newer: The feature will be automatically enabled if Digital Voucher Setup and Digital Voucher Entry Setup is configured to check for attachments prior to posting.
• Specifically for Denmark: When using BC23.2 or newer, and the environment is a production environment in Cloud, the digital voucher functionality is forcedly enabled from July 1st 2024. Consequentially Document Capture will automatically create digital vouchers from that date and onwards.

• Nothing is exported, because no changes have been done since the last export.

• Document Capture 8.00
• Document Capture 9.00
• Document Capture 10.00
• Document Capture 11.00
• Document Capture 12.00

• Create Posting Description Line: A boolean field that specifies whether a second comment purchase line will be created. The extra comment line is placed under the general comment line that contains the contract number.
  
• Posting Description: An option field that specifies whether the purchase line description will be populated from the recognized document's posting description. The available options are:
  
• No (default value): A purchase line with the invoice posting description will not be created.
  
• Yes - If Present: A purchase line will be created with the posting description from the invoice if the description field contains a value. If the posting description value is blank, the Purchase Contract Description field's logic is considered.
  
• Yes: A purchase line will be created with the posting description from the invoice if the description field contains a value.
  
• Purchase Contract Description: A boolean field that specifies whether the purchase line description will be populated from the purchase contract description:
  
• False: A purchase line with the purchase contract description will not be created.
  
• True: A purchase line will be created with the purchase contract description if Posting Description is set to No or Yes - If Present and the invoice posting description contains no value.

• The End Date can't be earlier than latest related invoice's posting date (<Posting Date>).
• The Start Date can't be greater than latest related invoice's posting date (<Posting Date>).
  

• The Invoice Date can't be before the Purchase Contract Line <Line No.> Start Date (<Start Date>).
• The Invoice Date can't be after the Purchase Contract Line <Line No.> End Date (<End Date>).

• Purchase Contract No.
• Purchase Contract Line No.
• Purchase Contract Line Amount

• Start Review
• Return to Reviewer
• Finish Review
• Cancel Review

• Amount Incl. VAT must be zero or positive.
  

• WARNING: The Quantity (<Document Line Quantity>), Unit Cost(<Document Line Unit Cost>), Promised Receipt Date (<Document Line Promised Receipt Date>) on line <Document Line No.> will update the purchase order line Quantity (<Purchase Order Line Quantity>), Unit Cost(<Purchase Order Line Unit Cost>), Promised Receipt Date (<Purchase Order Line Promised Receipt Date>).

• WARNING: The Quantity (<Document Line Quantity>)), Unit Cost (<Document Line Unit Cost>), Promised Receipt Date (<Document Line Promised Receipt Date>) on line <Document Line No.> will update the Quantity (<Purchase Order Line Quantity>), Unit Cost (<Purchase Order Line Unit Cost>), Promised Receipt Date (<Purchase Order Line Promised Receipt Date>) on purchase order line <Purchase Order Line No.>.

• The length of the string is <String Length>, but it must be less than or equal to 80 characters. Value: <String>

• Tax Liable
• Tax Area Code

• Tax Liable
• Tax Area Code
• Tax Group Code

• The selected Standard Amount Distribution Code ([Code]) is unavailable for vendor no. [VendorNo] ([VendorName]).
  

• When registering a Purchase Order in the Purchase Order category and adding attachments to this, the dropdown menu contains the original Purchase Order and the Attachment category after. 
• If the Purchase Order is created manually and a Purchase Invoice registered using the register option Match and Update Order, the dropdown will contain the Attachment category populated with the document files from all related invoices. 
• If the Purchase Order is created manually, and all attachments are done using Drag and Drop, then the Document Viewer is not visible.