What's new in version 2602.2.0.0

Shop Floor Production (BC) • Release Note • 5/27/2026 •

Enhancements/Modifications

With this release of the Aptean Shop Floor Production extension,

You can connect Shop Floor Production work instructions to a SharePoint library hosted in a different Azure AD tenant than the one running Business Central. A new SharePoint Tenant ID field has been added to the Work Instructions FastTab on the Shop Floor Production Setup page so that customers whose Business Central environment does not include SharePoint can still use the work instructions feature by pointing the app registration lookup to a corporate or partner tenant. Leaving the field empty preserves the existing same-tenant behaviour. For more information, see Set up work instructions in shop floor production.

The Tare Weight field on the Register Output page defaults to 0 for catch weight items, so operators can submit a registration without entering a tare value when no tare applies. Additionally, an integration event has been added so that partner extensions can override the default value when a customer-specific default is required.

A Pack Configuration column has been added to the Packaging section on the Production Order Details page. The column is conditionally visible only when at least one packaging row on the production order has pallet stacking data configured, and displays the number of shipping units and pallet breakdown in the format {No. of Shipping Units} ({Number per Layer}×{Number of Layers}) — for example, 48 (6×8). Rows without stacking data show a blank cell. For more information, see View the production order details.

Extension dependencies

The following extensions have been updated in this release to support the new or enhanced features:

Extension Name	Minimum version requirement	Extended functionality
Aptean Packaging for Food and Beverage	2602.2.0.0	Required to surface pallet stacking values (No. of Shipping Units, Number of Layers, Number per Layer) on the Production Order Details page.
Aptean Integration Layer for Food and Beverage	2602.2.0.0	Required to transfer the new pallet stacking fields from the Aptean Packaging extension to Shop Floor Production.

UI/UX changes

The following UI/UX changes have been made in this release.

The Pack Configuration column has been added to the Packaging section of the Production Order Details page.
The SharePoint Tenant ID field has been added to the Work Instructions FastTab on the Shop Floor Production Setup page.
The Ending Date Time field has been removed from the Shop Floor Production Status page.
The Starting Date Time field on the Shop Floor Production Status page has been renamed to Last Status Change.

Resolved issues

The following issues have been resolved in this release.

ID	Description
357291	The system fails to populate the Ending Date Time field on the Shop Floor Production Status page after a production order operation is completed and the production order is set to Finished, leaving the column blank even though the entry shows the Starting Date Time correctly.
365247	An error occurs when posting Shop Floor Production registrations if orphaned Item Journal Line records remain in the journal batch from earlier failed registrations on the same production order line, which prevents subsequent registrations from being posted. Additionally, warehouse put-aways are not generated and license plate logic does not run consistently when the Prod. Output Whse. Handling field value on the location is not set to Warehouse Put-away and no license plate is in scope.
365565	The system does not validate the report ID before executing print requests received from the Shop Floor Production app, which allows reports outside the Shop Floor Production allow-list — including reports that perform data processing — to be triggered from the front end.
365940	The system fails to honour the item-level Lot No. Per setting in three scenarios on the Register Output page. A specific sequence of edits on the Shop Floor Production Setup page leaves an item with Lot No. Per set to Production Order even when Output Lot Preview is None, bypassing the intended validation. Additionally, on a production order with co-products that share a single SFP order, the Generate New Lot action on the Register Output page derives its visibility from the main production order line rather than the co-product item being output. Furthermore, switching items on the Register Output page causes the lot number to increment for items with Lot No. Per set to Production Order, even when a prior output already established the lot for the production order.
367208	The system does not populate a default value in the Tare Weight field on the Register Output page for catch weight items, which requires operators to manually enter a tare weight before the registration can be submitted.
367771	The system displays the total lot quantity in the Inventory field on the Register Input page when an operator scans a license plate for a component with both Lot Specific Tracking and Package Specific Tracking enabled, instead of showing the quantity on the scanned license plate.
370976	The system fails to apply work instruction association filters to the work instruction count displayed on the Production Order Overview tile, which causes the tile to over-report the number of instructions actually available to the operator. Additionally, work instruction association filters are not applied on the Work Instructions screen in the non-Graph version of Shop Floor Production, so operators see instructions that should have been excluded by the active association.
362839	The system displays an incorrect value in the Registered Quantity field on the Shop Floor Production app when an item with an alternate unit of measure posts consumption in a decimal alternate unit of measure value. This issue occurs because the unit of measure conversion factor is derived from rounded quantity values on the production order component line instead of the exact factor from the Item Unit of Measure table. Additionally, the Consumption Correction dialog displays quantities in the base unit of measure instead of the posting unit of measure, causing a posting error when you save the correction.