When it comes to warehouse operations, efficiency and accuracy are non-negotiable. Dynamics 365 Business Central (2024 release wave 2) has introduced significant changes in handling warehousing, specifically in enabling concurrency during warehouse posting. If your business relies on Business Central for managing warehouse processes, this update could streamline operations and improve efficiency.

But what exactly does this “concurrency” mean for your warehouse setup, and how can you  maximize it?

This blog will walk you through how warehouse posting used to work, the changes introduced, and what developers or partners should keep in mind when implementing these updates.

How warehouse posting previously worked

 

 

 

 

 

 

 

Watch the short 5-minute Microsoft video on BC warehousing – it’s a little technical, so if you’re not into “code” you might just want to keep reading the blog. 

Prior to the update in Dynamics 365 Business Central, warehouse posting essentially operated on a single-user model. This meant only one user could post entries at a time.

Here’s the flow of how it traditionally worked:

  • The sequential process: A single user would lock the warehouse table, retrieve the most recent entry (using `Find Last`), increment the entry number, and insert new records sequentially.
  • Orderly ledger updates: Since only one user could post at any time, the entries were generated in consecutive order. The Warehouse Register recorded which entries belonged to a specific register (from entry “A” to entry “B”).

While this process ensured consistency, it also caused bottlenecks. For example, in the case of high-volume transactions, users often found themselves waiting for their turn, subsequently slowing down critical warehouse operations.

What’s new?

With the 2024 release wave 2, Microsoft has redefined warehouse posting to allow for concurrency. Put simply, multiple users can now post warehouse entries simultaneously. This change aims to boost efficiency in environments where warehouse transactions are frequent.

Here’s how it works now:

  1. Number sequences for entry numbers

Instead of performing a `Find Last`, the system now uses number sequences to assign unique entry numbers. This allows multiple users to post entries simultaneously without overlapping.

  1. Associating entries with registers

A new field has been introduced to explicitly associate each warehouse entry with a specific Warehouse Register. When entries are added, this field ensures clarity about which register the entry belongs to.

  1. New `Insert Record` function

The new posting flow introduces a function called `Insert Record`. This handles posting retries in cases where conflicts arise—especially if legacy processes (like using table locks and sequential insertion) are still active for certain users.

Addressing parallel posting conflicts

One of the biggest hurdles with concurrent posting is avoiding locking conflicts when two users post entries for the same item and location at the same time. Version 25 reduces the risk of this happening by introducing a “SIFT bucket number”:

  • This semi-random number (ranging between 0 and 4) acts as an additional column in the index, reducing the chances of conflict in scenarios involving multiple inserts into the same item-location combination.

Maintaining legacy systems without overhauls

To prevent disruptions during upgrades, version 25 allows users to drill down using filters that distinguish before and after-update records. This filtering mechanism ensures compatibility with older data.

Why these changes matter

While this might sound highly technical, these updates are critical for developers, partners, and businesses using Business Central. Here’s why you might care:

  1. Enhanced efficiency

Allowing multiple users to post simultaneously improves processing speed, especially for businesses handling high transaction volumes. No more bottlenecks caused by a single-user posting policy.

  1. Streamlined data processing

The new numbering system and register association ensure that entries remain organized and conflict-free, even with simultaneous postings.

  1. Easier upgrades

Microsoft has included options to disable or adapt these features via Feature Keys, allowing businesses to evaluate these changes without fully committing to them during the transition phase.

 

 

 

Take advantage of concurrency in Business Central

The introduction of concurrency in Dynamics 365 Business Central ensures smoother, faster warehouse operations by removing the single-user bottleneck. As a business scales, this feature can significantly enhance productivity and align your systems with modern warehousing demands.

Still unsure how to implement this new functionality? Or concerned about aligning your existing extensions? CAL Business Solutions has a team of experts to help you with your Business Central needs. Contact us today.

Do you wish to get more out of using Business Central? Read other articles from our blog to stay in the know.

By CAL Business Solutions, Connecticut Microsoft Dynamics GP / 365 BC & Acumatica Partner, www.calszone.com