Axcite modules
April 2025 release plan
What's new in Axcite's modules?
April 2025
This April release plan introduces new features to some of the Axcite modules and contains minor quality and performance updates.
New features and quality updates may be modified before release.
Version
This release is built on Dynamics 365 Supply Chain Management 10.0.41 and tested on 10.0.41, 10.0.42, 10.0.43.
Expected release: Late April.
New release
This April 2025 release introduces new and exciting functionality, bug fixes and quality updates.
Axcite Warehouse Management
#Tag counting for Warehouse automation systems
Adding functionality to support system counts in external warehouse management systems.
ID: 25961
#Entity for External Storage Setup
An entity has been created for the External Storage Setup table, enabling data creation and updates through the Excel plug-in or by importing files via Data Management.
ID: 26171
#More precise status handling of business events
Optimizing Business events status handling.
ID: 35993
Axcite EDI
#Delivery address validation and handling on inbound orders
This new feature has been introduced to support EDI Sales orders coming from B2C front-ends, i.e. webshops, in a better way. It is now possible to:
- Validate the delivery address components (address, zipcode, city and countrycode) on the specific EDI sales order.
- Search through the delivery addresses on the customer account to check whether the address already exists. If it does, it is used on the specific sales order.
- If the delivery address doesn't exists, create a new delivery address on the customer account and use it on the specific sales order.
- Validate the Mode of delivery against the support table and use it on the specific sales order.
- Transfer Service point ID to the corresponding field on the Sales order, if Axcite Transportation Management is installed.
ID: 22137
#Sorting at creation of BEDI sales lines
EDI Sales order lines in incoming direction are now sorted in the same ascending order as they are read from the incoming XML file. When the EDI Sales order are converted to a Sales order, the conversion is done according to the same sorting. The result is that the order of lines is the same in the incoming XML file, the EDI Sales order and the Sales order (after conversion).
ID: 22162
#Check for duplicates on incoming sales orders
A new general feature is introduced, allowing to check for duplicate records on incoming sales orders. If activated, the feature prevents conversion of an EDI Sales order with the same Document identification number, that has previously been converted for the same customer account. To prevent conversion, the previous sales order must:
- Have a sales order number in EDI Sales orders and be marked as Converted.
- Exist in Sales orders or in Voided sales orders.
- General causes for duplicates are:
- Customers sending an order more than once by mistake.
- External systems sending more than once by mistake or in case of outages/break down.
- Azure integration services sending more than once in case of outages/break down or updates in the back-end.
ID: 30102
#Correct Linereference in Sales packing slip
Linereference field in Sales packing slip line, has been changed to always show a unique reference.
This has become a requirement from the VANS provider.
ID: 30103
Axcite Invoice Workflow
#Bug fix: Error on purchase invoice with discount and penny diff
Handling error on purchase invoice with discount and penny diff
ID: 26303
#Bug fix: Pre-ledger posting on Fixed assets missing Book/type
Preledger posting on Fixed assets now defaults fixed asset type and book from selected fixed asset
ID: 26361
#Landed cost - vendor setup
Function added - if purchase order line is linked to a voyage, update requirement in invoice workflow is automatically set to None on the invoice line, regardless of settings in Vendor setup. This makes it possible to invoice update purchase order lines linked to a voyage (without receipt) and still require 3-way matching on purchase orders without voyages.
ID: 27926
#New Field PUR/COST
New Field - Showing the type of invoice.
ID: 29625
#PUR/COST in IWF APP
New filter possibility in Invoice approval, Invoice approval journal and in the Power app on Cost invoices and Purchase invoices.
ID: 30258
#Powerapp solution element prefixes
Changing the prefixes for the elements in the Power Platform solution for app AxciteInvoiceWorkflow.
ID: 35563
#Bug fix: Preledger posting låst
Fixing issue with changing financial account on posting proposal
ID: 36031
#Bug fix: Send mail - on approved invoices (partial approval)
Solving send email to approvers on approved invoices with preledger posting.
ID: 36088
Axcite Sales
#Fix ATP calculation if Sales order process is blocked in PLC state
Items that have a product lifecycle state in which sales order processes are blocked are now skipped in the periodic ATP calculation.
ID: 25787
#The parameter 'Use Axcite goods in transit' is removed
The parameter 'Use Axcite goods in transit' is removed along with the related functionality.
ID: 30014
Axcite Procurement
#Development of Kanban power app
Power app support for Axcite procurement kanban functionality.
ID: 23554
#Historical data in safety stock journal
A new parameter is added to include historical data when creating a safety stock journal.This means that historical transactions imported via data management can be used ot calculate safety stock levels.
ID: 26005
#Remove "item/supplier blocking" and "order quantity per supplier"
With this release, the functionalities "Item/Supplier blocking" and "Order quantity per supplier" have been discontinued. As a result, the corresponding setup forms (screen shots) have been removed along with any related functionality impacted by the setup.
ID: 30004
#Remove WHS validation in ASN import
Parameter in ASN import to conduct an extra validation on none-WHS items is removed.This means that there will no longer be an individual validation on whether the item is WHS enable or not.
ID: 30028
#Remove the parameter option to print the requested ship date on the standard purchase confirmation
Parameter to print the requested ship date on purchase order and purchase inquiry confirmation is removed, and this date is no longer printed on the standard confirmations.
ID: 30030
#Miscellaneous corrections in PAO
The field 'Replacement product' on product variants have been added to the detailed view.Several different labels and texts around the module have been renamed to reflect functionality.
ID: 35994
#Possibility to override ship calendar on purchase orders
The ship date calendar is now inherent from the vendor to purchase order lines. This makes it possible to change the ship date calendar on the individual lines in cases of for example urgent deliveries. An example could be that the vendor normally only ship goods every Friday, but you need the goods shipped as soon as possible. Changing the ship date calendar or just deleting it on the lines, makes it possible to ship on other days of the week.
The requested ship date on the lines will comply with the ship date calendar. The system will deduct the transport time from the requested receipt date and find the possible ship date.
ID: 35515
Axcite Transportation Management
#On packing slip posting initialize Mode of delivery and Delivery terms from WHS-Shipment
When using warehouse management processes and posting the packing slip from a WHS shipment, the "Mode of Delivery" field in the nShift booking section of the shipment dialog will be populated with values from the WHS shipment. The "Delivery Terms" field will be populated with values from the sales order line.
ID: 22272
#Phonenumber and mailaddress from customer account at shipment submitting
Two new fields, "Receiver E-mail" and "Receiver Phone", have been introduced on the customer record. The values from these fields will automatically transfer to the sales order.When a shipment is booked with the carrier, the values in these new fields on the sales order will be transferred to the carrier. If the fields on the sales order are blank, a fallback will apply, using the contact information configured on the customer record.
ID: 23396
#Correct booking address from WHS-shipment
When an nShift shipment is booked via a WHS shipment, the recipient address transferred to nShift is now taken from the WHS shipment instead of the sales order header.
ID: 30097
#nShift T&T change
T&T support has been improved to accommodate carriers that track shipments at the package level. Now, the system dynamically provides tracking links based on the carrier’s tracking method—either a single link for shipment-level tracking or multiple links for package-level tracking.
ID: 35559
#Service point ID on sales order
A new field on the Sales order header is added, allowing to store a unique identification of a certain Shipment service point ID/Drop box ID (in Danish "Pakkeshop ID"). The information is typically provided in a Sales order with origin from a webshop front end. It can also be entered manually. The unique ID can be used at shipping later in the process to identify the receiver/where to drop the shipment. This is not part of this development.
ID: 35572
Axcite Foundation
#Avoiding dublicate entries in Stages files
File stage service updated with feature to avoid duplicate entries.
ID: 34095
Any actions required?
Please attend to the Release Update Guide sent to you in an e-mail, to see if any actions is required when updating to this version.
Vi er specialister i Microsoft Dynamics 365 - og har Microsofts ord for det
Vi er certificeret Microsoft Partner Gold i Enterprise Ressource Planning. Det er din sikkerhed for, at du med os som partner, får professionelle og gennemtestede ERP-løsninger af høj kvalitet og sikkerhed.