Dynamics 365 Supply Chain Management

Currently, when using Electronic Reporting with the “Printer” file destination, only one copy is printed by default—even if Print Management is configured to print two copies. This limitation is causing operational inefficiencies for customers who require multiple physical copies of reports (e.g., Container Content Excel report). - This also been raised and responded to the product group team in issue number:

Proposed Idea:

Enable support for printing multiple copies directly from the “Printer” destination in Electronic Reporting, respecting the number of copies set in Print Management. This would eliminate the need for manual reprinting and improve workflow efficiency.

We are running into the “price amplification” effect with Moving Average costing in Dynamics 365 F&O. This is a well-known limitation whenever:

• Negative financial inventory is allowed,
• On-hand quantity reaches zero (or below), and
• The system tries to post an issue transaction without a proper moving average base → resulting in inflated or distorted costs.

Microsoft’s reply ("by design") basically means they aren’t considering it a bug, but a structural limitation of moving average valuation.

We need some functionality to overcome this design limitation

This request is to extend the information presented in the "The operation is taking a long time to process, click Wait to keep waiting for it to complete" dialog, often appearing when long-running processes are executing in interactive mode. The context that this specific request is being issued is when large volume shipments (>3K containers or more) are confirmed, often executing for several minutes.

Typically, when the functional users click the presented "Wait" option, there is often no response on the All Shipments form (whsshipmenttable form) unless the user attempts to close or refresh the form, at which point the message will reappear.

Our user community has requested more feedback to be presented on the form, such as a progress dialog - anything that can provide at least some cosmetic visibility that the triggered process is doing something.

Right now, a company's employee has to first re-submit a PO to the VCP, for a vendor user to be able to make changes to a PO.

In our projects business process, after initial confirmation, it is usual that a vendor makes updates to the expected (ex factory) delivery date and /or actual quantity to be shipped.

These changes should be reviewed by company employee, just like with changes for first submitted po.

nice to have: allow to set by vendor, if the vendor is allowed to submit changes to already confirmed PO's.

suggestion: tie in this change with the existing Supplier Communication Agent procedures, where an employee has to review the suggested PO changes from vendor emails.

In case a company submits many small PO's to their vendors, a vendor has to click through all orders and confirm one by one.

The request is to allow a multi-select functionality so the vendor user can confirm multiple PO's at once.

I suggest to add column for "reverse shipment confirmation" YES or NO in the load form to trace the no. of loads reversed.

After posting picking list from Production order (where status was ‘Started’ and Remaining status was ‘Material consumption’), User update production order status to ‘Created’ from started (since order was cancelled by customer and no more Production order to run). Since no more this production order needed, user delete the production order manually. 

Issue - After deleting the Production order when user generate MIP on past date (when Production order was not deleted), system shows no data.

Expectation -

System should show data since MIP generated on past date when production order was not deleted

In the released product default order setting you have inventory quantity settings (multiple, min, max & standard order quantity) per site.

Within our sites we have multiple production locations. But the production order qty for the same product can be different for the production locations within 1 site. It would be very useful if we could set these quantities per warehouse so that the masterplanning proposes correct production order with correct quantities.

We now had to move these production locations to the leven of sites and that causes other issues and extra work.

User is scheduling setup and process jobs for multiple orders using same resource from dispatch form.

When trying to schedule using re-schedule single jobs, only process jobs are moved and setup job is not rescheduled even while using hard link which breaks the expected sequence.

This was reported through LCS#1050322 and was concluded as feature limitation since 'Reschedule single job' does not consider other hard linked jobs for the same operation.

Hence, this idea is to consider design change request or adding additional functionality in the future.

Issue Description:

when creating a sales order line, the SalesPrice field derives its value from the InventTableModule table. This table does not store prices based on product configurations, which results in the system always pulling the latest activated price by default.  

This behavior causes challenges for businesses that manage pricing at a more granular level, such as by specific product configurations. Unlike SalesPrice, CostPrice handling references InventItemPrice, which correctly accommodates configuration-specific details.  

Additionally the issue is also effecting work breakbench structure when retriving cost price and sales price for product varients, as has been addressed in issue 1056538 and 974989

As a result, organizations face the following issues:

• Incorrect pricing applied on sales orders when multiple configurations exist.
• Extra manual effort to update pricing on sales lines.
• Inconsistent behavior between SalesPrice and CostPrice logic, leading to confusion and additional custom development.

Proposed Idea:

Introduce an option in standard functionality for the system to pull SalesPrice values from InventItemPrice table, similar to CostPrice behavior, so that product configuration-based pricing is respected out of the box.  

Alternatively, provide a configuration parameter or feature in pricing setup that allows businesses to choose the source table (InventItemPrice vs. InventTableModule) for SalesPrice retrieval in sales documents.