Detailed Changelog for the Continia Delivery Network
This article lists all new features and bug fixes for each version of the Continia Delivery Network.
Continia Delivery Network 24.02.03
Released: October 31, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | When sending a sales invoice as a Peppol or OIOUBL electronic document, the endpoint ID for both the customer and the vendor wasn't formatted according to the electronic format requirement. For electronic documents sent via NemHandel that failed validation, this issue prevented proper mapping of the validation error receipt – causing the document to be marked as 'Sent successfully', even though it wasn't actually delivered. | 61027 |
eDocuments | When sending a Peppol sales invoice with a negative line quantity or price, the validation failed. | 60360 |
eDocuments | When sending a sales invoice as a Peppol or OIOUBL electronic document, any empty fields of type GUID were exported in the XML document. This caused the eDocuments to fail validation. | 61144 |
Continia Delivery Network 24.02.02
Released: October 10, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting a Peppol document with only a GLN for the delivery information, the document failed validation. | 60393 |
Continia Delivery Network 25.00
Released: October 1, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | For the New Zealand localization, the company identifier was taken from the field 11620 ABN and not from the field with number 90 GLN. | 58005 |
General Application | When exporting a Peppol XML document, the allowance charge node wasn't created when the line discount amount was less than 0. | 57836 |
Continia Delivery Network 24.02.01
Released: September 17, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | When exporting a Peppol document from a Danish company, the payment means information was wrongly created, causing the document to fail validation. | 59509 |
Continia Delivery Network 24.02
Released: August 30, 2024
Bug fixes
Functional area | Description | Id |
---|---|---|
Country and Regional | Fixed the following issues in OIOUBL Order:
| 57394 |
Country and Regional | For the New Zealand localization, the company identifier was taken from the field 11620 ABN and not from the field with number 90 GLN. | 58005 |
General Application | When an eOrder response document is used to relay an item substitution from the selling party to the buying party, the substituted Item No. did not propagate correctly to the purchase document at the buying party. | 56149 |
General Application | When exporting an Peppol XML document the allowance charge node was not created when Line Discount Amount was less than 0. | 57836 |
Continia Delivery Network 24.01.07
Released: August 7, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | Prior to this fix, the following error was thrown when receiving a posted sales invoice or a purchase order with varying VAT percentages on different lines (e.g.: 25% and 10%) through the Continia Delivery Network:
| 58107 |
General Application | Prior to this fix, an error was thrown when trying to export an XRechnung document in a sandbox environment. | 58023 |
Continia Delivery Network 24.01.06
Released: July 30, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | When sending an eDocument where the type of the line was G/L Account, no unit of measure was used on the eDocument line. This caused the eDocument to not pass the validation. | 58006 |
Country and Regional | For the New Zealand localization, the company identifier was taken from the field 11620 ABN and not from the field with number 90 GLN. | 58005 |
eDocuments | The default value set on the XML structure entry was not used for the eDocument lines. | 57399 |
eDocuments | When an incoming eDocument contained a field with a date older than or equal to 01-01-1753, the following error occurred:
| 58013 |
Continia Delivery Network 24.01.05
Released: July 12, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | When exporting an XML document with an additional document attached, users might encounter the following error:
| 57634 |
eDocuments | The validation rule for the identifier type 0208 BE:EN has been updated. The new validation rule is: [0-1]{1}[0-9]{9} . | 57702 |
eDocuments | When selecting multiple documents to send through eDocuments, the following error occurred:
| 57915 |
Continia Delivery Network 24.01.04
Released: July 3, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | When importing an electronic document containing a mix of namespace declarations, an error occured when reading the content of the document causing the Bussiness Central client to crash. | 57389 |
eDocuments | The value of the legal company ID was not trimmed according to the validation rules of the electronic document. | 57396 |
eDocuments | When trying to send an electronic invoice that contained a comment line with a description longer than 50 characters, the following error occured:
| 57397 |
Continia Delivery Network 24.01.03
Released: June 26, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
eDocuments | Recognizing fields in an electronic document that contained document lines with InvoicedQuantity = 0 would produce the following error message:
| 57282 |
Continia Delivery Network 24.01.02
Released: June 13, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an invoice or a credit memo as an XRechnung document, XRechnung version 3.0 will be used. | 54595 |
Continia Delivery Network 24.01.01
Released: June 4, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When onboarding a new company with the network identifier "NL:KVK" to the Continia Delivery Network, the following validation error occured:
| 56769 |
Continia Delivery Network 24.01
Released: May 28, 2024
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | Introducing a new field in Customer Setup "Use Document Information for CustomerParty". When exporting a document, you now have the option to retrieve the Customer party details directly from the document rather than Customer. | 56588 |
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | When exporting electronic documents the VAT identifier of any party was taken from the VAT Registration No. field or any localized fields based on the localization of the Business Central. Now, this will be based on the country code of the party. | 53451 |
General Application | When exporting a Sales Invoice as an XRechnung document, the XRechnung version 3.0 will be used. | 54595 |
General Application | Several enhancements have been implemented for Peppol Payment Means functionality.
| 54780 |
General Application | When opening the Outgoing Network Documents page, the following error could occur:
| 55683 |
Continia Delivery Network 24.00.01
Released: May 1, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | The network identifier fields on the Customer Setup page were disabled and no values were shown. | 54404 |
Continia Delivery Network 24.00
Released: April 2, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an OIOUBL Service Invoice and Credit Memo the following error occurred for text lines:
| 53952 |
Continia Delivery Network 6.02
Released: March 7, 2024
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | Added support for onboarding companies, sending and receiving electronic documents throught the PEPPOL eDelivery Network via Continia Delivery Network for the following countries: Netherlands, Australia, New Zeeland. When the localization of the Business Central is set to Netherlands, Australia or New Zeeland all company information and documents will be stored in a separate datacenter according to the local regulations. | 53318 |
Continia Delivery Network 6.01.03
Released: February 12, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | A delivery codeunit for reminders has been created in order to support sending reminders through the Continia Delivery Network. | 53281 |
Continia Delivery Network 6.01.02
Released: February 1, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | A rounding error could occur on XML node LineExtensionAmount when exporting a document with Prices Incl. VAT set to true. | 52601 |
General Application | When opening the CDN Customer Setup Page without a VAT Registration No. the following error occurred:
| 52933 |
Continia Delivery Network 6.01.01
Released: January 20, 2024
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When trying to send an reminder the following error occurred:
| 52403 |
Continia Delivery Network 6.01
Released: December 15, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
The Action "Open Source Document" on Outgoing Network Documents now supports Service Invoices and Credit Memos. | 51678 | |
General Application | When exporting an PEPPOL,OIOUBL or XRechnung electronic documents and the document line had the Type G/L Account, cbc:Description node will not be created. | 50216 |
General Application | When exporting an OIOUBL Service Invoice/Credit Memo the following error occurred, when having the same extension fields with the same ID and different type:
| 51462 |
Continia Delivery Network 6.00, hotfix 2
Released: November 20, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When trying to create an Electronic Document, the following error could occur:
| 51206 |
Continia Delivery Network 6.00, hotfix 1
Released: November 9, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an OIOUBL document with a text line, a item line with standard VAT and a item line without VAT the following error occurred:
| 50849 |
General Application | In some cases, when sending an electronic document, the following error could occur:
| 50892 |
General Application | When creating an XRechnung document in the Continia Demo Portal, the following error could occur:
| 50950 |
Continia Delivery Network 6.00
Released: October 2, 2023
New or changed functionality
Functional area | Description | ID |
---|---|---|
Country and Regional | When exporting an OIOUBL document, the AccountCustomerParty/cac:Contact node will be populated with contact information from the following fields, listed in order of priority:
| 46473 |
General Application | The codeunits exporting the XRechnung documents were using an extended version of the XRechnung version. Now the codeunits use the latest version of the simple XRechnung version 2.3. Furthermore, the code will automatically find and use the latest version of the XRechnung that best matches the document receiver and the Continia Delivery Network participation. Therefore we recommend adding all the different versions of the XRechnung format to the existing participation. In the cases where a match is not found, the following error will be thrown:
| 41716 |
General Application | When exporting an OIOUBL XML document the following error occurred if the bank account number exceeded 10 characters.
| 42808 |
General Application | Outgoing Network Documents cues has been added to the Document Output Rolecenter. | 42897 |
General Application | When the Continia Delivery Network Customer Setup record is being inserted, if the field Use GLN in Electronic Document from the standard Microsoft OIOUBL extension is set to true then Receiver Type is set to GLN and Use GLN for Party and Legal Identification is set to true. | 43079 |
General Application | When exporting an OIOUBL document the maximum allowed decimals have been set to follow the schematron rules for OIOUBL. | 46745 |
General Application | When selecting the ZugFerd Outputprofile on Document Output Customer Setup List the Cross Industry Invoice Version is set to ZUGFeRD/Factur-X | 49139 |
General Application | Output profiles ZUGFeRD, OIOUBL, PEPPOL and XRECHNUNG are now prepared to support more document types, than the ones possible to send in the specific format. This means that the profile can generate the XML where possible, and send emails for the remaining template types. There should be no need for further configuration than adding the Output profile to the Document Output Customer List. | 49140 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | New field Enabled on Participation ID Type. Network Profiles and Participation ID Types with Enabled = TRUE will now be hidden all across Continia Delivery Network. | 31671 |
General Application | When exporting an OIOUBL XML Document using IBAN as the PaymentMeans the FinancialInstitution node was not created. | 43162 |
General Application | All validation codeunits have been updated to follow the latest XML ruleset in order to reduce the risk of non-compliant XML documents. | 43773 |
General Application | When sending more than 100 documents at a time, while opening the Outgoing Network Documents page, only the status of the first 100 documents was updated. | 44530 |
General Application | When exporting an OIOUBL document, the following validation error occurred if a line had no Unit of Measure Code.
| 46040 |
General Application | In some cases, a document received from Continia Delivery Network was created twice, this was causing the document to always be present in the Documents for Import even though the document was already imported. Additionally, when importing documents, only the first document imported would be marked as processed by Document Capture. | 46297 |
General Application | When running the Continia Delivery Network onboarding wizard, if the Country/Region Code exceeds 4 characters the following message will be displayed and the Country/Region Code will copy the first 4 characters.
| 46342 |
General Application | When registering for a participation for Nemhandel, without a mandatory profile, the following error was thrown.
| 46746 |
General Application | When activating Use GLN from document on the CDN Customer Setup page, the field GLN from the document is now used when exporting the invoice as the recipient of the document. This field is part of the standard Business Central OIOUBL extension app, and will only be used when the extension is installed. | 47003 |
General Application | The export of an OIOUBL document was not taking into consideration the Profile ID specified for the customer in the field OIOUBL Process ID on the page CDN Customer Setup. | 47380 |
General Application | When exporting an XML Document a blank line was exported if line Type was comment, Number had a value but Description was blank. | 47395 |
General Application | When exporting an OIOUBL document, the following error occurred if Sell-to Contact Name, exceeded 20 characters.
| 47630 |
General Application | When exporting an PEPPOL document, if the document was with Prices Incl. VAT. The Line Discount Amount was rounded which could result in the following validation error:
| 47966 |
General Application | When exporting PEPPOL or XRechnung electronic documents, where the Bill-to Customer was different from the Sell-to Customer, the information in the Accounting Customer Party section was filled in with the Sell-to Customer, and a new Payee Party section was created for the Bill-to Customer information. This was against the PEPPOL and XRechnung rules, as the Payee Party section should contain information about the Payment Receiver. A new field Use Sell-to Customer is created on the CDN Customer Setup page, which can be used to force the use of Sell-to Customer information in the Accounting Customer Party. The field is hidden by default. | 48078 |
General Application | When exporting an XML document, the following error occurred:
| 48127 |
General Application | After creating a test system as a copy of the production system having Continia Delivery Network participations, when pressing on any of the tiles or the Import files action on the Document Capture rolle center, the following error occurred:
| 49530 |
Continia Delivery Network 5.02, hotfix 1
Released: September 18, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
Country and Regional | When sending a PEPPOL document from or to a company with a SIRET number defined, this will now be used for the Party Identification node. | 49463 |
General Application | After creating a test system as a copy of the production system having Continia Delivery Network participations, when pressing on any of the tiles or the Import files action on the Document Capture rolle center, the following error occurred:
| 49530 |
Continia Delivery Network 5.02
Released: August 28, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an XML Document a blank line was exported if line Type was comment, Number had a value but Description was blank. | 47395 |
General Application | When exporting an OIOUBL document, the following error occurred if Sell-to Contact Name, exceeded 20 characters.
| 47630 |
General Application | When exporting an PEPPOL document, if the document was with Prices Incl. VAT. The Line Discount Amount was rounded which could result in the following validation error:
| 47966 |
General Application | When exporting PEPPOL or XRechnung electronic documents, where the Bill-to Customer was different from the Sell-to Customer, the information in the Accounting Customer Party section was filled in with the Sell-to Customer, and a new Payee Party section was created for the Bill-to Customer information. This was against the PEPPOL and XRechnung rules, as the Payee Party section should contain information about the Payment Receiver. A new field Use Sell-to Customer is created on the CDN Customer Setup page, which can be used to force the use of Sell-to Customer information in the Accounting Customer Party. The field is hidden by default. | 48078 |
General Application | When exporting an XML document, the following error occurred:
| 48127 |
Continia Delivery Network 5.01.04
Released: August 15, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | During the export of electronic PEPPOL or XRechnung documents where Bill-to Customer was different from Sell-to Customer, the information in the Accounting Customer Party section was filled with the Sell-to Customer data, and a new Payee Party section was created for the Bill-to Customer information. This was against PEPPOL and XRechnung rules, as the Payee Party section should contain information about the payment receiver. | 48843 |
Continia Delivery Network 5.01.03
Released: July 17, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When an XML document was exported, the following error occurred:
| 48127 |
Continia Delivery Network 5.01.02
Released: June 29, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When a PEPPOL document was exported, if the document was with Prices Incl. VAT, the Line Discount Amount was rounded, which could result in the following validation error:
| 47966 |
Continia Delivery Network 5.01.01
Released: June 9, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an OIOUBL document, the following error occurred if Sell-to Contact Name exceeded 20 characters.
| 47630 |
Continia Delivery Network 5.01
Released: June 2, 2023
New or changed functionality
Functional area | Description | ID |
---|---|---|
Country and Regional | When exporting an OIOUBL document, the AccountCustomerParty/cac:Contact node will be populated with contact information from the following fields, listed in order of priority:
| 46473 |
General Application | When exporting an OIOUBL XML document the following error occurred if the bank account number exceeded 10 characters.
| 42808 |
General Application | When the Continia Delivery Network Customer Setup record is being inserted, if the field Use GLN in Electronic Document from the standard Microsoft OIOUBL extension is set to true then Receiver Type is set to GLN and Use GLN for Party and Legal Identification is set to true. | 43079 |
General Application | When exporting an OIOUBL document the maximum allowed decimals have been set to follow the schematron rules for OIOUBL. | 46745 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When exporting an OIOUBL XML Document using IBAN as the PaymentMeans the FinancialInstitution node was not created. | 43162 |
General Application | All validation codeunits have been updated to follow the latest XML ruleset in order to reduce the risk of non-compliant XML documents. | 43773 |
General Application | When sending more than 100 documents at a time, while opening the Outgoing Network Documents page, only the status of the first 100 documents was updated. | 44530 |
General Application | When exporting an OIOUBL document, the following validation error occurred if a line had no Unit of Measure Code.
| 46040 |
General Application | In some cases, a document received from Continia Delivery Network was created twice, this was causing the document to always be present in the Documents for Import even though the document was already imported. Additionally, when importing documents, only the first document imported would be marked as processed by Document Capture. | 46297 |
General Application | When running the Continia Delivery Network onboarding wizard, if the Country/Region Code exceeds 4 characters the following message will be displayed and the Country/Region Code will copy the first 4 characters.
| 46342 |
General Application | When registering for a participation for Nemhandel, without a mandatory profile, the following error was thrown.
| 46746 |
General Application | When activating Use GLN from document on the CDN Customer Setup page, the field GLN from the document is now used when exporting the invoice as the recipient of the document. This field is part of the standard Business Central OIOUBL extension app, and will only be used when the extension is installed. | 47003 |
General Application | The export of an OIOUBL document was not taking into consideration the Profile ID specified for the customer in the field OIOUBL Process ID on the page CDN Customer Setup. | 47380 |
Continia Delivery Network 5.00.01
Released: May 22, 2023
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | The export of an OIOUBL document was not taking into consideration the profile ID specified for the customer in the field OIOUBL Process ID on the page CDN Customer Setup. | 47380 |
Continia Delivery Network 5.00
Released: April 1, 2023
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | On the Network Documents list, a new action, Mark as Processed, has been added. When running the function, the network document will be set to unprocessed and can be imported again into the document journal. | 28156 |
General Application | For OIOUBL Documents export codeunits have been added for Service Invoice and Service Credit Memos. | 32878 |
General Application | Added support for exporting of ZUGFeRD Electronic documents. | 32888 |
General Application | In the "CDN Customer Setup Card" a new boolean field "PEPPOL use GLN for Party and Legal identification" has been added. Enabling this field will prioritize using GLN instead of VAT Registration No. for Customer Party Identification and Customer Party Legal Identification nodes. | 34627 |
General Application | When exporting an OIOUBL document. Payment Means Due Date will now be populated with the due date from the invoice. | 40202 |
General Application | When exporting an OIOUBL document, the profile will change depending on how the receiver is registered. If the receiver is registered with the profiles Procurement-BilSim and NES5, the Procurement-BilSim profile will be chosen. If the receiver is only registered with the NES5 profile, this profile will be chosen. | 42453 |
General Application | New field on CDN Customer Setup <Use GLN from document>. This makes it possible for Danish localizations to use <EAN> on the document as receiver endpoint ID. | 42724 |
General Application | Events have been added to the solution. For details, please see Event Publishers for Continia Delivery Network 5.00 | 42861 |
General Application | Improved user experience of the CDN Customer Setup Page.
| 43201 |
Bug fixes
Functional area | Description | ID |
---|---|---|
When exporting a PEPPOL document the Belgian enterprise number was not stated in the correct format. | 38857 | |
General Application | When setting up the participation for an E-Document Setup, you can now only select participations with a minimum of a Network Profile with the Direction Outbound or Both. | 31529 |
General Application | When onboarding a participation, it's now possible to register in the PEPPOL network and the NemHandel network at the same time. | 39996 |
General Application | The following Event Publisher in Codeunit 6086271 CTS-CDN OIOUBL Export Inv. has been marked as obsolete as the XmlDoc parameter is not a VAR parameter:
| 40920 |
General Application | Continia Delivery Network now supports the new "Item Reference" table introduced as a feature in Business Central 2020 Release Wave 2. | 41710 |
General Application | It was posible to create an oboarding with a network profile having the Profile Direction as Both, even though Document Capture was not installed. Now the following error is thrown:
| 41889 |
General Application | When exporting an OIOUBL document, the validation of the document failed because two or more Tax Categories with the same VAT percentage were present. | 41922 |
General Application | When exporting an OIOUBL document, the validation of the document was failing because the InstructionID node was exported without a value. | 42018 |
General Application | When exporting an XML document text lines with spaces in the description will be skipped. | 42632 |
General Application | When trying to create an OIOUBL Electronic document in a Sandbox environment, the following error occurred:
| 42809 |
General Application | The Output Profiles for reminders were not created when running the Document Output Setup Wizard. | 43480 |
General Application | When exporting an OIOUBL Document where the <Qty. per Unit of Measure> on the line had a value between 0 and 1, for example, 0.2, the PriceAmount node was not calculated correctly. | 43496 |
General Application | In the CDN Customer Setup page, the Sender ID and in the E-Document Setup page, the Receiver ID value will now be filled with information from localized fields, for example, Enterprise No. for Belgium. | 43768 |
General Application | When exporting an OIOUBL Credit Memo and using the following event OnBeforeSkipDocumentLine, the FromCodeunit parameter had the wrong value 6086240 ("CTS-CDN PEPPOL BIS3 Inv."). This has been corrected to 6086272 ("CTS-CDN OIOUBL Export Cr."). | 44664 |
General Application | For Sender and Receiver with Swedish the country-specific prefix 'SE' and the suffix '01' are now removed when exporting a PEPPOL document. | 45514 |
General Application | When exporting an OIOUBL document, the node DocumentTypeCode was not added inside the AdditionalDocumentReference element. | 45752 |
General Application | When exporting a PEPPOL, XRechung or OIOUBL document, item line nodes will be populated with Item Attributes, if the item contains any Item Attributes. The following nodes will be created
| 45862 |
General Application | ZUGFERD Output profiles were created with the value "PDF and XML (e-doc)" in the field E-mail, this has been corrected to the value "PDF". | 45867 |
General Application | When exporting an OIOUBL Document the order in which the data in the Contact section under AccountingCustomerParty is being exported has been changed to the following priority:
| 45875 |
Continia Delivery Network 4.03
Released: March 27, 2023
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | Events have been added to the solution. For details, please see Event Publishers for Continia Delivery Network 2022 R2 (4.00) | 43354 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | In the CDN Customer Setup page, the Sender ID and in the E-Document Setup page, the Receiver ID value will now be filled with information from localized fields, for example, Enterprise No. for Belgium. | 43768 |
General Application | When exporting an OIOUBL Credit Memo and using the following event OnBeforeSkipDocumentLine, the FromCodeunit parameter had the wrong value 6086240 ("CTS-CDN PEPPOL BIS3 Inv."). This has been corrected to 6086272 ("CTS-CDN OIOUBL Export Cr."). | 44664 |
Continia Delivery Network 4.02
Released: January 2, 2023
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | Added support for exporting of ZUGFeRD Electronic documents. | 32888 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | The Output Profile for reminders was not created when running the Document Output Setup Wizard. | 43480 |
General Application | When exporting an OIOUBL Document where the <Qty. per Unit of Measure> on the line had a value between 0 and 1, for example, 0.2, the PriceAmount node was not calculated correctly. | 43496 |
Continia Delivery Network 4.01
Released: December 12, 2022
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | On the Network Documents list, a new action, Mark as Processed, has been added. When running the function, the network document will be set to unprocessed and can be imported again into the document journal. | 28156 |
General Application | In the "CDN Customer Setup Card" a new boolean field "PEPPOL use GLN for Party and Legal identification" has been added. Enabling this field will prioritize using GLN instead of VAT Registration No. for Customer Party Identification and Customer Party Legal Identification nodes. | 34627 |
General Application | When exporting an OIOUBL document. Payment Means Due Date will now be populated with the due date from the invoice. | 40202 |
General Application | When exporting an OIOUBL document, the profile will change depending on how the receiver is registered. If the receiver is registered with the profiles Procurement-BilSim and NES5, the Procurement-BilSim profile will be chosen. If the receiver is only registered with the NES5 profile, this profile will be chosen. | 42453 |
General Application | Events have been added to the solution. For details, please see Event Publishers for Continia Delivery Network 2022 R2 (4.00) | 42861 |
Bug fixes
Functional area | Description | ID |
---|---|---|
When exporting a PEPPOL document the Belgian enterprise number was not stated in the correct format. | 38857 | |
General Application | When setting up the participation for an E-Document Setup, you can now only select participations with a minimum of a Network Profile with the Direction Outbound or Both. | 31529 |
General Application | When onboarding a participation, it's now possible to register in the PEPPOL network and the NemHandel network at the same time. | 39996 |
General Application | The following Event Publisher in Codeunit 6086271 CTS-CDN OIOUBL Export Inv. has been marked as obsolete as the XmlDoc parameter is not a VAR parameter:
| 40920 |
General Application | Continia Delivery Network now supports the new "Item Reference" table introduced as a feature in Business Central 2020 Release Wave 2. | 41710 |
General Application | Automatic generation of output profiles, for OIOUBL, were wrongly generated with the description "PEPPOL". This description has been changed to OIOUBL. | 41834 |
General Application | It was posible to create an oboarding with a network profile having the Profile Direction as Both, even though Document Capture was not installed. Now the following error is thrown:
| 41889 |
General Application | When exporting an OIOUBL document, the validation of the document failed because two or more Tax Categories with the same VAT percentage were present. | 41922 |
General Application | When exporting an OIOUBL document, the validation of the document was failing because the InstructionID node was exported without a value. | 42018 |
General Application | When exporting an XML document text lines with spaces in the description will be skipped. | 42632 |
General Application | When trying to create an OIOUBL Electronic document in a Sandbox environment, the following error occurred:
| 42809 |
Continia Delivery Network 4.00
Released: October 1, 2022
New or changed functionality
Functional area | Description | ID |
---|---|---|
General Application | Support added for exporting documents in the A-NZ PEPPOL BIS 3 format. | 31752 |
General Application | New events have been added to the solution. Find them in the article Event Publishers for Continia Delivery Network 2022 R2 (4.00). | 32149 |
General Application | It is now possible to export OIOUBL reminders. | 32880 |
General Application | Support added for exporting documents in the Netherlands PEPPOL BIS 3 format. | 32884 |
General Application | When sending an OIOUBL document via NemHandel network, the validation of the document failed because ContactID is mandatory for OIOUBL documents. The code now populates the ContactID with the Salesperson Code from the Invoice/Credit Memo. | 34768 |
General Application | When sending an OIOUBL document to a receiver with a GLN identifier, the document was failing the validation with the following error messages: "[F-LIB196] schemeID = DK:SE, CompanyID must be a valid SE number (like 'DK12345678', value found: '1234567890123')" "[F-LIB190] schemeID = DK:CVR, CompanyID must be a valid CVR number (like 'DK12345678', value found: '1234567890123')" | 34770 |
General Application | The following events have been removed from the solution: Codeunit 6086240 CTS-CDN PEPPOL BIS3 Inv.
| 41228 |
Bug fixes
Functional area | Description | ID |
---|---|---|
For PEPPOL Service Invoice and Service Credit Memo cbc:BuyerReference is now populated in the following order:
| 32052 | |
When exporting an OIOUBL Credit Memo the text lines had 0 in CreditedQuantity. | 34368 | |
General Application | For PEPPOL documents, when Bill-To Customer is different from Sell-To Customer the PayeeParty Node will now be added. | 31062 |
General Application | When exporting an OIOUBL document having a line with 0 in quantity the following error occurred:
| 31359 |
General Application | Added a new action to Incoming Document List page - "Set Document to Processed". This action allows the user to mark a document as Processed, preventing the document to be imported again. | 31511 |
General Application | It is now possible to further customise the export of electronic documents by pressing the Additional setup action from the Continia Delivery Network subpart in the Document Output Customer Setup page. On this page you can choose a custom ProfileID to be used when sending the document in the Continia Delivery Network (for example NES5 for OIOUBL). | 31854 |
General Application | When exporting a PEPPOL document from a Swedish sender company, the value at the XML path "Invoice/AccountingSupplierParty/PartyTaxScheme/CompanyID" was not formatted according to the PEPPOL validation rules. | 31855 |
General Application | When exporting PEPPOL or XRechnung, documents following only the following type of lines are not exported:
| 31871 |
General Application | When sending a PEPPOL or XRechnung Service Invoice or Credit Memo the following transferfields error occured:
| 31919 |
General Application | When exporting OIOUBL documents the Delivery nodes DeliveryActualDeliveryDate and DeliveryActualDeliveryTime are renamed: From
| 32876 |
General Application | When exporting OIOUBL documents the following error occurred:
| 34743 |
General Application | When exporting PEPPOL or XRechnung documents, Delivery node will not be exported if the required values are not present. | 34809 |
General Application | When exporting an OIOUBL Document, the EndpointID for VAT No. did not contain the prefix DK. | 38466 |
General Application | When exporting OIOUBL or PEPPOL documents, empty lines with a space in description will be skipped when exporting. | 39644 |
General Application | When exporting OIOUBL documents, it's now possible to use the OnSetPaymentMeans Event Publisher to specify the FIK payment details. | 39680 |
General Application | When exporting OIOUBL & PEPPOL documents the following error occurred in some situations:
| 40565 |
General Application | When exporting an PEPPOL document where either the customer or supplier was Belgian the following validation error occured:
| 41371 |
General Application | When exporting OIOUBL documents, the validation for PartyIdentification was failing, when customers VAT number did not have a value. | 41543 |
Continia Delivery Network 3.01
Released: April 1, 2022
New or changed features
Functional area | Description | ID |
---|---|---|
General Application | Events have been added to the solution. For details, refer to Event Publishers for Continia Delivery Network 2022 R1 (3.00) on Continia Docs. | 32149 |
Bug fixes
Functional area | Description | ID |
---|---|---|
For PEPPOL Service Invoice and Service Credit Memo cbc:BuyerReference is now populated in the following order
| 32052 | |
General Application | When exporting an OIOUBL document with a line with 0 in quantity the following error occurred:
| 31359 |
General Application | Added a new action to Incoming Document List page - "Set Document to Processed". This actions allows the user to mark a document as Processed, preventing the document to be imported again. | 31511 |
General Application | When exporting a PEPPOL document from a Swedish sender company, the value at the XML path "Invoice/AccountingSupplierParty/PartyTaxScheme/CompanyID" was not formatted according to the PEPPOL validation rules. | 31855 |
General Application | When exporting PEPPOL or XRechnung, documents following only the following type of lines are not exported:
| 31871 |
General Application | When sending a PEPPOL or XRechnung Service Invoice or Credit Memo the following transferfields error occured.
| 31919 |
General Application | When opening the Customer Setup page, if the E-Document Setup Code was not the same as Output Profile Code, the following error occurred:
| 31995 |
Continia Delivery Network 2.03
Released: February 4, 2022
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | When sending a PEPPOL document with positive quantity and negative line amount, or the opposite, the validation was failing. | 30191 |
General Application | When sending a PEPPOL document with 0 quantity, the validation was failing. | 30390 |
General Application | When sending a PEPPOL document with an item which contained an GTIN number the validation was failing. | 30501 |
General Application | Added support for exporting OIOUBL electronic documents. | 30562 |
General Application | When sending a PEPPOL document with a VAT Posting Group or Bus. Posting Group longer than 10 characters, the following error occurred:
| 30762 |
General Application | When sending a PEPPOL Invoice where the total invoice amount is 0, the validation of the PEPPOL document was failing because the PayableAmount element was not created. | 30953 |
Platform and Technology | Events have been added to the solution. For details, please see Event Publishers for Continia Delivery Network 2021 R2 (2.00) | 30840 |
Continia Delivery Network 2.02
Released: November 30, 2021
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | Empty lines (Lines with no Type, Description nor Quantity) are now skipped by default when exporting a PEPPOL or XRechnung electronic document. The following event OnBeforeSkipDocumentLine in Codeunit 6086234 "CTS-CDN Export Mgt." was introduced so that this logic can be further customised. | 26208 |
General Application | When trying to onboard a participation in Continia Delivery Network only for sending PEPPOL or XRechnung documents, the Onboarding wizard will indicate that the participation already exists in the PEPPOL network, even though is it only required to be registered in the PEPPOL network when receiving documents. | 28581 |
General Application | Improved the pages Network Documents and Outgoing Network Documents. | 28833 |
General Application | External Document No. and Order No. will now be set inside OrderReference on all PEPPOL exports. Event publisher created with handle pattern for all PEPPOL export codeunits.
| 29470 |
General Application | When finding the customer or company identifier based on the localization of the Continia Delivery Network, the system was not taking in consideration the country of the customer or company. | 29548 |
General Application | When running the Document Output wizard, the following error was thrown:
| 29579 |
General Application | Removed check on Ship-To information on Credit Memos and Return Orders for XRechnung Exports. | 29620 |
General Application | The validation of XRechnung documents failed because of a missing Line Feed at the end of the Payment Terms description. | 29702 |
General Application | The amount in the path Invoice/InvoiceLine/Price/PriceAmount was rounded. This is not a requirement for PEPPOL documents. | 29729 |
Platform and Technology | Obsolete Publisher Function for all CDN Exports.
| 29508 |
Continia Delivery Network 2.01
Released: October 4, 2021
New or changed functionality
Functional area | Description | ID |
---|---|---|
Platform and Technology | The following events are added to the solution: OnBeforeValidate
| 24692 |
Platform and Technology | The following event is added to the solution: OnAfterGetReceiverInfo
| 27940 |
Bug fixes
Functional area | Description | ID |
---|---|---|
General Application | In some cases when sending an electronic document via Continia Delivery Network the following error was thrown:
| 27171 |
General Application | When running the system first with DEMO credentials, 4 temporary Network Profiles are created. After changing to Production Credentials, when sending an electronic document the following error was thrown:
| 27436 |
General Application | When not choosing to create the Output Profiles for Service documents in the Document Output Setup Wizard, the following error was thrown
| 27727 |
General Application | When sending an electronic document where the Receiver Identifier was empty on the Customer Setup, the following was thrown:
| 27808 |
General Application | When choosing the VAT option in Receiver Type on Customer Setup page, the Receiver ID Type was empty. When choosing the VAT option in Sender Type on E-Document Setup page, the Sender ID Type was empty. | 27822 |
General Application | When creating a PEPPOL document from a sales document without a Salesperson on, the following error occurred:
| 27929 |
General Application | When using Dynamics NAV 2015 version, the Continia Delivery Network Onboarding Wizard was not showing any instructional text. | 28084 |