History¶
Including all features, bugs and fixes released up until 3.2025.3.1
Features¶
This section contains a table that lists the features that were included in our releases. This article will be update with each release.
Release Version | ID | Title |
---|---|---|
- | 2654 | DMF export incremental on multi entity |
- | 2786 | Creation of new Classe for Importing Peppol E Invoice Romania |
- | 2894 | Azure File Share move file with same name |
- | 3105 | Babelway connector |
- | 2842 | “Is purchase order” and “Purch Id” validation on import |
3.2025.2.1 | 3096 | Queue UI and UE upgrades |
3.2025.2.1 | 3112 | Add printer specific text to outgoing labels |
3.2025.2.1 | 3114 | Add API authorisation type to include audience |
3.2025.1.4 | 2962 | Upgrade Queue UI en UE |
3.2025.1.4 | 2963 | Add more flexibility to the outbound configuration |
3.2025.1.4 | 3014 | Add external service smart connect option for label printing (e.g. BarTender integration) |
3.2025.1.4 | 2956 | Create business event when a message in the queue fails |
3.2025.1.4 | 2889 | Move certain variables to the connecter |
3.2024.9.1 | 2686 | DMF import did not run |
3.2024.8.7 | 2593 | EDI - Report license variable and pipeline update |
3.2024.4.1 | 2307 | Extension issues on data processors |
3.2024.4.1 | 2314 | DMF entity name on export too short |
3.2024.11.6 | 2809 | Readsoft connecter |
3.2024.10.5 | 2767 | AS2 protocol |
2022 | 2548 | FTP/SFTP connector |
-2146826246 | 2359 | DMF export no staging computed column empty file |
-2146826246 | 2579 | NANVendTable and NANCustTable DeleteAction |
Bugs & Fixes¶
This section contains a table that lists the bugs and fixes that were included in our releases. This article will be updated with each release.
Release Version | ID | Title |
---|---|---|
2904 | Import UBL object not set to a reference | |
2957 | RO object not set to the instance of an object import (DMS) | |
3087 | File name bug for reprocessing processor using the NANHandlerInDMSUbl_RO handler (DMS) | |
3.2025.2.1 | 3092 | Label changes |
3.2025.2.1 | 3094 | Message content changes can not be saved |
3.2025.2.1 | 3101 | File not moved to FailDirectory of SuccessDirectory when using SAS Credential |
3.2025.2.1 | 3108 | API Connection failed on ER OUT processor |
3.2025.2.1 | 3109 | Authorization types (API, Storage account, …) Not cleared when changing connector type |
3.2025.2.1 | 3120 | Parent Path Error when directory doesn’t exist (ER - OUT handler in combination with a Fileshare) |
3.2025.2.1 | 3122 | failed XML (import or export) can sometimes not be reprocessed |
3.2025.2.1 | 3133 | Label printing through processor not working from document routing |
3.2025.1.4 | 2965 | issues with the processors which were using the “Use Queue” parameter |
3.2025.1.4 | 2966 | 9A Smart Connect missing label for license report usage |
3.2025.1.4 | 3004 | Empty error message when error is thrown in event processing |
3.2025.1.4 | 3037 | Strange behaviour when DMF import |
3.2025.1.4 | 3038 | When DMF import process message is in error in the queue, and the same processor is triggered, its runs infinitely |
3.2025.1.4 | 3048 | Auto Create directories if not exist in DMF export |
3.2025.1.4 | 3050 | When reprocess an failed DMF export message (non excel) The name of the export file is wrong |
3.2025.1.4 | 3052 | Filter on top of page is not working when a view is saved with another sort by column |
3.2025.1.4 | 3059 | File share SAS credentials fail on instantiation |
3.2025.1.4 | 2950 | Connector setup issue |
3.2024.12.1 | 2869 | Lookup on Connecter key vault value not working |
3.2024.12.1 | 2880 | Move to failure folder not working |
3.2024.11.6 | 2829 | Object reference not set to an object error |
3.2024.10.5 | 2733 | Dll update for version 41 |
Detailed Notes¶
This section contains the workitems mentioned in the above sections, with additional details and applicable notes
2894¶
- Title: Azure File Share move file with same name|
- Release:
- Type: User Story
- Notes When exporting or copying files to Azure file storage you may have a file that was previously processed with the same name and as such the system fails to copy or export the file
2904¶
- Title: Import UBL object not set to a reference|
- Release:
- Type: Bug
- Notes When importing an invoice where there is no ID for the OrderReference the ID is therefore null causing the error. Check if the ID on the OrderReference exists before reading the value.
3087¶
- Title: File name bug for reprocessing processor using the NANHandlerInDMSUbl_RO handler (DMS)|
- Release:
- Type: Bug
- Notes Now, when reprocessing a failed import with the processor using the NANHandlerInDMSSUbl_RO handler, the correct reference name is used.
2842¶
- Title: “Is purchase order” and “Purch Id” validation on import|
- Release:
- Type: User Story
- Notes If there is an order reference present in the invoice then set the IsPurchaseOrder to Yes. When importing with order references that do not exist as purchase orders then leave the field empty. Auto matching after import activated
3092¶
- Title: Label changes|
- Release: 3.2025.2.1
- Type: Bug
- Notes Some spelling mistakes are resolved.
3094¶
- Title: Message content changes can not be saved|
- Release: 3.2025.2.1
- Type: Bug
- Notes It is now possible to save changes made to message content in the queue.
3096¶
- Title: Queue UI and UE upgrades|
- Release: 3.2025.2.1
- Type: User Story
- Notes The standard view has been changed to display more relevant data.
3101¶
- Title: File not moved to FailDirectory of SuccessDirectory when using SAS Credential|
- Release: 3.2025.2.1
- Type: Bug
- Notes The bug when import from a fileshare while using SaS is fixed.
3108¶
- Title: API Connection failed on ER OUT processor|
- Release: 3.2025.2.1
- Type: Bug
- Notes The bug for ER OUT in combination with API connector is resolved.
3109¶
- Title: Authorization types (API, Storage account, …) Not cleared when changing connector type|
- Release: 3.2025.2.1
- Type: Bug
- Notes The connector is not taking unrelated columns into account to generate the displayed view.
3114¶
- Title: Add API authorisation type to include audience|
- Release: 3.2025.2.1
- Type: User Story
- Notes It is now possible to use an API connection that requires audience for authorisation.
3120¶
- Title: Parent Path Error when directory doesn’t exist (ER - OUT handler in combination with a Fileshare)|
- Release: 3.2025.2.1
- Type: Bug
- Notes This bug is resolved by creating the complete directory path on the fly (if it doesn’t already exist).
3122¶
- Title: failed XML (import or export) can sometimes not be reprocessed|
- Release: 3.2025.2.1
- Type: Bug
- Notes The issue that blocked the reprocessing has been resolved.
2962¶
- Title: Upgrade Queue UI en UE|
- Release: 3.2025.1.4
- Type: User Story
- Notes The queue UI and UE got an upgrade including:
- Standard queue lay out
- Multi select cancel option
- More filter functionality
- Better logging layout
2963¶
- Title: Add more flexibility to the outbound configuration|
- Release: 3.2025.1.4
- Type: User Story
- Notes There is added more flexibility to the outbound configuration:
On the processor it is now possible to select a business process, that business process is a trigger to place a record in the event table when certain conditions are met.
The event contains the record id and the table id of the created record, that reference can be used by the handler on the processor to create an export message. For now 4 business processes are added:- Sales order confirmation (custConfirmJourTable)
- Packing slip creation (custPackingSlipJourTable)
- Sales invoice creation (custInvoiceJourTable)
- Purchase order confirmation (vendPurchOrderJourTable)
There are multiple condition that can be added to trigger, for each customer or vendor it is possible to ‘activate’ the processor by adding a relation between the customer/vendor and the processor, next to that a relation can be made between customer/vendor group and the processor. The processor can also be default on for all vendors/client by setting the Enable for all accounts parameter to yes.
More information will be provided in the manual.
2965¶
- Title: issues with the processors which were using the “Use Queue” parameter|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bug is fixed where in some cases the queue parameter was automatically set to No while Yes was needed.
2966¶
- Title: 9A Smart Connect missing label for license report usage|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bug where some labels were missing for license report usage is fixed
3004¶
- Title: Empty error message when error is thrown in event processing|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bug is fixed where empty error messages was thrown in the event processing.
3014¶
- Title: Add external service smart connect option for label printing (e.g. BarTender integration)|
- Release: 3.2025.1.4
- Type: User Story
- Notes The standard external service instance has been extended with a processor field.
This makes it possible to send labels (custom labels, document routing labels, wave labels) to a connector (e.g. Fileshare, Blob, Container, … ).
This makes it possible to send labels to on premise label processors (e.g. bartender).
Needed setup:- Create a processor that will process the labels
- Use the NANHandlerOutDR handler
- Fill in the variable information on the processor that is linked to the selected connector
- Create an external service definition
- Create an external service operations
- The http information is not relevant
- As ‘request body type’ select Raw
- As request body (raw)
- select content type plain/text
- request body = \(label.body\)
- For ZPL labels and variable script labels, fill in the previously created service in the print operation en the variables print operation field of the definition
- For Variables tables the script needs to be filled in.
- Create an external service instance
- Add the previously created definition to the instance
- Add the previously created processor the the instance
- The other information doesn’t need to be filled in
- Create a label printer
- Select connection type = External label service
- Select as Label print service instance the previously created external service definition
3037¶
- Title: Strange behaviour when DMF import|
- Release: 3.2025.1.4
- Type: Bug
- Notes The strange behaviour when performing the DMF import is fixed:
- Files are moved to the correct folder
- On failed, the state in the queue is changed to Error
3038¶
- Title: When DMF import process message is in error in the queue, and the same processor is triggered, its runs infinitely|
- Release: 3.2025.1.4
- Type: Bug
- Notes This bug is fixed.
Note:
Using the queue in combination with DMF import/export of excel files is not possible.
3048¶
- Title: Auto Create directories if not exist in DMF export|
- Release: 3.2025.1.4
- Type: Bug
- Notes When a directory is specified in the directory path of the processor that doesn’t exist, it is now created on the fly.
3050¶
- Title: When reprocess an failed DMF export message (non excel) The name of the export file is wrong|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bug where the name of the export file on reprocessing a failed DMF export record in the queue was wrong is solved.
3052¶
- Title: Filter on top of page is not working when a view is saved with another sort by column|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bugs with the filter on top of the page are solved.
3059¶
- Title: File share SAS credentials fail on instantiation|
- Release: 3.2025.1.4
- Type: Bug
- Notes The bug that SAS credentials fails on instantiation for a fileshare is solved.
2950¶
- Title: Connector setup issue|
- Release: 3.2025.1.4
- Type: Bug
- Notes When a the type of a connector is changed, the previously used credentials are now cleared from the connector table.
2956¶
- Title: Create business event when a message in the queue fails|
- Release: 3.2025.1.4
- Type: User Story
- Notes When a record in the queue fails to process (entering the error state), a business event can be send out. This business event can be picked up by a power automate, logic app, …
This makes it possible to send communication (email, teams message, etc.) to dedicated persons when the records fails to be processed in the queue.
Name of the business event: NANQueueErrorBusinessEvent
Fields included:- BusinessEventId
- BusinessEventLegalEntity
- EventTime
- Info
- Filename
- QueueId
- Direction
- BusinessEventId
2889¶
- Title: Move certain variables to the connecter|
- Release: 3.2025.1.4
- Type: User Story
- Notes Variables are very specific to certain connecters and handlers and as such have been split to the correct classes. This will ensure that no erroneous variables are created Azure file share requires directories
But an API does not require directories
2869¶
- Title: Lookup on Connecter key vault value not working|
- Release: 3.2024.12.1
- Type: Bug
- Notes When selecting ‘Use Keyvault’ in the parameters, the connection string field lookup was not applying the dropdown to the keyvalut values. Issue has been resolved
2880¶
- Title: Move to failure folder not working|
- Release: 3.2024.12.1
- Type: Bug
- Notes When importing files and there are failures the files are not moved to the failure folder, this issue has been resolved