Business Central v26 — Reopen Finished Production Orders (Deep Guide) If you ever hit Finish on a production order and then notice a missing component, wrong lot, or time that “mysteriously” didn’t get posted… good news. In Business Central v26 there’s finally a built-in Reopen action for Finished production orders. You can reopen, fix what’s wrong (consumption, output, capacity time, tracking), and finish again — all on the same order so the audit trail stays clean. Heads-up: You generally get one shot to reopen a finished order. Posting dates and costing rules still apply like normal, so plan your corrections before you click. Why this matters (in real life) Before v26, any mistake after Finish meant awkward workarounds — undos, journals, or spinning a rework order. Now most “oops” cases are solvable on the original order without messy side effects. Finance will love you later. What Reopen actually does Changes a Finished order back to an ...
Posts
Comprehensive Guide to Flushing Methods in Business Central (Version 27) Flushing methods in Microsoft Dynamics 365 Business Central v27 determine when and how raw material inventory is deducted (consumed) for production. Configure them well and you’ll streamline shop-floor posting, keep on-hand stock honest, and keep WIP/costing accurate. What are flushing methods? They’re rules that tell Business Central when to post component consumption: manually by users, automatically at release (Forward), at finish (Backward), or automatically with a required warehouse pick (Pick+Forward / Pick+Backward). Where flushing shows up on orders When you create/release a production order, the item’s method copies to Production Order → Components. You can override per line. If you link components to operations via Routing Link Codes (RLC), flushing can occur per operation (Forward on operation start, Backward on operation finish). Manual flushing (maximum control) ...
Business Central v27: Locking & Blocking — Practical Guide + How to Use the Database Locks Page If you’ve seen “The record is locked by another user” in a busy system, you know how painful blocking can be. This post explains locking vs. blocking in Dynamics 365 Business Central v27 , what’s improved in recent versions to reduce contention, how to read and act on the Database Locks page , and the AL patterns I use to prevent most issues. Locking vs. Blocking (quick refresher) Locking is normal: BC (and SQL Server) protect data while a transaction changes it. Blocking is the wait that happens when your session needs a lock that another session holds. Deadlock is a circular wait; SQL cancels one transaction. BC primarily locks rows ; SQL can escalate to page or table locks if you touch many rows in one go. The shorter the transaction, the shorter the lock window. What got better in v27 (and around it) Tri-state locking (optimistic reads by default). Mo...
Understanding Database Indexes in Business Central (and How They Can Help You)
When I first started working with Business Central, the word “indexes” felt too technical for me — like something only developers or database admins cared about. But then I discovered the Database Missing Indexes page . At first, I thought it listed all the indexes that exist in the database. Later, I realized it’s even more interesting: it actually shows the indexes that don’t exist yet, but SQL thinks should be there . That page became a game-changer for me in understanding why some reports and pages are slow, and how I can help point my team toward performance fixes. What Are Indexes, Anyway? Indexes are like shortcuts. Imagine a giant cookbook with 1,000 recipes. If I want to find every recipe with “chicken,” I don’t flip through each page — I go to the index in the back. Databases work the same way. If I filter a table by Posting Date , an index lets the system jump straight to those rows instead of scanning everything. When no index exists for the filter, the system has to ...