DEV Community: Insight Works

Capacity-Aware Delivery Dates in Business Central: Extending Capable-to-Promise with MxAPS

Insight Works — Tue, 20 Oct 2026 15:57:41 +0000

When a customer asks when a made-to-order item can arrive, the answer depends on more than inventory. It depends on machine capacity, materials, and the work the plant has already scheduled.

That gap sits between the order promising tools Business Central provides and the capacity reality of a manufacturing plant. The questions below walk through how standard promising works, where it stops, and what changes when a finite capacity scheduling add-on feeds capacity and materials into the same process.

Where does standard capable-to-promise stop for made-to-order items?

Standard capable-to-promise in Business Central calculates the earliest date an item could be produced, purchased, or transferred. For made-to-order and assembled items, the delivery date also depends on the plant's existing production commitments. That production context is the piece a finite capacity scheduling add-on brings into order promising.

How do available-to-promise and capable-to-promise split an order?

Available-to-promise looks at unreserved inventory and planned receipts to see what can ship from existing supply. Capable-to-promise handles only the remainder, the quantity not covered by stock or scheduled orders, and asks when it could be produced, purchased, or transferred. Both checks run from the Order Promising Lines page on the sales order.

What happens in Business Central when you accept a promised date?

In Business Central, order promising fills two fields. Planned Delivery Date shows when the customer can expect the goods, and Earliest Shipment Date shows when the order can leave your facility. Accepting a capable-to-promise date creates a planning line and a reservation entry, so the supply behind that promise is already in motion, not a date typed into a field.

How does a capacity-aware add-on change order promising?

MxAPS, a finite capacity scheduling app for Business Central, extends the existing Sales Order Promising feature instead of replacing it. When the order processor runs promising, the tool assesses production capacity and material requirements for the items on the order. The resulting date reflects what the plant can produce, and the processor never leaves the sales order.

What has to be in place before capacity-aware dates are reliable?

Capacity-aware promising relies on the same Business Central setup as the scheduling app itself: routings, work centers, and machine centers kept accurate and assigned to production cells. That setup is the plant model the app uses to schedule production orders forward against machine capacity, following the scheduling rules each manufacturer defines.

Which items actually need a capacity check?

Stocked items usually do not need a capacity check in Business Central. Available-to-promise already confirms whether they can ship from inventory or scheduled receipts. The capacity view earns its place with make-to-order and assemble-to-order items, whose ship dates hinge on free production capacity, not on stock already in the warehouse.

Originally published on the Insight Works blog.

How Do You Run One Business Central Warehouse Setup on Android, Windows, and Chromebooks?

Insight Works — Wed, 14 Oct 2026 19:16:16 +0000

Picture a small request from a warehouse supervisor: add a lot number column to the pick screen. In a warehouse where every device runs the same operating system, that is one edit. In a warehouse where pickers carry Android handhelds, receiving works from a Windows PC, and shipping uses a Chromebook on a forklift mount, that same edit can turn into three.

This article walks through how a Business Central warehouse app can treat a mixed fleet as one environment, with a single configuration that every device reads and screen views matched to the people using them.

Which screen view works best for each warehouse role?

The deciding factor is where a worker's attention goes. Pickers moving fast confirm lines by item picture in Rich Tile View. Forklift operators, putaway associates, and quality inspectors use Directed Card View for one task per screen. Receiving clerks and supervisors at Windows PCs work in Compact Grid View to reconcile lines or spot exceptions.

How do the three warehouse screen views differ?

Think of them as glance, focus, and scan. Rich Tile View shows an item picture, description, bin, lot or serial, and quantity per tile, with row color rules. Directed Card View presents one record in full detail, with factboxes for comments and the item image. Compact Grid View lists every line in a sortable list with a footer detail panel.

Why does maintaining a separate setup for each operating system cause problems?

Each platform-specific setup is another copy of the same screens that IT must edit, test, and keep aligned. When a supervisor requests one new column, a three-platform warehouse needs three matching changes. Miss one, and a picker on Android sees a different screen than a clerk on Windows, which invites errors exactly where accuracy matters most.

What does a single warehouse configuration cover in Business Central?

With Warehouse Insight, you define menus, applications, column layouts, workflows, and overrides once, inside Business Central. Each device loads that setup when a worker signs in, whether it runs Android, Windows, or Chrome OS. A new lot number column becomes one edit that every handheld, desk PC, and forklift tablet reads at the next sign-in.

What happens when a worker switches between a desk PC and a handheld?

Very little. A receiving associate might scan pallets on an Android handheld at the dock, then check a purchase order on a Windows laptop at a desk. Both devices read the same Business Central setup, so the screen looks familiar on either one. Each device configuration sets OS and view, so no role needs a separate product or license tier.

Do I need to replace existing devices to standardize on one warehouse app?

It can come to that. A warehouse management system limited to one operating system leaves devices on other platforms without a role, so the warehouse shelves a Windows receiving PC or a Chromebook already on a forklift mount and buys replacements. Warehouse Insight runs on Android, Windows, and Chrome OS, so existing hardware stays in service without a separate procurement round.

Disclaimer: This content is shared for informational purposes and is not promotional.

Read the full blog

Rebuilding Dynamics GP SOP-to-POP Links in Business Central

Insight Works — Fri, 02 Oct 2026 22:15:34 +0000

Picture the first morning after a GP-to-Business Central cutover. A buyer opens an imported purchase order for a customer-specific item and finds nothing on it that points back to the sales order it was raised to fill. Both documents came across intact. The connection between them did not.

That gap is structural, not a migration bug. GP and Business Central model the sales-to-purchase relationship in different ways, so restoring it means understanding both models before writing a single field.

Which GP orders need their SOP-to-POP link migrated?

Only orders open at cutover. Consider a drop-ship order your team fully invoiced last quarter: its commitment is complete, and nothing in Business Central will act on it. Carrying that link forward adds mapping work with no payoff. Scope the effort to open sales and purchase pairs, the only ones planning and posting logic needs to see.

What does Business Central use instead of GP's link?

Two features: special orders and drop shipments, each with separate fields. A special order fills Special Order Purchase No. and Special Order Purch. Line No. on the Sales Line, mirrored on the Purchase Line. A drop shipment sets its own flag and uses Purchase Order No. Mislabel a GP drop-ship as a special order, and the receipt won't auto-post.

Why don't RapidStart configuration packages restore the link?

RapidStart works one table at a time, which is fine for records that stand on their own. The link is a different problem: it requires writing a purchase line number into a sales order after both documents exist in Business Central. Think of it as a join, not a load. RapidStart has no step for that cross-record update.

What sequence rebuilds the link after migration?

Import Export PowerTool handles it as a second pass. Import open GP orders first so every line has a real Business Central document and line number. Then update Sales Line and Purchase Line with the paired numbers, and set the Purchasing Code plus the Special Order or Drop Shipment boolean. Reversing that order leaves nothing to point at.

Why test the update pass in a sandbox before production?

Import Export PowerTool writes straight to document lines, outside the interface users normally work in, and field types matter. Special Order Purchase No. and Special Order Sales No. are Code[20]; paired line numbers are integers. Picture a sales line whose link points at another customer's purchase line: it looks connected on screen but won't behave that way.

Which GP fields help verify the migrated links?

The ones GP itself used to approve the match: item number or vendor item number, unit of measure, and site ID, plus customer ID and ship-to address for drop-ship orders. Export them with every open line. If a migrated pair fails to reconcile, those fields show whether the original match held.

Disclaimer: This content is shared for informational purposes and is not promotional.

Read the full blog