In this series of bimonthly blogs, Western Computer shares our expertise with tips and tricks to help users work more efficiently in Microsoft Dynamics 365 Business Central. Based on our more than 35 years in business—with 1,250+ solution implementations, including more than 300 in the cloud—we share the expertise we have accumulated to enable users to work as proficiently as possible. You can also subscribe to these blogs in our LinkedIn newsletter. 
If your organization relies heavily on warehouse posting, such as through multiple scanning devices or intensive warehouse activities, a new feature introduced in Business Central 25, that is slated to become mandatory in Business Central 27 (scheduled for release in October 2025) could significantly impact your processes. Designed to address concurrency issues during warehouse posting, this feature introduces changes to how Warehouse Entries are created and viewed.
While the feature primarily impacts system processes and not day-to-day operations for consultants or end users, understanding its implications will help you adapt effectively. If your warehouse posting system is customized, this can also help you getting ahead of the game and adjusting your extensions before the feature is mandatory. Let’s dive into what’s changing and how to prepare.
What’s Changing in Warehouse Entries?
Currently, when you post warehouse transactions, all the related Warehouse Entries are recorded sequentially in the Warehouse Entries table for each transaction. This makes it straightforward to trace activities in the system, as entries appear in order by Entry No.
With the introduction of the new feature, however, this process will no longer be strictly sequential. Although the concepts of Warehouse Registers and Warehouse Entries remain, entries from multiple transactions may now be intertwined.
When you sort by the Entry No. field, transactions might appear “out of order,” but rest assured, the data will still be accurate and consistent.
Why the Change?
This update addresses the challenge of table locking during concurrent warehouse transactions. Previously, when multiple users posted warehouse activities, the system locked both the Warehouse Registers and Warehouse Entries tables, ensuring that numbers were assigned sequentially. However, this locking process could delay or block other users from completing their tasks.
With the new feature, Business Central uses Sequence Numbers to assign entry numbers, allowing simultaneous transaction postings. This improvement eliminates bottlenecks but changes how entries are displayed in the system.
Key Considerations for Your Team
-
Training Users:
If your team is accustomed to viewing the Warehouse Entries table in sequential order to trace activities, you’ll need to train them on the new behavior. Transactions may appear “out of order” but are still traceable through other identifiers, such as Warehouse Registers.
-
Customizations and Extensions:
If you’ve implemented or developed modifications that rely on consecutive entry numbers, these may no longer function as intended. Review your customizations to ensure compatibility with this change. If necessary, disable the ConcurrentWarehousingPosting feature key until updates are made.
-
Process Adjustments:
Ensure your operational consultants and end users understand that the changes won’t affect the accuracy or reliability of Warehouse Entries, even if the display order differs.
Best Practices for Managing the Change
-
Use Warehouse Registers for Tracing Activities:
Each Warehouse Register links directly to the first and last entry numbers of the corresponding transaction. Leverage these records to trace warehouse activities accurately.
-
Test in a Preview Environment:
The feature is already available in any BC 25 environment. Use this opportunity to familiarize your team with the new behavior and identify any potential issues with extensions or workflows.
-
Document Updated Processes:
Ensure that any documentation related to warehouse processes reflects the changes. This will help minimize confusion and ensure a smooth transition.
This new feature in Business Central 25 is a step forward in optimizing concurrent warehouse posting, reducing table locks, and enabling more efficient operations. While it requires adjustments to how you view and manage Warehouse Entries, the benefits of smoother transaction handling are substantial.
In some scenarios, it may be beneficial to temporarily disable the ConcurrentWarehousingPosting feature key, especially if:
-
You rely on customizations or extensions that depend on sequential entry numbers.
-
Your processes involve table locking that could be disrupted by the new sequence number approach.
For more details, refer to the official Design Details: Creating Warehouse Entries on Microsoft Learn.
By preparing your team, reviewing customizations, and leveraging tools like Warehouse Registers, you can ensure a seamless transition and continue to maintain operational excellence.
For more tips and tricks on working with Business Central, stay tuned to our updates. Western Computer’s experts are here to help you navigate changes, optimize processes, and achieve your goals.
About the Author
More Content by Marcelo Borges