Dynamics 365 Supply Chain Management

The "Change BOM item" feature for item replacement in the production BOM doesn't enter the operation number correctly.

The feature allows you to indicate the old item already present in the production BOM and the new item to be replaced. The system then resets the quantity of the old item in the BOM, inserts the new item into the BOM but associates it with the first operation number of the route and not with the operation number to which the old item was associated.

The expected behavior is that the system associates the new BOM line with the same operation number with which the original replaced item was associated.

Currently, when a sales order contains line items with mixed statuses, such as "Open order" and "Delivered" and the item price is updated, running the price recalculation job based on the "Open order" status still causes the system to recalculate prices for all lines within the order. This behavior is inefficient and may result in unintended price updates for already delivered lines.

The price recalculation logic should be improved to strictly apply the recalculation only to sales order lines that match the specified status filter.

In a buy-to-order process, some clients utilize the "Create Purchase Order" or "Direct Delivery" function directly from a sales order. In such cases, the sales price should be dynamically calculated based on the actual purchase price from the generated purchase order, combined with a predefined margin. If the purchase price in the PO is modified, the corresponding sales price in the sales order should also be updated accordingly to reflect the change.

it would be ideal to have the same vendor consignment / inventory owners functionality on the sales side for when holding customer owned inventory in the warehouse and needs to be used or consumed it in a process change inventory ownership from customer to the corresponding

If a user needs to run the same test twice within a single quality order—such as using different specification limits—the test must be added to the quality order twice. This is allowed as long as each test entry has a unique sequence number. However, the system currently auto-assigns the same sequence number as the first test, which results in a duplicate record error. As a result, users must manually adjust the sequence number to avoid this issue.

We have observed that users must be explicitly assigned either the Maintenance Worker or Maintenance Requester role in Dynamics 365 to authenticate and access the Power App. Assigning a custom role, even one configured with the same security privileges and duties, results in authentication failure.

Other standard roles, such as Maintenance Manager and Maintenance Clerk, also fail to grant access. This leads us to believe that the app's authentication logic is hardcoded to recognize only the Maintenance Worker and Maintenance Requester roles.

We are requesting Microsoft’s assistance in resolving this issue or let us know the reason behind using the role specific validation. Ideally, the app should validate user access based on assigned security privileges and duties, rather than fixed role names. This would allow organizations to maintain custom roles without sacrificing functionality.

Enabling the "Select voyage cost" functionality from Pending vendor invoices in D365 F&O would streamline workflows by allowing users to allocate voyage costs earlier in the process, reducing manual steps and rework. It would enhance cost allocation accuracy, improve invoice matching and validation, and provide more timely financial visibility. This early integration supports better inventory valuation, budgeting, and decision-making, while also aligning more effectively with the Landed Cost module for comprehensive cost tracking.

The system doesn’t respect the Unit price set on the Original SO in case the Confirmed ship date is modified on the Intercompany SO in Currency exchange rate scenario leading to incorrect invoicing.

Production route update - performance after change

The route circularity check is always executed when one of the fields in the production route is changed, even if nothing changed in the route sequence itself and no operations were added or deleted.

The check itself is slow, almost 1 second per operation.

Proposed change:

Only execute the check when a new operation is added, or an operation is deleted or when the field Next operation changes. (E.g. by storing operations ProdRoute.RecId + Next operation in a map when the form is opened, and check whether this is changed when the form is closed)

Or make the circularity check much faster.

Repro:

Create production order for item D0003, and press button Route.

Change the run time for the first operation from 1 hour to 0.9 hour.

Close the form.

Wait 4 seconds until the Processing operation - Update route message disappears.

This check is not very fast, ca. 1 operation per second.

Issue Description:

Today there’s an inconsistency in how “best-before date” is evaluated for batch-controlled items:

• MRP/ATP validate shelf life based on the sales order ship date.
• Warehouse reservation (Release to warehouse or manual “Batch reservation”) validates against the requested receipt date.

This mismatch leads to practical issues: ATP can show availability, but when attempting to reserve, the Batch reservation dialog returns no selectable batches (blank grid) because the receipt date check is stricter than the ship date logic used by ATP/MRP. This creates confusion for users and blocks standard flows (especially FEFO/shelf-life scenarios with transport days or sellable days).

Proposed Idea:

Add a configurable parameter to control which date the reservation engine uses for best-before validation, so customers can align Warehouse reservation with their ATP/MRP logic.