Introduced the Configuration Package Excel API, enabling automated tools (such as PowerShell, Power Automate, or custom scripts) to import and apply Excel-based configuration packages in Business Central without manual intervention. This API is designed specifically for data migration automation, supporting the official RapidStart (Configuration Package) format and allowing for consistent, repeatable migration processes. You can read more about this here.
Advanced Project Management is enabled when you install it, and in each new company. Using its features needs an active subscription or trial. If you disable it, its fields and actions are hidden on standard pages such as the project card and project list, and standard Business Central works as if the app weren't installed. You can still view retention ledger entries, retention claim invoices, project purchase invoices and fixed asset cost entries.
Generate Demo Data action on Advanced Project Management Setup. In a sandbox, it creates the setup, customers, subcontractors, resources and seven construction projects with several months of progress claims, retentions, variations and WIP.
Restored compatibility with extensions that depend on Generic Workflow. Version 29.0.0.0 removed the Request Approval promoted action group from the Vendor Bank Account Card, which could break extensions that reference it. The group has been restored but is hidden and marked obsolete. The Send Approval Request, Cancel Approval Request and Revert Changes actions are still shown in the standard Request Approval group.
This version requires Business Central 2026 release wave 2 (version 29) or later.
The Vendor Bank Account Card now uses the standard Workflow Status FactBox and the standard Request Approval action group instead of adding its own, so they are not shown twice.
Added
Added the Hide Default Vendor Bank Account Approval Actions option to the Generic Workflow Setup page. Turn it on to hide the standard vendor bank account approval actions when Generic Workflow manages approvals for vendor bank accounts.
Fixed
Fixed approval requests getting stuck in Processing when sent by a delegated admin or helpdesk user. Notifications for these requests are now sent by the next run of the Notification Entry Dispatcher job queue entry.
Fixed a "The type is not supported." error when sending or cancelling an approval request while another workflow step was still processing.
Approval entries for vendor bank accounts are now filtered correctly when Generic Workflow is active for that table.
Added whole-unit and estimated-weight guidance to Advanced Move, based on the bin's average weight per unit. Registration and posting are unchanged. #104001
Changed
Extended the Enter Units step to Inventory Pick.
Fixed
Prevented picking more units than a license plate holds and corrected source units when picking part of a license plate. #94559
Suppressed standard missing-consumption and missing-output warnings during automatic production-order finishing; configured checks and manual finishing confirmations remain unchanged. #95693
Added Undo Pick with License Plate to reverse selected license plates for picking again. Undone quantities are excluded from packing slips; shipping less than picked now requires undoing the pick first. #101172
Added production output and reversal from the consumption screen, restricted to items on the selected production order. #108343
Added zone filtering to Bin Content and Locate Item, plus expiration-date sorting and clearer tracking details in Locate Item. #106304 #106295
Added posted document and originating order details to license plate entries for easier tracing. #99408
Added tote pallet printing from the mobile picking pallet selection list. #107627
Added configurable barcode quantity precision, decimal input, quantity display rounding and over-delivery warnings for planned functions. #100638
Changed
Enabled receiving shipped license plates on sales returns and removed the location setup requirement for receiving from existing license plates. #106286 #106481
Displayed external document numbers in Advanced Move and improved movement posting performance. #106609
Improved production consumption errors and added API and OData support for production-local time handling. #100965 #106636
Deprecated
Deprecated Receive from LP on locations; the setting no longer controls receiving from license plates. #106481
Removed
Removed duplicate standard Receive, Move and Unplanned Move mobile functions. #96107
Fixed
Prevented license plates that are not ready from being loaded onto trucks. #107610
Corrected shipment posting errors caused by partially shipped items on another warehouse shipment. #109166
Kept warehouse receipt posting within the caller's transaction. #107295
For variable-weight items, changing the units to ship or receive no longer resets the weight to the average weight, which overwrote valid weights on items with high tolerances. The weight is now only recalculated when it is outside the item's weight tolerance (0% always recalculates). Applies to sales, purchase and transfer orders, including returns; warehouse shipments and receipts are unchanged. #105362
Changing the weight to ship or receive no longer recalculates the units to ship or receive for variable-weight items. Enter the units first, then the weight. #105362
Fixed an issue where Units entered on Item Tracking Lines were lost or misallocated across reservation entries when tracking was first applied or updated. Units are now carried onto every related entry and distributed by quantity, with the final entry receiving any rounding remainder. #101380
Fixed sales line tolerance handling so weight deviations use the configured Units/Weight Tolerance and under-shipments preserve the ordered units. AB#100722
Fixed partial drop shipments posting the ordered units instead of the units actually received or shipped, for both purchase receipts and sales shipments. #91637
Fixed purchase and sales line pricing after item, unit of measure, Units, or Order Quantity changes, including zero costs from third-party tools using temporary purchase/sales orders to determine prices.
Fixed line quantities being cleared when changing the Order Unit of Measure before entering an order quantity, and when changing items on non-Dual UOM purchase lines.
Fixed an issue where units could become incorrect when transfer orders were partially shipped or received, with or without warehouse shipments and receipts. This includes lot-tracked items where only part of a lot is shipped or received. #106621, #99238
Fixed an issue posting a sales return receipt when the return order was processed without using Copy Document. #106216
Changed
Adjusted the app's over/under variance handling to account for Business Central's standard item-tracking adjustments when line quantities change. Tracking allocations are preserved during app-driven variance updates, while reservation behavior remains standard. If tracking no longer matches the quantity to handle, update it on Item Tracking Lines before posting #105869.
Handling units conversion and display mode procedures are now available to connector apps, so pages in other apps can show Handling Units the same way warehouse pages do.
Added
Added required and available Handling Units to the Sales Line FactBox, respecting the configured display mode #101864.
Sales lines created from EcpPro invoices now round the unit price to the standard Unit-Amount Rounding Precision (General Ledger Setup for local currency, or the Currency card for foreign currency). Previously the unit price was copied from EcpPro unrounded, so a unit price with more than 2 decimals could make the printed unit price × quantity differ from the line amount.
Added available units, total units and unit of measure to Locate Item results. #106295
Changed
Blocked Unplanned Move and Unplanned Move Advanced when units are missing for variable-ratio items. #98471
Fixed
Corrected source units when moving part of a license plate into a new one in Advanced Move, and prevented moving more units than the source holds. #101579
Corrected units posting for partial warehouse receipts with item tracking. #106621
Resolved an issue on Business Central 27.5 and later where resetting the Dataverse integration configuration could fail because the Dataverse table connection was not yet available when the Transaction integration table mapping was created. The reset now completes, and the mapping's existing filter is restored from the saved default mappings.
Added Create Demo Data to Consignment Setup in sandbox environments. The demo setup report is now included in the main app and requires a warning confirmation before changing setup or posting sample transactions. Runs outside sandboxes and background runs are blocked.
Changed
Made demo items selectable through an item filter and multi-select lookup, defaulting to the first four eligible items when the request page opens. Replaced fixed CRONUS/Contoso items, warehouse, and posting groups with company-based defaults and selectable vendor/customer setup.
First release of Consignment Inventory on the Microsoft Marketplace (AppSource)
Changed
The PTE (per-tenant) version of the app has been renamed to Consignment Inventory (PTE), so it can be installed alongside the Marketplace version during migration
The Marketplace version is a new app, separate from the PTE version. Existing customers can install it alongside Consignment Inventory (PTE) while their data is migrated. Please contact us to plan your migration.
New Show Sync All from Entra ID setting on Purchase Requisition Setup. The Sync All from Entra ID action on the Requesters page is now hidden unless this setting is turned on. Requesters can still be synchronised with Entra ID one at a time
New Status field (Active or Inactive) on Vendor Catalogue Items. Only Active catalogue items can be added to purchase request lines. Blocking a vendor sets all its catalogue items to Inactive, and unblocking it sets them back to Active. The Status is synchronised to the Vendor Catalogue Item Status in Dataverse, so the Portal can offer only Active items. Inactive items that have never been synchronised are not created in Dataverse
New Vendors and Requesters actions under Dataverse Records on Purchase Requisition Setup show the vendor accounts and the contacts in Dataverse, including whether each one is coupled to Business Central and its status. Every table this app synchronises with Dataverse now has a Dataverse Records page there
New Edit Lines in Excel action on the Purchase Request card opens the request's lines in Excel, where they can be changed and new lines added, and then published back to Business Central. New lines must have the request's number in the Document No. column. Lines can only be changed while the request is Open. Use the new Refresh action on the card to see the published changes
New Requester Cannot Receive field on Vendor Catalogue Items, to mark items that the requester is not allowed to receive. The field is synchronised to Dataverse so the Portal can use it
Changed
The portal invitation and Entra ID actions on the Requesters list and the Requester card have moved from Related to Actions, in a new Portal group that is also shown on the action bar
Blocking a vendor in Business Central now sets its vendor account in Dataverse to Inactive at the next synchronisation, and unblocking it sets the account back to Active, so the Portal can stop offering blocked vendors on new purchase requests. Previously a vendor stopped synchronising as soon as it was blocked and stayed Active in Dataverse. Blocked vendors that have never been synchronised are still not created in Dataverse
The e-mail sent to the requester when their purchase request is converted to a released Purchase Order now names the purchase request: its number is in the subject and the body, the body also shows its Justification/Purpose, and it links to the request on the Portal when a Portal URL is set up on Purchase Requisition Setup
When a purchase request uses a Ship-to Address copied from a Location, the Purchase Order created from it now gets that Location Code, and its lines default to it. For an address copied from a Responsibility Center, the order gets that Responsibility Center (and the Location Code set up on it). If the location requires warehouse receipts, receipts for those orders must be posted through the warehouse
The Purchase Requisition Job Log now records each purchase request converted by the Auto Convert PR to PO job, with the Purchase Order(s) created for it, and any error releasing those orders
Fixed
Use Default Synchronization Setup on the Integration Table Mappings page replaced the PRVENDOR, PRCURRENCY and PRPURCHASER mappings with Microsoft's standard vendor, currency and salesperson mappings. It now restores this app's own default setup for them
Deleting a requester that still has purchase requests (after confirming the warning) left the requester's number, name and e-mail on those purchase requests. They are now cleared again, as they were in 27.0.10.0
After a receipt was undone in Business Central, the Qty. Received on the purchase request line was not always updated in Dataverse, so the Portal still showed the quantity as received and would not let it be received again. The reduced quantity is now synchronised at the next synchronisation, for full and partial undos. The same applies to the Qty. Received after a partial receipt
The Auto Convert PR to PO job could convert the same purchase request again and again, creating a new Purchase Order each time. Business Central routinely works with temporary copies of purchase order lines (for example when calculating totals or printing the order), and removing such a copy was treated as if the real order line had been deleted, which sent the request line back to Released. Only deleting the real order line now reopens the request line
When the Auto Convert PR to PO job failed part-way through converting a purchase request, a Purchase Order with only a header and no lines could be left behind. A failed conversion by the job is now undone completely
The Auto Convert PR to PO job now releases the Purchase Orders only after they have been created. If releasing an order fails (for example because e-mailing it to the vendor needs user input, which a background job cannot give), the order is still kept with all its lines and the reason is shown in Last Posting Error on the request lines and in the Job Log. If the order did get released and only the vendor e-mail failed, the requester is still notified
When posting a receipt from a purchase request failed part-way, a posted receipt could be left behind while the Purchase Order still pointed to it, so every later attempt failed with "interrupted posting attempt". A failed receipt is now undone completely
Deprecated
The Process PO Receipts codeunit, the PO Receipt Transactions XMLport and the PO Receipt Temp table are marked obsolete and will be removed in a future release. Nothing in the app uses them: Portal receipts are posted from the purchase request lines by the Post Receipt job
The previous portal invitation and Entra ID actions under Related on the Requesters list and the Requester card are hidden and marked obsolete, and will be removed in a future release
One approval path can now be marked as the Escalation Path. When an approval set is worth more than the path it matched can authorise, the levels of the Escalation Path are added after the path's own levels (numbered on from the last one), so the request can still be approved instead of ending up Blocked. Mandatory levels of the original path stay part of the approval; its other levels that have not been opened yet are skipped, because the escalation approvers carry the authority. Without an Escalation Path, a request worth more than any level of its path can authorise is now rejected straight away, with the reason on the Approval Sets page, instead of being left Blocked after everyone had approved. The same happens if every level has been worked through and nobody with enough authority approved. The Approval Sets page shows which escalation path was used
Approval path levels have a new Unlimited Authority option for a level that may approve any amount. The Escalation Path must have at least one such level, and the app prevents you from removing the last one while the path is the Escalation Path
Added public consignment helper procedures and duty calculation events for extension use. #108392
Added additional public CreateAndAssignConsignment procedures for purchase and transfer orders. #108393
Added public consignment helper procedures to check whether a charge invoice is needed and assign item charges to purchase and transfer receipts.
Added the OnSelectConsignmentLinesForGetConsignmentLineOnAfterSetFilters integration event.
Added the OnReverseAllPredictedEntriesOnAfterSetFilter integration event so extensions can adjust which predicted entries are reversed.
Changed
Duty recalculation now respects message suppression, avoiding unnecessary messages during background processing. #108392
The Generate Demo Data request page now shows the Location Code the purchase orders will be received at, so you can choose another location before any data is created. Choosing a location sets Location Type to match how that location receives. See Creating Demo Data.
Demo data now creates the duty item charge as LC-DUTY (Import Duty) with Default Assignment Method set to Duty, replacing LC-SPECIAL. The Import Duty template line now has a nominal amount of 100, so duty is calculated on the demo orders.
Demo data now creates a set of example duty rates for LC-DUTY: rates by item category (chairs, tables, coffee makers, espresso machines and parts), item rates for items classified differently from their category, higher rates for goods from China, and a rate change from 1 January of the current year. Rates for items, categories or countries that don't exist in the company are skipped.
New OnBeforeIsExpectedCostApplicable_LC_TSL and OnAfterIsExpectedCostApplicable_LC_TSL integration events on purchase lines and transfer lines. #108365
Changed
The GetLinePredictedCost_LC_TSL, GetLineLandedCostLCY_LC_TSL and LookupLinePredictedCost_LC_TSL procedures on purchase lines and transfer lines are now public. #108367
Extensions can now subscribe to the event of codeunit Consignment Mgt_LC_TSL. #108375
Fixed
Fixed item charge rate matching to compare the HTS code with Tariff No. on the item card, allowing separate rates for different tariff classifications. Blank HTS codes apply to any tariff number. If the item's tariff number is blank, any HTS code can match. #108354
New Re-apply Templates action on purchase and transfer orders. It updates the predicted landed costs on lines that are not received or linked to a consignment, using the current consignment templates. Use it after a template is changed, replaced or deleted. See Re-applying Templates to Open Orders. #108018
New Generate Demo Data action on the Advanced Landed Cost Setup page, available in sandbox companies only. It creates the setup, vendors, item charges, attributes and consignment templates that Advanced Landed Cost needs, plus a set of open purchase orders that each show a different landed cost scenario. A Location Type option chooses whether the orders are received at a basic location, one that requires warehouse receipts, or one that requires inventory put-aways. See Creating Demo Data.
In sandbox companies, the Landed Cost Setup wizard now starts by asking whether you want to set up Advanced Landed Cost or generate demonstration data.
Changed
The purchase order Prepare tab now has a Landed Costs button with Create Consignment and Re-apply Templates.
The consignment template help now explains which order fields each template field is matched against, and how purchase orders and transfer orders differ. Shipping agents are only matched on transfer orders. See How Templates Are Matched to Orders.
Improve tooltips on several pages.
Improved consignment line editing and amount handling.
Improved landed cost calculations and display for transfer orders.
Improved consignment finalisation checks and setup options.
Fixed
Corrected the location assigned to consignments created from transfer orders.
Added the integration events OnBeforeFinishProdOrder and OnAfterFinishProdOrder to the Auto Finish Production Orders report, so extensions can run their own logic, such as shop floor finishing, when a production order is finished automatically. The events run before and after the standard status change to Finished, which always runs. Errors raised by subscribers are logged against the order as a failed status change. See Finishing events. #100973
Updated the Print License Plate report to select printers using the license plate location, and added a Location Code parameter to the Pre-Printed License Plates report so printer selection uses the specified location. #106768
Added FlowField support to label field mappings, both for fields on the label's source table and for fields on related records, such as an Item. FlowFields are now calculated before their values are formatted and printed, so labels use the calculated value rather than an uncalculated default, such as zero. Both the Field No. and Related Field No. lookups now allow normal fields and FlowFields, but exclude FlowFilters.
Added a new printer selection method that matches printer assignments by user, location, label type and template, while retaining the legacy method. #106768
Added the Label Print Log, which records every label job together with its source record, the label and printer selection that matched, and the printer it was sent to. A retention policy that keeps entries for 1 week is created and turned on. See Label print log.
Added Log Label Payload to Advanced Production Setup to store the content sent to the printer on each log entry. This is disabled by default.
Updated Tasklet license plate printing to use the new printer selection method, matching printer assignments to the selected label type and template. #106768
Prevented Undo Pick from processing registered pick lines with matching license plate entries and directed users to the Undo Pick with License Plate action instead. #101172
Fixed missing source documents and source names on warehouse receipts. Blank source information is now refreshed when users with write permission view the receipt list or document, and populated when receipts are created or updated from the Warehouse Receipt Board.
Added Create Picks by Order to warehouse shipments, allowing users to choose which source orders to pick and review their remaining pick quantities. #101177
Added a Warehouse Pick Group to vendors and purchase return orders. A new return order takes the pick group from its vendor, and changing it on the vendor offers to update open return orders. Purchase return orders can now be filtered by pick group on the Warehouse Despatch Board. See Warehouse Pick Group. #101177
Changed
Shipping numbers assigned during warehouse picking now support purchase return orders and carry through to posted return shipments. #101177
Updated warehouse shipment logistics statuses to report Shipped in Full on completed headers and lines, refresh line statuses during scheduled, explicit, and upgrade updates, and label lines that don't require a pick as Picked in Full/Ready to Ship.
Added a logistics status to warehouse shipments and their lines. The shipment status shows whether any line is still waiting for a pick, and the lines can be filtered by status.
Added a Schedule Logistics Status Update action to the Advanced Sales Setup. It creates a job queue entry that updates the saved logistics status of sales orders and warehouse shipments together in the background.
Added an event that lets other apps add their own figures to the Shipment Totals page. #106225
Changed
The Show Sales Order Logistics Status setup field is now called Show Logistics Status and also controls the status on warehouse shipments.
The Pending Picked Creation logistics status is now called Pending Pick Creation.
Added warehouse shipment and receipt totals, remaining quantities, pick visibility, receipt source information, and base-quantity totals on the warehouse boards. #106225
Added Inventory Movement totals on the list and document pages, with a Show Totals action for selected movements.
Added a Default Shipment Date Filter to the Advanced Sales Setup. The expression you enter, for example ..T, is applied to the Shipment Date Filter on the Warehouse Despatch Board when the board is opened with no filter in place. #100946
Added Warn on Different Shipment Date to the Advanced Sales Setup. When enabled, a single warning is shown if you add despatch board lines to an existing warehouse shipment whose shipment date differs from the shipment date on those lines. #100946
The New Shipment Date on the Create/Update Warehouse Shipment request page now defaults to the upper limit of the despatch board's Shipment Date Filter when no New Shipment Date Calculation Formula is set up. #101768
Added the integration event OnBeforeInsertGenJournalBalancingLine and OnAfterSettingFilterOnGlobalGenJournalLine in the codeunit "Generate EFT Payment_ACC_TSL" 70254471. See Extensibility.
Added the integration event OnAfterGetRecordUnpostedJournalAppliedEntry to the report 70254473 EFT Payment Schedule_ACC_TSL. Another extension can use it to retrieve or modify temporary buffer record when listing unposted applied entries . See Extensibility.
Added the integration event OnBeforeCheckEFTApprovalRequired to the Generate EFT Payment_ACC_TSL codeunit ID 70254471. Another extension can use it to skip, or require, approval for specific journal batches without changing Gen. EFT File without Approval in EFT Setup. See Extensibility.
When Skip Pending Approval/Missing Bank Accounts is enabled in Suggest Vendor Payments or Suggest Customer Payments, the open entries of a skipped vendor or customer are no longer left marked with an Applies-to ID. A later suggestion now picks them up once the bank account is available.
Suggest Customer Payments now skips a customer whose bank account is pending approval when Skip Pending Approval/Missing Bank Accounts is enabled. Previously the run stopped with "Bank Account … has not yet been approved".
Skipping a customer in Suggest Customer Payments no longer stops lines being created for the customers after it in the same run.
With Force Bank Account on Suggest enabled, Suggest Customer Payments now checks the bank account that matches the transaction: the direct credit bank account for refunds and the direct debit bank account for receipts. Previously a refund also required a direct debit bank account, and a receipt did not check the direct debit bank account.
Check Other Journal Batches now works in Suggest Customer Payments. A document already suggested in another journal batch is left out and listed for review, as in Suggest Vendor Payments.
Replace Description with Customer Name can now be selected in Suggest Customer Payments when you summarise per customer. It is cleared if you turn off Summarise per Customer.
Selecting Sales Return Order in the Usage field at the top of Report Selection - Sales now shows the return order reports. Previously the list did not change.
Changed
Each Sales, Purchase, Warehouse and Remittance Advice document report now uses its own copy of the shared RDLC layout. There is no change to the design or content of the printed documents.
Deprecated
The By Dimension option in Suggest Customer Payments is now hidden and marked as obsolete, because it never had any effect. It will be removed in a future release.
Non-Conformances cues are now shown on the Accountant, Accounts Payable Coordinator, Account Receivables, Production Planner, Purchasing Agent, Warehouse WMS and Product Specification role centers, so every role can see and follow up its non-conformances. #87115
The QC Check cue and Compliance Document Activities are added to the same role centers, and to the Order Processor and Non-Conformances role centers, where Aptean does not already show them. #87115
The Customer, Vendor and Internal Non-Conformances lists and the All Non-Conformances list now show how many follow-up actions each non-conformance has: No. of Actions, No. of Outstanding Actions (not yet closed), No. of New Actions, No. of In Progress Actions and No. of Closed Actions. Select a number to open the matching follow-up actions. #96176
On a Non-Conformance line, the Expiration Date and Lot No. now stay in step. Selecting a lot pulls through its expiration date, and entering an expiration date resolves the matching lot - automatically when only one lot carries that date, or by opening the Lot No. Information List to pick when several lots share it. When no lot information matches, the lot is still resolved from item ledger entries. #94613
Companion subscription plan — Purchase Accruals now has a Companion plan for when it's installed only because another Theta app depends on it (for example, Consignment Inventory). Choose the Companion plan under Service Connections in Theta Account Setup to stop subscription warnings. Accrual posting still needs the Essentials plan. On Companion, Consignment Inventory works, but it doesn't recognise purchase variances on receipt for standard-cost items.
Purchase Quote to Order — Fixed an approval error when running Purch. Quotes to Orders with purchase approval workflows enabled. #106389
Changed
Namespaces — All objects now use AL namespaces (Theta.PurchaseAccruals.<Feature>, e.g. Theta.PurchaseAccruals.Posting). Object names and IDs are unchanged. Apps that extend Purchase Accruals and already use namespaces may be impacted, and need using statements for the Purchase Accruals objects they reference. Apps without namespaces are not affected.
Added comment lines to charge conditions. Leave Line Type blank to add a text-only line, such as "Free Shipping", with no quantity or amount. Use a standard text code or type the description. See Setup.
Changed
The line-creation integration events (OnBeforeCreateSalesLine, OnBeforeSalesLineInsert and OnAfterCreateSalesLine) are now also raised for comment lines. Extensions that subscribe to them should check the line type if they expect a priced line.
Alert Report Selections — each Status Management line can now use its own report and layouts for alert emails, with the option to attach the report as a PDF. See Alert Report Selections. #92881 #107305
Status Mgt. Alert - Non-Conformance Detail report (ID 66005) for non-conformance status alerts. See Non-Conformance Detail report. #92881 #107305
Distribution Group action on Status Management Setup. #92881 #107305
Changed
App renamed from Aptean Notification Enhancement to Email Alerts for Aptean. Existing installations upgrade as normal.
Fixed
Status Management alerts for non-conformances now pick up the matching Status Management line's Distribution Group and Report Selection. #92881 #107305
Creating a warehouse pick for a sales order no longer fails with a bin error when the warehouse shipment uses a shipping bin. Pick take lines are now pointed to the promotion bin assigned on the sales line, but only when that bin has enough quantity available to pick for the full line; otherwise the bin suggested by Business Central is kept.
Deprecated
The CheckWarehousePickTakeLine procedure in codeunit "Promotion Mgmt_SP_TSL" is obsolete. Promotion bins are now applied automatically when a warehouse pick is created.
Managed Job Queues: deleting now removes job queue entries in every company, Earliest Start Date/Time is applied consistently, and Apply Changes picks up companies newly added to a Company Group.
Added
Managed Job Queues: choose which companies to apply changes to, and hold, restart or delete job queue entries for multiple companies at once.
Changed
Managed Job Queues: Apply Changes can be re-run when job queue entries are already active.
Automatic Forecast Alignment: imports can now align immediately and optionally publish to BC demand, with each completed action committed separately. See Automatic Forecast Alignment for details.
Changed
Demand Forecast Publish: successful publishing now refreshes all enabled derived forecasts that use its target as their source, retaining completed work if one derivation fails. See Automatic derivation after publishing for details.
External Forecast Alignment: missing items are now skipped and logged instead of stopping the alignment run. See External Forecast Alignment for details.
Demand Forecast Publish: added the publication date and time to demand forecast entry descriptions, and showed the last successful publication time and summary in the Forecast Status FactBox. The FactBox is always visible, with separate publishing and derivation groups. See Demand Forecast Publish for details.
Outbound Message Batching — split large background-sync exports into fixed-size batches, each its own outbound message, with a new Outbound Batches monitoring page. Read more
New outbound event — Synchronise in the background using CreatedAt date/time (per record) — like ModifiedAt sync, for insert-only feeds selected by creation date/time. Read more
Invalid JSON error highlighting — the Message Body Viewer now pinpoints where a message body's JSON fails to parse. Read more
Changed
API Endpoint records are no longer overwritten when importing integration handlers — handlers now bind to the target environment's own endpoint by code instead of replacing it. Read more
Fixed
Fields added by other extensions are now kept when exporting and importing a Data Exchange Definition — fields from other extensions (e.g. Excel Mapping Template Code) were previously dropped. Read more
Fixed an issue that prevented integration messages from being reprocessed when failed messages were configured for deletion after a successful import.
Dual Unit of Measure support on non-conformances. Customer, vendor and internal non-conformance lines now carry Units, Handling Units and Quantity (Base), including when lines are brought in with Get Posted Document.
Changed
Requires Dual Unit of Measure 28.1.1.0 and Aptean Non Conformances for Food and Beverage.
Resolved an issue in the Price List Import where the Allow Line Disc. and Allow Invoice Disc. values were replaced with the imported line's values, even when those fields were not mapped in the template.
Resolved an issue affecting Customer, Vendor, Item, Resource and Employee Imports - when the number was omitted from an import file, subsequent rows were added to the record created for the first row, so their details were not imported. The importer now creates a separate record for each row and assigns it a number from the number series.
Added
Internal Movement Import: Added support for importing internal movements from Excel or text files directly from the Internal Movements list. Requires a Premium subscription plan. More details...
Added shipped license plate retrieval for inbound transfer receipts and required license plate checks before receipt posting. #431 #100458 #101746
Added Unplanned Move Advanced from Locate Item, with options to move items onto new license plates or pallets. Advanced Move also supports full or partial license plate picks into a pallet. #101633 #100506 #100703
Added Reverse Posting, allocation history and navigation to Bulk Allocation, with allocation based on actual production output and precise rounding. Serial-tracked items cannot be bulk consumed. #101629
Added configurable license plate attribute captions and cleanup of obsolete staging entries. #94944 #99412
Changed
Added confirmation to Start New LP in receiving and assigned new license plates the Pallet type. #101720
Strengthened freight pallet scan validation and hierarchical output checks; output now retains license plate attributes and GS1 serial numbers. #99249 #104300 #101426 #105865
Improved license plate posting and content merging performance, platform compatibility and privacy classifications. #100947 #106180 #88972
Deprecated
Hid Allocation Variance, Consumption Variance, Expected Qty. (Base) and Consumed Qty. (Base) on Allocation Lines pending removal. Use Statistics instead. #101629
Fixed
Corrected bulk allocation eligibility, multi-day calculations and reallocation after deleting an unposted allocation log. Posted and reversed groups cannot be deleted. #101629 #104166
Corrected destination matching when adding license plates or items to pallets in Advanced Move. #100528
Corrected freight pallet additions and license plate types during posting. #104956 #103965
Corrected receipt handling for non-base units of measure and locations without put-away. #101735 #100528
Corrected production consumption time zones, hierarchical output license plate types and output reversal warnings. #103222 #101171 #100533
Changed Export Package and Import Package on the Label Templates page to include the label service used by each template, including its label size and print density. The Service URL is not included, so after importing a new label service, preview stays off until you specify its Service URL on the Label Services page. Packages exported from earlier versions still import.
Added a Label Output field to the request page of the Print License Plate and Pre-Printed LP reports. It defaults from the Label Printing Mode on Advanced Production Setup and can be changed for a single run, for example to export or preview the labels. Labels printed from a mobile device still use the Label Printing Mode. See Printing mode.
Added Break Bulk Labeling to break bulk inventory into smaller packs and print a label for each pack, optionally moving the packed quantity to another bin. See Break Bulk Labeling.
Added the Weight 6 Digits 3 Decimals transformation rule for label field mapping, for example 0.202 prints as 000202. See Labelling.
Added a Label Templates action to the Label Types page.
Added label preview, shown as a PDF using an external label service. Set up a service on the new Label Services page, starting with Labelary for ZPL labels, and choose it on the label template. Then use Preview Label on Label Templates or the new Preview printing mode. See Previewing labels.
Moved the label settings on Advanced Production Setup to a new Labelling tab.
Added a Label Output field to the request page of the label reports, defaulting from the Label Printing Mode, so you can change the output for a single run. See Printing mode.
Fixed
Fixed the Label Type lookup so new label types can be created from it.
Fixed the Get Expiration Date transformation rule so it uses the lot's current expiration date after a reclassification.
Added OnAfterSendLabelWhenPrintingLabel integration event to Label Printing Mgt, raised after a label is successfully printed, so other extensions can log or react to print requests. #99241
Added License Plate Print Log table and list page, and a "No. Printed" flowfield on MOB License Plate, to track when a license plate label has been printed. #99241
Changed
Changed automatic license plate label printing after Advanced Receipt posting to only print license plates that have not already been printed, avoiding duplicate labels for existing pallet/carton license plates. #99241
Changed the caption of the "Print License Plate on Warehouse Receipt" setup field to "Print New License Plate on Warehouse Receipt" and updated its ToolTip. #99241
The Auto Send COA job queue entry is now created automatically when the app is installed or upgraded, if it does not already exist. It runs every day, every 5 minutes. It is set to Ready, or to On Hold when the app is installed or upgraded by a CSP (delegated admin) user. An existing entry is never changed or duplicated, including one that is On Hold. #94604
New Auto Send COA Lookback (Days) field in the new Certificate of Analysis section of Quality Control Setup. It sets how many days back the Auto Send COA job looks for posted sales shipments whose Certificate of Analysis has not been e-mailed yet. The default is 5 days, and existing setups are set to 5 on upgrade. #94604
Changed
The Auto Send COA job no longer reads the look-back period from the job queue entry's Parameter String (for example DAYSBACK=14). Use the new Quality Control Setup field instead. #94604
Certificate of Analysis > Print on warehouse shipment lines now prints the Lot Certificate of Analysis instead of the old Certificate of Analysis report. If the line has item tracking for more than one lot, a separate certificate is printed for each lot. The customer, sales order, customer PO and shipment date are taken from the sales order. If no lot is assigned to the line, an error asks you to assign item tracking first. #94604
Fixed
When a posted sales shipment has several item lines, the Certificate of Analysis e-mail (sent from the Posted Sales Shipment page or by the Auto Send COA job) now attaches the correct lots for each line. Before, every line used the lots of the last line on the shipment. #94604
The Lot Certificate of Analysis request page no longer replaces the item, lot and shipment passed in from the calling page with the values saved from the last time the report was run. #94604
The Non-Conformance report now includes a Reference No. column against each product line for vendor non-conformances, showing the vendor's own item reference. The number is taken from the item reference set up for that vendor, then from the Item Vendor catalog, and finally from the Vendor Item No. on the item card. The column is hidden on customer and internal non-conformances. #103317
Fixed the Sales Shipment No. lookup on the Lot Certificate of Analysis report request page so the selected shipment number is retained instead of being cleared. #94604
New "Compliance Documents To Approve" tile on the Compliance Document Activities cue group, showing the number of purchase order compliance documents that are pending approval and letting you drill down straight to the list of documents awaiting approval. The Compliance Activities cue is now also available on the Warehouse Worker (WMS) Role Center. #101190
Safety Days (Lanham) — hold the safety cover Lanham plans with on the item and stockkeeping unit, so it can be maintained alongside the rest of an item's planning data and copied down to procurement units in bulk. The field is for Lanham's use only: Business Central ignores it, so unlike Safety Lead Time it does not push out the expected receipt date. See Update Procurement Units from Items for details.
Changed
Update Procurement Units from Items now takes Safety Stock Days from Safety Days (Lanham) rather than from Safety Lead Time. See Update Procurement Units from Items for details.
Planning Worksheet Schedule — runs failing overnight after a previous run logged planning errors. When a run left entries in the planning error log, the next run asked whether to continue from where it left off. Nothing can answer a question in a job queue session, so the run failed in milliseconds, and because the question is asked before the error log is cleared, every following night failed the same way. Restart After Error now decides this instead of a prompt: selected replans from the first item, cleared resumes from the item that failed. Schedules stuck in this state recover on their next run with no intervention.
Planning Worksheet Schedule — failed runs reported no planning errors. A failed run recorded an error count of zero and discarded its progress checkpoint, which made a run that never started look the same as one that finished cleanly. Failed runs now report the planning errors outstanding on the worksheet and keep the checkpoint showing how far the run got.
Added
Derived Daily Forecast — build a daily demand forecast from a weekly one, so short-term planning works from a shape that matches the trading week instead of putting a whole week's demand on a Monday. Days are weighted by a maintained pattern or by the location calendar, and settled against what has already sold and what is on order. See Derived Daily Forecast for details.
Division Codes from Item Categories — decide a procurement unit's division once, on the item category, and have every procurement unit follow it as items are created and move category. Divisions are inherited down the category parent chain, so a handful of entries covers a whole catalogue. See Division Codes from Item Categories for details.
Delete Empty Vendor Buying Calendars — remove vendor buying calendars that no procurement unit sits behind, so buyers are not scrolling past buying relationships nobody maintains. Scheduled with the other configuration rules under a single CONFIGMGT job queue command, which every rule added in future will run from too. See Delete Empty Vendor Buying Calendars for details.
External Forecast Alignment — import a forecast produced outside Business Central, attributed to a customer or grouping that need not exist in Business Central, and have planning use it. The Lanham statistical forecast is offset rather than overwritten, so planners keep both numbers side by side. See External Forecast Alignment for details.
Inventory Building Batches — plan a temporary build of inventory, such as a pre-season build or shutdown cover, and protect it from everyday demand until you choose to release it. Carried by transfer demand rather than forecast adjustments, so it works the same for items with no forecast. See Inventory Building for details.
Inventory at Risk — find lot-tracked inventory that is about to expire, or that is on hold or has failed inspection, and stop planning counting it as inventory you can sell, so the replacement is planned before the shortfall arrives. Priority-ordered rules decide what counts as at risk and how much of it to write off. See Inventory at Risk for details.
Demand Forecast Publish — copy the Lanham net forecast into a Business Central demand forecast, so Business Central planning works from the same demand the demand planner sees. See Demand Forecast Publish for details.
Suggested Order Action Bar — Create Purchase Order, Create Transfer Order and Statistics are promoted onto the suggested order's action bar, with the line review, transfer orders and transfer lines under Related. A new Posted Vendor Performance action shows how the vendor being bought from has performed on orders already received.
Open Purchase Orders Created — Create Purchase Order on a suggested order can now finish by opening the orders it created, instead of leaving you to go looking for them. One order opens on its own card, several in the purchase order list filtered to that suggested order. Optional, and switched on with Open Purchase Orders Created on the Suggested Order tab of Inventory Management Setup.
Changed
Configuration Assistant documentation — the setup and bulk maintenance features now have their own Configuration Assistant page, rather than a one-line summary on the Introduction.
Fixed an issue where negative consumption postings could incorrectly trigger the zero-Units error for Dual UOM items. #104022
Fixed an issue where reducing the weight to receive or ship could incorrectly reduce the ordered quantity and units on purchase and sales orders. The order is now preserved, and any related over/under units are cleared when the units to receive or ship are recalculated. (105362)
Added
Added Units and Remaining Units columns for Dual UOM items in Get Posted Document Lines to Reverse on Purchase Return Orders. Values update with Show Reversible Lines Only and Return Original Quantity across Posted Invoice, Posted Receipt, Posted Return Shipment and Posted Credit Memo sources. Reversal behavior for non-Dual UOM items is unchanged. #101880
Added support for date compression of warehouse entries when Dual Unit of Measure is enabled and in use. Compressed entries now keep the correct summed Units totals and the Warehouse Entry Units table stays in sync, while historical entries that differ only by their Units UOM remain separate instead of being collapsed into one misleading total. #70859
Changed
Corrected the translations of Outstanding Units and Units Outstanding, which had been translated as though outstanding meant excellent or remarkable rather than not yet delivered. The captions, tooltips and the related over-handling error message now use the correct wording in Danish, German (AT/CH/DE), Spanish, Finnish, French (CA/FR), Italian, Japanese, Norwegian, Dutch, Polish, Portuguese, Swedish and Simplified Chinese. Some of these messages also lost their quantity placeholder during translation, so the number of units was missing or shown incorrectly; this is now fixed.
When an Approval Administrator approves or rejects on another approver's behalf, it is now shown as such: the approval history on the Portal reads "Approved by (administrator) on behalf of (approver)", the Approval Set Approvers page has a new On Behalf column, and the Approval Sets page has a new Decided on Behalf column. Those decisions still count towards the approval as before
Changed
Complete new Approval functionality
The Approvals action on the Purchase Request card and lines now shows every approval entry for the request or the selected lines, including entries sent or approved by other users - previously only Approval Administrators saw the full list, and everyone else saw just the entries they had sent or were approving. On a line, it also includes the entries of the approval sets the line belongs to
Fixed
A requester who is also a Business Central user could approve their own request even when the approval rule's Self-Approval was cleared. The requester was only linked to their Business Central user when the e-mail addresses matched exactly, including capitals, which they usually do not - the link now ignores case, and existing requesters are re-linked when the app is upgraded
A mandatory approval level that nobody could approve - for example because the requester is the only person holding its role and the rule does not allow self-approval - was skipped, so the approvers at the later levels were still asked, and the request was then blocked anyway once they had all approved. Such a level now blocks the approval straight away, before anyone is asked, and the Blocked Reason names the level
The existing Approval Candidates preview on the Purchase Request Line now also shows whether each candidate already has an Approval Entry, so it can be used to see how far a request's approval routing has actually progressed
Fixed
A purchase request line could be released (and auto-converted to a Purchase Order) after an early approval level instead of escalating to the next level - the workflow settings needed for escalation are now cached when the request is first sent for approval, so escalation no longer fails if Business Central has already archived the workflow run, and the release decision now checks whether the routing chain has a further level to escalate to, rather than whether that level's approval entry happened to exist yet
A purchase request line now keeps an approval history (step number, approver, decision, and date/time for each step) in a new "Requestline Object" field, synced through to the Portal so the approval trail is visible there too
A new "Default Qty. to Receive" option in Purchase Requisition Setup (Remainder or Blank) controls how the Qty. to Receive field on a purchase requisition line is set after a receipt is posted, matching the same setting on the standard Purchases & Payables Setup
Changed
Renamed the "Archive" purchase request status/action to "Closed" to match the Portal's "Mark as Closed" wording (Purchase Request Setup's "Auto Archive PR"/"Notify Auto Archive JQ" toggles are now "Auto Close PR"/"Notify Auto Close JQ")
A purchase request can now be closed from any status except one that is already Closed, including Pending Approval - closing while Pending Approval automatically cancels the in-flight approval first
The Reopen action is no longer available once a purchase requisition line has been converted to a Purchase Order (Converted or Partially Converted) - only Rejected and Released lines can be reopened, preventing an already-ordered line from being resubmitted for approval
Fixed
Posting a receipt for multiple lines from the Purchase Request Card no longer fails with "cannot be saved because some information on the page is not up-to-date"
Closing a purchase request (manually in BC, via the Portal's "Mark as Closed", or via the automatic job) now syncs correctly to the Portal - previously the Dataverse status field didn't have a matching option for this status, so the sync could fail
Receipt Date now syncs through to the Portal's purchase receipt history - it was never populated in Dataverse before
A rejected purchase request line is no longer permanently blocked by the approval workflow's usage restriction - it is now released on rejection, the same as it already is on approval
Deleting a Purchase Request header in the Portal now also deletes it in BC, matching the existing behaviour for individual lines
Resubmitting a rejected purchase request for approval from the Portal now correctly reopens it and starts the approval workflow again in BC
Qty. to Receive on a purchase requisition line is now recalculated to the remaining outstanding quantity after a partial receipt is posted, instead of always being cleared to 0
A purchase request line created in the Portal is no longer occasionally deleted and then recreated on the next sync - it was being deleted if its Dataverse record still read as inactive at the moment it first synced into Business Central
Vendor Item No. on a purchase requisition line now syncs through correctly when the line is created or updated from the Portal - it previously stayed blank even though the selected Vendor Catalogue Item came through
Purchase Order Number is now synced through to the Portal for a purchase request line once it has been converted to a purchase order
Fixed
Deleting a Purchase Request or one of its lines now also deletes the corresponding Dataverse record, instead of leaving an orphaned row behind
Purchase Request header status is now consistently recalculated from its lines whenever a line is added, deleted, or changes status - previously this only happened for line quantity-based conversions, so some header statuses could go stale
A purchase requisition line sent for approval no longer gets stuck on Pending Approval with a Desired Status Error when its Approval Routing Header has no approver configured for it - it is now auto-released or rejected the same way a line with no applicable workflow already was, per the "Auto Release If No Workflow" setup toggle (now covering both cases)
Quantity Received on a purchase request line now reliably syncs through to the Portal after a partial receipt is posted, instead of only updating once the line reaches full quantity
Vendor and internal requester now receive an email notification when a purchase order is automatically released on conversion from a purchase requisition, each independently toggled via new "Email Vendor on PO Creation" / "Email Requester on PO Creation" settings in Purchase Requisition Setup
Purchase requests can now be archived (manually, from any status except Pending Approval, or automatically once every converted line is fully received, via a new "Auto Archive PR" job queue toggle in Purchase Requisition Setup); archived requests are hidden from the Purchase Requisition Worksheet but remain viewable and cloneable
Fixed
Post Receipt job queue no longer stops processing remaining purchase requests when an earlier one fails to post - every request is now posted or logged, none are silently skipped
Setting a default Dimension value on the Requester card no longer fails with a "record has changed" error
Requesters can now add a new line to a purchase request that has a rejected line, to complete what the approver flagged as missing; the request automatically reopens for approval once the new line is added
Developer API - General Journal Setup: Balancing lines created during general journal imports now use the standard SetUpNewLine function, allowing other apps to apply their default values through its extension events.
Developer API - Background Processing over REST: Imports created through the REST API (e.g. from Power Automate) now honour processingMethod instead of always processing immediately. Background imports are queued for codeunit 70253970 FileImportJobQueue_EI_TSL, and Manual imports wait for a manual Process action.
Data Validation - Distinct Errors Only: The Validate data before Import template setting has a new value, Yes - (Distinct errors only). Each distinct issue is then reported once, against the first row it occurred on, instead of once per row. This is useful for large files where the same issue repeats on many rows. More details...
Developer API - Data Validation for Custom Import Types: Extensions can now contribute their own row level validation. Codeunit "DataValidationMgt_EI_TSL" is no longer internal, so the documented OnBeforeCheckImportedValuesBeforeUpdate and OnAfterCheckImportedValuesBeforeUpdate events can be subscribed to from another app. The same codeunit also exposes the checks the built-in imports use - master record existence and blocked checks, item variants, units of measure, and the standard message shapes - so the errors an extension logs read like the rest of the list. More details...
Changed
Developer API - Distinct Errors: Distinct errors collected for an import definition now name the first row the issue occurred on. Previously the row was removed from the message.
Added transformation rule support so payment reconciliation values can be reviewed and overridden before journal transfer. See Custom Field Values. #97270
The payment suggestion and EFT processes can now be driven end-to-end from another extension, so a large payment run can be generated in controlled batches and sent to the bank unattended. See Running processes unattended.
Added a new Extensibility reference page listing the integration events and public procedures the app publishes, grouped by area.
Quality Control Check headers for receipt and shipment document types now show the originating source document numbers in the Source Name, in the format Default Source Name [PO-10045, PO-10051]. The Source Name is populated when the check is created, kept up to date as warehouse receipt and shipment lines are added, and falls back to the Quality Control Plan description when no source documents are found. Existing quality control checks are updated once on upgrade/install. #88240
Added Advanced Move for inventory movement orders, including partial license plate picking, label printing and reprinting.
Added Bulk Consumption Allocation to apportion material across production orders by actual output, with review, scheduled processing and traceability. Orders cannot finish while bulk consumption remains unallocated. #100953
Added license plate assignment during picking. #87708
Added Units UOM Source to select production-order or put-away units for production scans, with conversion and consistency checks.
Blocked production output onto license plates in bins with Strip License Plate enabled.
Changed
Removed the separate destination license plate step when starting a new license plate in Advanced Receive. #99242
Hid shipments with no pallets ready for truck loading and clarified pallet loading status. #98622
Left partial consumption quantities and units blank to avoid accidentally accepting a full label quantity.
Enabled explicit retries of suspended production scans and processed pending output before dependent consumption.
Improved license plate creation performance when importing existing inventory.
Added support for non-base units of measure in item and reclassification journal posting. #99116 #100937
Fixed
Corrected non-base quantities in production output and consumption posting.
Preserved receipt document details and original receipt-line links through receiving and put-away. #99292
Corrected posted document references in license plate entries and movement audit records. #376 #93929
Corrected picked license plate checks when building freight pallets. #99249
Added Update Quantity on Finish to Advanced Production Setup, disabled by default. When enabled, changing a production order from Released to Finished sets each line Quantity to the Finished Quantity and recalculates the component Expected Quantities to match, so expected versus actual consumption on a finished order is a true variance and the actual mix can be extrapolated from it. Applies in both directions, including over-production. Because the new quantity is validated, an open warehouse document such as an output put-away now stops the finish until it is registered or deleted. See Update Quantity on Finish.
Added Original Quantity to the production order line, shown on the lines of a Finished Production Order. It is written the first time an order is finished, so a finished order always carries the planned figure, and a reopened order keeps the plan it was originally finished against. It differs from Quantity only where Update Quantity on Finish was enabled and the finished quantity was not the planned quantity.
Added Cost Shares by location and effective date to the BOM Cost Shares page. You can now select a Location Code, Variant Code and Effective Date, and calculate the cost shares using the production BOM, routing and lot size that apply to the stockkeeping unit at that location, at every level of the structure. Opens from the standard Cost Shares action on the Item Card, and from new Cost Shares actions on the Stockkeeping Unit Card and Stockkeeping Unit List. See Cost Shares. #101344
Added Production BOM Version Code and Routing Version Code columns to BOM Cost Shares, so a calculated figure can be traced back to the setup that produced it. These are hidden by default and can be added with Personalise, alongside the standard Production BOM No. and Routing No. columns.
Added two fact boxes to BOM Cost Shares, each showing the item, production BOM, routing and lot size the figures were calculated from. Top-Level Item stays fixed on the item being costed. Current Item describes the item behind whichever line you are on — so a component or a work centre line still tells you which production BOM produced it — and lists every production BOM and routing available to that item: the item card, plus each stockkeeping unit that resolves to something different. The row the figures came from is shown in bold. The production BOM and routing are each shown as a single value carrying the number, the version code and the date the version starts from, and choosing one opens it. #101344
Added Cost Shares by Location to Advanced Production Setup, enabled by default. Turning it off restores the standard Business Central behaviour of the page.
Initial app release with the following capabilities:
BOM cost and yield visibility — product yield %, process weight change %, scrap %, total input and output weight per batch, and cost per batch on the BOM Cost Shares screen. Yield is shown only on lines produced from a production BOM and is read from the production BOM version effective for the line; component lines show process weight change % instead. Scrap % comes from the production BOM line on component lines and from the routing line scrap factor % on capacity lines.
Target batch size on the Top-Level Item and Selected Line fact boxes of the BOM Cost Shares screen, so the batch behind the per-batch weights and cost is visible alongside the lot size.
Automatic expiration dates on manufactured output — rules per item, item variant, or item category, counted from either the work date or today's date, with an optional cap to the earliest expiration date of the ingredients consumed on the production order line. Rules are maintained on the new Item Output Expiration Date Setup list.
Cancel Reservations Entries and Cancel Shopfloor Entries actions on released production orders, letting a planner reduce or restructure an order already in progress. Reservation cancellation also runs automatically when an order is refreshed, with the resulting date-conflict warning suppressed.
Post Time Entries action on the shop floor time entries list, opening the posting batch job already filtered to the released production order behind the current entry.
Shop floor awareness in Advanced Production auto finish — a routing line counts as finished when its Aptean shop floor status is Finished, a production order line with a shop floor status of Finished is treated as ready to finish, and a line with unposted shop floor time entries is held back. The outcome is recorded as Time Entry Result on the Auto Finish Production Order Log.
Aptean Production Enh. Admin permission set covering the new table, pages, report and codeunits.
Added Allow Different Order UOM for normal Items to the Dual Unit of Measure Setup. When enabled, the Order Unit of Measure on sales and purchase lines can differ from the line unit of measure for items that are not Dual UOM items, so you can order in pallets or kilograms while pricing, receiving and putting away in cartons. The Order Quantity is converted to the line quantity as before. The setting is enabled by default for new installations and disabled by default for existing installations, so behavior does not change when you update the app.
Added support for non-specific item tracking on Dual UOM items, where the item tracking code does not use specific tracking so lot, serial or package numbers are captured on inbound transactions only, or on outbound only. These items now complete the full flow at every location configuration: basic, bin-mandatory, inventory put-away and pick, warehouse receipt and shipment with picks, and directed put-away and pick. Because no tracking line dictates the units on an outbound document, picks derive the units from the stock being picked. See Warehouse - How Units are Defaulted on Picks for details.
Fixed
Fixed an issue where reopening Item Tracking Lines after posting a tracked shipment or receipt for a Dual UOM item could still show the posted Units as waiting to be handled. The posted quantity was handled correctly, but the related Units were not moved into Units Handled. This is now corrected for both shipments and receipts, whether or not the item tracking code uses specific tracking. (#100939)
Fixed an issue where the item-level Prevent Negative Inventory setting was ignored when checking that a posting would not drive the units inventory negative; only the Inventory Setup value was effectively applied.
Fixed Item Reclassification Journal posting for Dual UOM items at bin-mandatory locations when using multiple tracking lines. Weight tolerance checks and package units are now calculated per tracking line, preventing posting errors and incorrect units in warehouse entries.
Added Handling Units conversion support to Item Availability pages for non-dual UOM items with a Put-away Unit of Measure.
Fixed
Fixed an issue where the Handling Units conversion in ConvertUnitsToHandlingUOM would exit without converting when the source or target UOM resolved to blank. Blank UOMs now default to the item's Base Unit of Measure, enabling correct conversion for non-dual items on all Item Availability pages.
Fixed an issue where only one lot, serial or package number could be entered on a document line. Choosing a second tracking number from the lookup silently replaced the first line instead of adding its own, with no error shown. This affected every item tracking line, not only those on Dual UOM items.
Fixed an issue where non-dual UOM items on sales orders could be over-shipped beyond the outstanding quantity. The app was suppressing Business Central's standard quantity-to-ship validation for all items, not just dual UOM items. Warehouse shipments, picks, and inventory picks were not affected as they already correctly limited non-dual items to the outstanding quantity.
Fixed an issue where planning-created production orders could create multiple reservation entries with incorrect Units, leading to warehouse shipment item tracking and posting issues. #99264
Fixed an issue where the Transfer Order had a comment line, which was causing issues for Warehouse Shipment posting as the line was treated like an item line.
Added
Added Handling Units columns (Inventory and Expired Inventory) to the Lot No. Information Card, following the same display mode as Bin Contents.
Added a Qty. per Handling UOM column to the Item UOM Equivalents FactBox on Sales Orders. For dual items this shows the Units unit of measure; for non-dual items it uses the put-away unit of measure, falling back to the base unit of measure if none is set.
Added a Handling Units per Unit of Measure column to the Item Units of Measure page and a Handling Units inventory column to the Item List. Both follow the Show Handling Units for Non-Dual UOM display mode on Dual Unit of Measure Setup.
Fixed an issue where planning-created production reservations could leave units at zero and block warehouse shipment posting.
Fixed Item Tracking Lines lookup so selected lot/serial/package entries now assign the correct Units for variable-weight items.
Fixed posting and undo errors on Assembly Orders where Resource BOM lines were incorrectly treated as requiring Units. #99250
Added
Added Handling Units columns to the Lot No. Information List (Inventory and Expired Inventory) and the Item Ledger Entries Preview page. They follow the same display mode as Bin Contents, set by Show Handling Units on Bin Contents on Dual Unit of Measure Setup. See Warehouse - Bin Contents - Handling Units Display.
Added a new opt-in warehouse display mode on Dual Unit of Measure Setup for Bin Contents to support viewing Handling units for non-Dual UOM items as well as Dual UOM items. You can choose to hide, show alongside, or show instead of the existing Units columns by using Show Handling Units on Bin Contents. This is opt-in because it is not appropriate in all scenarios. For Dual UOM items, Handling Units show the existing Units values (no conversion). For non-Dual UOM items, Handling Units use the item put-away unit of measure, with fallback to the Bin Contents unit of measure when put-away UOM is blank. See Warehouse - Bin Contents - Handling Units Display.
Added an Item Card visibility improvement so the Dual UOM ratio/units group is shown only when Unit of Measure - Units is specified on the item.
Fixed an issue where changing Qty. to Handle or Units to Handle on a warehouse Put-away line incorrectly triggered tolerance recalculation, causing the line's Quantity and Units to be reduced. Put-away quantities are now correctly fixed to what was received and are no longer affected by handling field changes.
Added
Added new setup support for fixed-weight rounding variance to improve handling of precision edge cases. For configuration guidance, see Setup - Fixed-Weight Rounding Scenario.
Initial app release. Distributes Dual Unit of Measure demand units from production order components onto Aptean consolidated production movement internal movement lines and their per-lot warehouse item tracking lines, using proportional quantity-share allocation with cumulative rounding.
Posting a receipt no longer leaves stranded documents on the Purchase Order if it fails partway through
Post Receipt job queue no longer stops entirely when one document fails to post - other locked receipts still process, with failures logged
Background jobs (Post Receipt, Auto Convert PR to PO, Process PO Receipt) only suppress and log errors when run via Job Queue; manual runs show errors as normal
Fixed errors resetting a Purchase Requisition line after posting and using the Condition assist-edit on a new Approval Routing Line
Added
Purchase Requisition Job Log for reviewing background job errors and summaries, accessible from Purchase Requisition Setup
Posting receipts for a document now shows a summary message if any lines fail
Added a Warehouse Pick Group field to the Location card, under Purch., Sales & Transfer. Validating the Transfer-to Code on a transfer order now copies the warehouse pick group from that location, in the same way that a sales order copies it from the ship-to address. Changing the pick group on a location also offers to update open transfer orders that transfer to it. See Warehouse Pick Group.
Fixed an issue where no further picks could be created for a warehouse shipment once a pick existed for some of its lines. Adding another source document to the shipment and creating picks again reported that there was nothing to handle, and the only workaround was to delete the existing picks. Source document lines that are already covered by an open pick are now left alone, and picks are created for the remaining source documents as expected. This applies to both the Create Pick action on a warehouse shipment and the Create Multiple Warehouse Picks action on the warehouse shipment list. See Whse. Pick Create Method.
-Updated Warehouse Receipt Worksheet logic to populate the Location field from the Transfer-to Location, ensuring warehouse receipts are created successfully at the configured receiving location and preventing downstream processing issues.
Resolved an issue in outbound XML and JSON exports where a child line definition sharing its parent's Data Line Tag had its columns written after all of the parent's columns, producing a duplicate element such as a second <DbtrAgt> in a pain.001 file. Columns now interleave by Column No. again, as they did before 27.0.10.0. This completes the partial fix released in 27.0.16.0. Read more
Resolved an issue where a Data Format using the Business Central placeholder syntax (e.g. <Year4>, <Precision,2:2>) combined with a Data Formatting Culture exported the literal format string instead of the formatted value. Existing definitions are unaffected; the combination can no longer be configured. Read more
The app Now depends on the Microsoft Marketplace (AppSource) version of Purchase Accruals, version 26.0.1.0 or later
This version requires the Microsoft Marketplace (AppSource) version of the Purchase Accruals app. If you are still running the PTE (per-tenant) version of Purchase Accruals, you must migrate to the Marketplace version before updating Consignment Inventory, otherwise the update will fail.
Purchase Accruals 26.0.1.0 includes an App Migration Tool for moving from the PTE app to the Marketplace app. See the Purchase Accruals changelog for details, and contact us if you need help with the migration.
Demand Forecast Import: Demand forecast entries can now be imported from Excel or text files directly from the Demand Forecast Card. Supports aggregate lines, replace-all or replace-period update methods, and automatic base quantity calculation from the item's unit of measure. More details...
Payment Reconciliation Import: Payment reconciliation journals can now be imported from Excel or text files, with optional standard automatic matching.
Price List Import - Group by Start Date: A new template setting controls whether the Starting Date forms part of the price list grouping. It defaults to No, so prices with different starting dates are now added to the same price list. Existing templates are automatically set to Yes on upgrade, so imports keep behaving as they did before.
Fixed
Price List Import - Expire Other Prices: Expired price list lines are no longer left waiting to be verified. Where an expired line was in a Draft state on an Active price list, it is now returned to Active after the ending date is set, as the import has already verified the line.
Bank Statement Import - Multi-Bank Files: A single import file can now contain transactions for multiple bank accounts. When the Bank Account No. column is mapped in your template, the importer automatically creates or aggregates into a separate reconciliation per bank account — rows can be in any order. Aggregation rules, statement dates, balance updates, and automatic matching all apply independently per bank account. More details...
Added additional sample bank statement template for the ASB CASE format, with support for multiple statements in one file.
Import Dialog - Last Import Error Indicator: If a previous import of the same template failed mid-way, the import dialog now shows a warning with the last known position — the row, column, sequence, field, and value being processed at the time of the error. This makes it easier to identify what went wrong without having to reproduce the error. Clicking the lookup button next to the indicator opens a detailed view showing the full error message and call stack. More details...
Resolved an issue in the Suggest Vendor Payments batch job where a vendor bank account restricted by a pending approval workflow could raise an error while the journal line's Account No. was being validated, interrupting the batch job before the Skip Pending Approval/Missing Bank Accounts option had a chance to apply.
Resolved an issue where the Default Update Report Selection page (introduced in 27.1.1.0) did not filter the standard Report Selections correctly after the move to the standard Report Selection Usage enum. The Copy from Report Selection and Auto Update Layout actions now map the customer layout usage to the correct standard usage value and behave as expected.
The New view on the EcpPro Invoice List now shows an invoice while either its Sales Processing Status or its Purchase Processing Status is still New. Previously the view keyed off the sales side only, so an invoice whose sales document had already been created but whose purchase document was still outstanding dropped out of the view.
Fixed
For scenarios where EcpPro invoice's customer matches the Internal Customer No. and sales document creation is skipped then the Sales Processing Status is now set to Skip (instead of New).
Posting a sales or purchase document linked to an EcpPro invoice no longer fails; the linked-document check now only blocks manual deletes of unposted documents and is skipped for the delete that occurs as part of posting.
Fully returned order lines are now released from the consignment, their consignment link can be changed or cleared, and adding or amending charges no longer fails when a linked receipt falls in a closed Inventory Period. #99380
Added limited support for subcontracting purchase orders for order tracking only. You can link subcontracting purchase order lines manually to an empty consignment, but consignment cost lines and landed-cost allocation are not supported. See Subcontracting Purchase Orders for details.
Full support for purchase returns and undo receipts on consignment-linked orders. Predicted and actual landed costs are now correctly reversed and redistributed when goods are returned or a receipt is undone. See Purchase Returns and Undo Receipt for details. #96102
Added Batch action group to the Item Journal and Item Reclass. Journal pages, surfacing the Item Journal Batch Delete and Batch Post Item Journal tools directly from the journal ribbon. The current journal template and batch are pre-set automatically when launching either tool from the journal.
The Archive Posting Setup and Revert Posting Setup functions used during custom take-on processes are now accessible to customers with an active Essentials subscription, in addition to implementation partners.
Changed
Added Continia tables (6225781, 6225782, 6175315) to the default exclusion list used by the Sandbox Initialisation email/phone update, so Continia Users / Continia User Setup email addresses do not get overwritten.
Budgeted Exchange Rate — Purchases can now be valued at a budgeted currency rate, so exchange movements are recognised as realised gain/loss on payment instead of changing inventory cost or purchase variances. Configure the rate in Budgeted Relational Rate on Currency Exchange Rates, enable it on Purchase Accrual Setup (Document Only, Posting Only, Document and Posting), and opt in vendors individually with Use Budgeted Exchange Rate. See Budgeted Exchange Rate.
Prepayments on Released Purchase Orders — The app can now allow Prepayment % changes on Released and Pending Prepayment purchase orders without reopening, including header and line-level prepayment handling. Enable the company switch on Purchase Accrual Setup and then opt in each vendor. See Prepayments on Released Purchase Orders.
Inspection Status Reason Codes are now kept in sync with the standard "Reason Code" table: creating, editing, or renaming an Inspection Status Reason Code automatically creates or updates the matching Reason Code. Existing Inspection Status Reason Codes are synced once on upgrade/install.
Photo attachments linked to a Non-Conformance (including those attached to follow-up action lines) are now included on the Non-Conformance report. Previously only images stored against the Non-Conformance header table were shown. #98553
Attachments can now be uploaded against Non-Conformance Follow-Up Action records without error. Added a new "Non-Conformance Follow-Up Action" document type so attachments are correctly linked to the specific follow-up action line on the #98553 Non-Conformance.
Extended the All Non-Conformances page to display Status Management status code and description from Aptean Status Management, and replaced the Location Code column with Origin Location Code. #98628
New "All Non-Conformances" page giving a single list of every non-conformance, with views for Customer, Vendor, and Internal types (and open/closed variants of each), and the ability to navigate straight to the underlying non-conformance card.
Changed
Extended Quality role center refreshed to surface the new All Non-Conformances list alongside Inspection Status and Expiration Management activities, and reorganised the Compliance Documents and Non-Conformance Setup actions.
New "Extended Quality" role center combining Product Specification, Compliance Documents, and Quality Control cues, activities, and setup into a single home page.
Added a Qty. per [Units] UOM column to the Item Units of Measure FactBox, showing how many of each unit of measure are contained in one unit of the item's units unit of measure. This complements the existing equivalent quantity column. #98617
Fixed
Fixed rounding in unit conversions for fixed-ratio items to use high-precision rounding (0.00001) rather than UOM conversion rounding, preventing units from being rounded to an incorrect value. #98617
Fixed an issue where renaming a Unit of Measure code did not update Unit of Measure - Units on Dual UOM items. Renaming now updates the item, including items with posted ledger entries.
Fixed an issue on Item Tracking Lines where reducing the quantity on an existing lot did not update the reservation units, causing tracked units to revert when the page was reopened.
Fixed an issue on Item Tracking Lines where rebalancing lots multiple times could overstate tracked units. Units are now distributed across the lot's reservations in proportion to quantity.
Fixed an issue in warehouse shipments for random-weight items where reduced shipment and tracking units were not saved after pick registration.
Changed
Added support for Inventory Movements created by other extensions (e.g. consolidated production movements) where the warehouse item tracking lines do not carry Dual UOM information. The app now correctly populates units on movement lines in these scenarios. See Warehouse - Internal Activities for details.
Renaming or deleting an Item Unit of Measure record that an item uses as its Unit of Measure - Units, Order Unit of Measure (Sales), or Order Unit of Measure (Purchases) is now blocked with an error, mirroring how Business Central protects the base, sales, and purchase units of measure. To rename such a unit of measure, rename the Unit of Measure code itself, which updates all references.
Fixed the linked purchase order line not being synchronised when applying an over-shipment on a drop shipment sales order, which caused item tracking synchronisation to fail because the tracking quantity exceeded the purchase line quantity.
Added
Added the Item Units of Measure FactBox to the Sales Order page. When you select a line for an item, the FactBox shows all units of measure configured for that item along with the equivalent quantity for the line's current quantity. This makes it easy to see at a glance how the ordered quantity translates across all configured units without leaving the order.
Fixed an error that occurred when creating or releasing a warehouse shipment for a sales order containing a Dual UOM line where both Order Quantity and Order Units were set to 0.
Fixed an issue where Warehouse Entries for over-consumption of a random-weight, lot-tracked Dual UOM item had incorrect unit values when multiple lot numbers were posted together. Units are now split consistently with the related Item Ledger Entries.
Added
Drop shipments: Added support for posting shipment directly from the sales order for drop shipment scenarios (automatically synchronising the linked purchase receipt).
Improved the reprocess experience for failed integration messages by introducing clearer operator guidance and support for retaining the existing retry chain when reprocessing. Read more
The default failed-message handling in Integration Hub Setup now uses Delete Failed Messages After Successful Import to better support cleanup after successful retries.
Updated the documentation for time zone handling to clarify Default Time Zone, UTC background-processing context, and where time zone settings are applied. Read more
Added activity cues to the Order Processor Role Center. #98398
Changed
The Find Entries (External) action is now promoted to the Process (home) category on the Sales Order, Posted Sales Invoices list, and Posted Sales Shipments list for quicker access. #98398
Boolean values in outbound HTTP messages now default to true/false — a new Use Boolean Format in Messages setting has been added to the Integration Hub Setup page. For new installations this defaults to enabled, so boolean fields (e.g. isproduction, base64encoded) are sent as true/false rather than Yes/No. Existing installations retain the previous Yes/No behaviour by default, ensuring no impact on Logic Apps or other integrations that rely on those values.
Fixed locale-sensitive boolean formatting in outbound HTTP payloads that caused a 400 Bad Request error when Business Central was set to Polish language. #97221
Resolved an issue when generating outbound messages where fields targeting the same element were written into separate elements. They are now merged into the same element again.
Export/Import Integration Handlers now includes additional subscribers — the Export Integration Handlers action did not include a handler's additional subscribers (child handlers). Importing the exported file therefore recreated the handler without them, so outbound events produced fewer messages than expected. Additional subscribers are now exported and re-imported together with their parent handler.
Changed
Minor internal changes to enhance the app's automated testing.
Outbound XML/JSON export fails for Data Exchange Definitions with short column paths — resolved an error where outbound exports using Data Exchange Definitions with column paths that do not include the Data Line Tag prefix (e.g. /fieldname instead of /root/parent/fieldname) would fail during file generation. This regression was introduced in version 27.0.10.0 as a side-effect of the export line numbering change. Definitions that previously produced flat JSON or XML output are no longer affected.
Export crash when snapshot is not active — resolved an error during outbound export when the snapshot manager had not set a record variant for the session. The export now falls back to opening the source table directly, so exports work correctly regardless of whether a snapshot is in use.
The bank's ACK/NACK feedback description is now recorded against each EFT Transfer Line, in the existing Payment Status Reason field, so users can see why the bank accepted or rejected a specific payment line.
Changed
EFT feedback processing no longer requires the bank response to contain the EFT Transfer No. When the bank returns only its own message reference (for example ASB), the feedback is now matched to the correct EFT Transfer using the line-level unique EFT Reference. An integration event (OnResolveEFTTransferHeaderFallback) allows bank-specific extensions to implement alternative matching.
EFT bank account fields (EFT Bank No., EFT Bank Branch No., EFT Bank Account No., EFT Bank Suffix No.) on the Vendor Bank Account, Customer Bank Account, Bank Account, and Employee records now respect the Business Central sensitive data masking feature.
EFT bank account fields (EFT Bank No., EFT Bank Branch No., EFT Bank Account No., EFT Bank Suffix No.) on the Vendor Bank Account, Customer Bank Account, Bank Account, and Employee records now respect the Business Central sensitive data masking feature. When masking is enabled, these fields are hidden by default and can be revealed using the unmask button — consistent with the behaviour of the standard Bank Account No. and Bank Branch No. fields.
Fixed
Resolved a regression where the link between Banking Details in Payment Journal and Edit EFT References on Payment Journal in EFT Setup was re-introduced by a branch merge. The two flags are once again fully independent: each can be toggled freely without affecting or blocking the other.
Resolved an issue where enabling Edit EFT References on Payment Journal in EFT Setup had no effect on the downloaded EFT file when Banking Details in Payment Journal was turned off. The EFT file now honours user-entered values in the EFT Particulars, EFT Code, and EFT Reference fields on the journal line, regardless of whether banking details are sourced from the journal or the bank account master record.
Added
Added Word layouts for the Customer Statement. The layout closely matches the existing templates and can be easily customised by users and administrators. See Word Layouts for details.
Changed
Edit EFT References on Payment Journal and Banking Details in Payment Journal in EFT Setup are now fully independent flags. Each can be toggled without affecting the other.
Custom document layout pages now use the standard Business Central extensibility model – Microsoft now supports extending the report selection usage enums directly, removing the need for our previous workaround. Existing data is migrated automatically on upgrade. If you have an extension that references the deprecated objects listed below, please test before deploying to production. See Extending Report Usage Mappings for details.
Deprecated
The following objects and members are marked obsolete (tag 27.0) and will be removed in a future release. Existing data is migrated automatically on first run after upgrade.
Table Custom Email Pref._ACC_TSL — replaced by CustomEmailPreference_ACC_TSL.
Table DefaultUpdateRepSelect_ACC_TSL — replaced by DefUpdateReportSel_ACC_TSL.
Page CustomEmailPref_ACC_TSL — replaced by CustEmailPreference_ACC_TSL.
Page DefaultUpdateRepSelect_ACC_TSL — replaced by DefUpdateRepSelection_ACC_TSL.
Enum CustReportLayoutUsage_ACC_TSL — replaced by the standard "Report Selection Usage" / "Custom Report Selection Sales" enums (extended via CustReportSelSales_ACC_TSL).
Field Usage3_ACC_TSL on the Customer Report Selections page extension — the standard Usage field is now visible and editable instead.
Procedures Report Selection Mgt._ACC_TSL.AutoUpdateCustomerDocumentLayoutEmails, MapReportUsageToCustomReportUsage, MapCustomReportUsageToReportUsage and the integration events OnMapReportUsageToCustomReportUsage / OnMapCustomReportUsageToReportUsage.
Planning Worksheet Schedule — automate and sequence standard Business Central planning worksheet runs in the background. Each schedule line stores its own worksheet, parameters (including forecast), and run order. Review run status, duration, and any planning errors after each run. Schedule via one or more job queue entries. See Production Planning for details.
Added Conditional Template feature, allowing label field mappings to splice in reusable conditional text blocks based on source field values. #95825
Added JSON import/export for Label Templates, including their field mappings and referenced Conditional Templates, to simplify moving templates between environments. #95825
Added Auto Finish Production Orders feature, allowing production orders to be automatically finished based on configurable rules for output and consumption tolerances. #95693
Improved SSCC check digit handling in SSCC 00 formatting — an 18-digit SSCC now has its check digit validated regardless of the 'Add GS1 Check Digit to SSCC' setting; when the setting is enabled, both 17-digit (check digit appended) and 18-digit (check digit validated) inputs are accepted. #98388
Fixed license plate label printing to correctly resolve various item contents by using calculated license plate data from Advanced License Plating. (#97054)
Fixed SSCC formatting when the 'Add GS1 Check Digit to SSCC' setting is disabled — the barcode is now correctly validated as 18 digits and formatted with the '00' application identifier. #95825
Added ZIP functionality to Import and Export Label Content actions on the Label Templates page, allowing label template files to be imported and exported individually or in bulk from a ZIP archive. #95825
Force Delete action added to Sales Invoice, Sales Credit Memo, Purchase Invoice and Purchase Credit Memo card and list pages.
Changed
Sales or purchase documents linked to an EcpPro invoice can no longer be removed with the standard Delete action; the Force Delete action must be used instead.
Developer API - Background Processing: The background job queue codeunit (FileImportJobQueue_EI_TSL) now processes queued files. When ProcessingMethod::Background is used, files with a status of Queued for Processing or Queued for Retry are picked up one at a time. Each file is processed in isolation so a failure in one record does not block the remaining queue. Schedule codeunit 70253970 FileImportJobQueue_EI_TSL as a recurring Job Queue Entry to enable this. More details...
Receipt Registration — Warehouse and operational staff can now register non-inventory purchase receipts (G/L Account, Resource, Fixed Asset, Service Items, Non-Inventory Items) from the Purchase Order or Purchase Order List without posting. Registrations are stamped with the user and date/time, queued for review, and can be posted individually or in bulk by the finance team. This provides an auditable record of goods and services received within a period, enabling accurate month-end accruals without requiring the purchase order to be ready for invoicing. See Receipt Registration.
Purchase Quote to Order Conversion — A new batch report (Purch. Quotes to Orders) converts all released and approved purchase quotes into purchase orders in a single step. The resulting orders are automatically released, the purchase order is emailed to the vendor (where an email address is configured), and the original quote creator is CC'd. Approval entries from the quote are copied to the resulting order so approver information remains visible. The report is accessible from the Purchase Order List and Purchase Quotes list. See Purchase Quote to Order.
Added integration events to the Allow Posting Date update process so extensions can intercept and adjust the General Ledger Setup : OnBeforeModifyGLSetupand User Setup :OnBeforeModifyUserSetup records before they are modified.
Rebate Per Unit Calculation Methods: Rebates can now be calculated as a fixed amount per unit of measure, in addition to the existing percentage method. Three new calculation methods are available: Specific Unit of Measure, Sales Unit of Measure, and Base Unit of Measure. See the Setup Guide for details.
Added the QuantityIsChangedDueToOverUnderReceipt_DU_TSL procedure on Sales Line as a public API for third-party extensions that integrate with sales pricing. Extensions can call this function to determine whether a quantity change was caused by an over/under receipt adjustment and suppress any unwanted price updates accordingly. Extensions that do not have their own pricing logic do not need to use this function, as the Dual Unit of Measure app already handles price updates internally.
Fixed an issue in Item Journal Item Tracking Lines where fixed-ratio items using a third document UOM could calculate Units-to-Quantity and Quantity-to-Units incorrectly; conversions now correctly use the item's base unit of measure.
Changed
Changed the access scope of the CalcQtyAvailToTakeUnits_DU_TSL procedure on Bin Content table from internal to public.
Changed the access scope of the CalcUnitsOnComponentLines_DU_TSL procedure on Item from internal to public.
Fixed an issue in warehouse shipments where, after picking items from multiple lots, manual reductions to the quantity to ship (less than picked) were not saved; adjustments now persist correctly when handling multiple lot numbers.
Changed
Updated the caption of the Units per Unit of Measure field on the Item Units of Measure page to remove duplication of the configured Units caption. Also improved the tooltip to better explain how the value is derived and what it represents. Also updated the online help.
Improved support for items that use lot, serial, or package tracking without specific tracking or warehouse tracking enabled. When an item is configured to record tracking numbers only on selected transactions (non-specific tracking), units stock-on-hand checks and warehouse bin availability calculations no longer filter inventory by those tracking numbers, preventing false insufficient-stock errors during posting and warehouse pick creation.
Outbound Granularity — consolidate multiple records into a single outbound message instead of sending one message per record, reducing file count for batch exports. Read more
CSV export — export data as comma-separated files with configurable encoding and delimiters via the Data Exchange framework. Read more
Include Column Headings — optionally output a header row in Variable Text and Fixed Text exports so receivers can identify columns without external documentation. Read more
XMLport and Codeunit payload generation — generate outbound payloads using your own XMLport or Codeunit, giving full control over output format beyond what Data Exchange Definitions offer. Read more
Message Body Viewer — the Message Details page now renders message payloads with automatic format detection, syntax highlighting, and a collapsible tree view for JSON and XML. CSV payloads are displayed as a formatted table with column headers. A raw/formatted toggle and expand/collapse controls are provided. Read more
Additional sample configurations — new samples covering CSV and JSON exports, including multiple-record processing examples. Access them through the setup wizard in a Cronus company.
Changed
Unlimited export records — removed the previous cap on the number of records that could be processed per export level, enabling large-volume batch exports without workarounds.
Snapshot — sync watermark now advances even when no messages are sent — the Synch. Modified On Filter now advances at the end of every sync run, even if the snapshot suppressed all exports. This prevents unchanged records from being re-evaluated on every cycle. See Sync Watermark Behaviour with Snapshot for details.
Export line numbering simplified — multi-level Data Exchange exports now assign sequential line numbers (1, 2, 3…) instead of using gap-based numbering (10000000, 10000, 100…). The old gap-based scheme was the cause of the record-count limitation on exports. The internal GetLevelIncrement function has been removed. These line numbers are only used internally during file generation and are not written to the output payload. If you have a custom subscriber that reads Data Exch. Field line numbers during export processing, see Export Line Numbering for details.
Default Mapping Codeunit — new Data Exchange Mappings for Integration Hub definition types now automatically set the Mapping Codeunit. If you previously relied on a custom mapping codeunit, you may need to update the mapping after creating it.
Snapshot watermark change notification — when you change the Synch. Modified On Filter on a handler that has active snapshot data, a message now reminds you that snapshot records are not cleared and previously suppressed records will remain suppressed until their tracked fields change.
Fixed
Data Formatting Culture — exports now correctly apply the culture specified on Data Exchange Column Definitions, producing correct decimal separators and date formats.
Blank dates export as empty strings — blank Date and DateTime values now export as empty strings instead of default values such as 0001-01-01 or 1753-01-01T00:00:00. If your receiving endpoint expects a specific default date for blank values, you may need to adjust the transformation rule or endpoint logic.
Added "Import Integration Handlers" and "Export Integration Handlers" actions on the "Outbound Integration Handlers" and "Inbound Integration Handlers" pages to import and export of integration handler configurations including the related tables and Data Exchange Definition defined on the handler(s).
Added the Delete Data Exchange Payload setting on inbound and outbound integration handlers. When enabled, Data Exchange payload records are deleted after processing to reduce table growth and storage usage.
Fixed
Resolved an error when exporting EFT files using Custom payload generation on outbound integration messages.
Vendor Purchase History Dimension Update report added to allow bulk updating of dimensions on posted purchase receipts, invoices, credit memos and return shipments based on the dimensions currently specified on the vendor card.
Fixed an issue where reversing predicted costs on a return shipment used the original receipt's posting date, which could fall in a closed Inventory Period and block posting. The reversal now posts in the return shipment's period. #94979
Subcontracting purchase order lines (where Work Center No. is specified) are now prevented from being assigned to consignments. Business Central does not support item charge assignment on subcontracting receipts. See Subcontracting Purchase Orders for details.
A notification is now shown when a predicted consignment line uses the Weight or Cubage assignment method but the item has no gross weight or volume set. The notification includes the affected item, assignment method, charge item, and template, and provides actions to open the Item Card or Item Units of Measure to correct the setup. This notification can be enabled or disabled per user via My Notifications.
The Missing Consignment notification (shown when predicted consignment lines exist but no consignment number is assigned to the source document) can now be enabled or disabled per user via My Notifications. It is enabled by default.
Changed
Updated help documentation to cover receiving items via Transfer Orders alongside Purchase Orders. See Receive Items.
Added a new integration event to codeunit 58211 (SalesPriceMgmt_AS_TSL): OnBeforeUpdateSalesLineBeforeCalculateSalesPrice. This was added to prevent price updates when over/under shipping using the Dual Unit of Measure capabilities.
Fixed an issue where the additional sales charge line was not being created when the document was submitted for approval. #94597
Added
Added Item Charge as a selectable line type on charge condition lines, allowing item charges to be used when defining additional sales charges. #94597
Exposed CreateDocChargesLines as a public procedure on DocChargesMgt_ASC_TSL, allowing external code to trigger charge line generation outside of the standard document release workflow.
Changed
Improved posting behaviour for partial shipments and invoicing. Charge lines are now aligned automatically with the posting action (Ship, Invoice, or Ship and Invoice) immediately before posting. You no longer need to set quantities on charge lines manually. See Shipping and Invoicing of Charge Lines for details. #94863
Percentage of Invoice Amount charges are now recreated per invoice cycle. When an order is shipped and invoiced in multiple runs, fully shipped-and-invoiced Percentage of Invoice Amount charge lines are removed and replaced with a fresh line for each new invoice. This keeps the order tidy and prevents zero-balance charge lines from accumulating. #94863
Manual override now respected at all workflow stages. When the Skip Adding Additional Sales Charges field is enabled on a document, the app will no longer add, update, or delete charge lines during release, approval submission, reopen, or posting. Previously, some workflow stages did not honour this flag. #94863
Enabling manual override on a document with existing charge lines now prompts to delete them. Previously, an error was raised when enabling the field if charge lines already existed. The app now asks whether to delete them; if you choose to keep them, the field reverts to disabled. #94863
Invoice-only posting after multiple shipments now raises a clear error. If you attempt to post an invoice-only run when a new Percentage of Invoice Amount charge line has been created but not yet shipped, the app raises an error explaining that you must post with Ship and Invoice together, and advises setting Qty. to Ship to zero on lines you do not want to ship. #94863
Added Word layouts for the Sales Invoice and Sales Credit Memo documents. The layouts closely match the existing templates and can be easily customised by users and administrators.
Added Unique EFT Reference generation to automatically assign a unique reference to each EFT payment line during file generation. The feature is configured separately for Direct Credit and Direct Debit on the EFT Setup page. Read more here.
Changed
Edit EFT References on Payment Journal in EFT Setup is now disabled and greyed out unless Banking Details in Payment Journal is enabled. Turning off Banking Details in Payment Journal while Edit EFT References on Payment Journal is enabled is blocked with an informational error message.
Independent Sales Processed and Purchase Processed status flags so the sales and purchase sides are tracked separately. The combined Processed flag (used by the API and to lock staging records) is now set whenever either side has been processed.
Allow for internal and external G/L Account No. setup on purchase documents to reflect internal expenses versus external Cost of Sales.
Changed
Purchase document creation no longer requires the sales side to be processed first; sales and purchase documents can be created in any order.
Fixed
A sales document could not be recreated after it was deleted while the purchase side still had a document (and vice versa). Each side now resets and frees only its own status flag, so either side can be deleted and recreated independently.
Cleaned up redundant code.
Set obsolete tags to unused actions for deprecation in next release.
Developer API - Temporary Storage: Made GetCurrentRowNumber() on TemporaryStorage_EI_TSL available externally so extensions can access the active import row number during processing. More details...
Developer Event - Global Settings: Updated the OnBeforeAddGlobalSetting event so ImportType is now available to subscribers, allowing extensions to apply import-type-specific logic when global settings are added. More details...
Added page extensions for Stock Keeping Unit Card and List pages with action to open the Procurement Unit for the same item, location, and variant.
Added page extension for LAX DP Forecast View with promoted actions for Procurement Unit, Forecast Adjust, Toggle Chart Visible, Item Usage, Forecast User Setup, and Usage Ledger Entries.
Replaced the Synchronise Modify boolean toggle with a new enum field that provides granular control over when record modifications are synchronised. Read more about Synchronise Modify.
Fixed
Fixed the session restart notification continuing to appear after selecting Don't show me again.