We have a Ticket regarding massive performance issues using BC SAAS.
Our customer posts about 1000-4000 sales lines using serial numbers, affecting that even creating or later booking/register a warehouse shipment / warehouse pick takes serveral hours, while in the meantime other users are unable to do their work in BC.
In consultation with the Microsoft support team they identified that several functions can be optimized, the main reason for the slow behaviour is, that BC handles each serial number as a separate sale line by checking availability, bin content, warehouse entries etc.
As we have been informed, this behaviour hasn´t been reported by other Microsoft partners, which we cannot comprehend.
We hope to be able to uncover further cases in this way and to push this topic in priority.
Comments
probably it's the time for MS to review posting procedure and all related table (Ledger Entry at first) to reduce lock, allow fast bulk insert and finally really increase performance.
I presume that some performance issue are not related to infrastructure, scaling it's not the solution.
Category: Warehousing
This is super important!
I have a new customer that uses serial numbers. posting one shipment row with 4 000 pcs (without Automatic Cost Posting , Expected Cost Posting, Automatic Cost Adjustment) takes between 4-15minutes (!).
A warehouse receipt with 100 lines took hours to post.
This needs a rework if BC should be a viable and optimal system for these types of customers and processes.
Category: Warehousing
Performance is important by posting!
Category: Warehousing
Performance is really important. It is an important factor that can persuade other customers to use the cloud version.
Category: Warehousing