Dynamics 365 Supply Chain Management

No infolog message displayed when asset states changed for a 'Active' asset states from Asset management > setup > Assets, even though Assets are linked with 'active' and they are in use.

Expected:

Expected to atleast display infolog message while user set 'Active' radio button to 'NO' from lifecycle state (Asset management > setup > Asset). 

In Module "Procurement and Sourcing" there are two reports "Item/vendor statistics" and "Vendor/item statistics". Currently these two reports only allow to evaluate the data on the Item level. Product Variants and Dimensions are not taken into consideration. For customers who use product variants, these two reports are not useful because the data is aggregated on the item and not displayed on the product variant level.

Suggestion: as an Option (in the report dialog) make it possible to print the reports presenting the data based on the product variant/product dimensions.

In high-volume consignment operations, the current D365 behavior of automatically creating a Purchase Order (PO) for each ownership change journal entry leads to significant operational overhead. For example, our organization processes ~2,000 SKUs daily, resulting in over 4,000 POs per month solely due to ownership changes. This volume creates:

• Excessive transactional load
• Manual reconciliation effort exceeding 1,000 person-hours/month
• Operational cost impact of ~$30,000/month
• Compliance risks due to workaround dependencies

Suggested Enhancement:

Introduce a configurable option to suppress PO creation during ownership change journal posting. This could be implemented as:

• A journal-level toggle (e.g., Create PO: Yes/No)
• A system mode that allows periodic or consolidated PO generation based on vendor/date/SKU rules

Functional Requirements:

• Ownership change posts inventory and ledger updates without triggering PO creation
• Optional batch process to generate consolidated POs referencing source journals
• Maintains inventory valuation and audit trail integrity
• Backward compatibility with existing automated flows

Business Justification:

This enhancement would reduce administrative overhead, improve scalability, and support compliance in consignment-heavy environments. It aligns with real-world operational needs and would be a valuable addition to D365’s flexibility.

When performing 'Create items' to calculate average issues per month and standard deviation, the system in Dynamics 365 Supply Chain Management includes inventory transactions with the status Deducted and sold in the Issue status. Goods in transit records that are sold to the transit warehouse are included in this calculation

The inclusion of goods in transit in safety stock calculations is by-design in Dynamics 365. Safety stock is calculated using all historical issue transactions, which includes both external usage and internal inventory movements (such as goods in transit). The calculation logic is built to consider all inventory movements, including goods in transit.

Currently, there is no native configuration to exclude goods in transit from these calculations. 

The issue is that an inbound transaction is used when calculating safety stock. In real life that will mean to big safety levels, higher inventory value and potential lots of stock getting scrapped because there is no usage for it.

Appreciate if we can get this fixed by Microsoft.

Currently in Dynamics 365 Finance & Operations, once a costing sheet node has posted transactions, it cannot be deleted or disabled. This creates challenges for companies that want to simplify or update costing sheets after going live, particularly when indirect costs are applied at a detailed level (e.g., per item).

Customers face performance issues when the costing sheet evaluates every node during production journal posting, even nodes that are no longer relevant. Existing options, such as setting the node rate to zero, do not prevent the system from processing the node, and there is no supported way to make a node “inactive” for future calculations.

The inability to deactivate or replace nodes safely leads to limited flexibility, potential performance bottlenecks, and extra complexity for ongoing projects. A solution that allows safe inactivation or expiration of costing sheet nodes would improve system performance, simplify cost management, and reduce operational overhead.

When creating or editing a Product Relationship Type in Dynamics 365, entering a Friendly name with spaces directly in the main form does not persist after saving the system automatically removes spaces and reverts to the internal name. Currently, users must open the Translation form to maintain the desired text.

Business Impact:

This behavior affects usability and can slow down data entry, especially in environments with many product relationships. It also introduces inconsistency and may impact user confidence in the system, as the expected result is not achieved from the main form.

Proposed Improvement:

Allow users to enter and save Friendly names with spaces directly from the main Product Relationship Type form without needing to open the Translation form. This would improve usability, reduce extra steps, and enhance user trust in the system.

Purchase requisition prepared by the worker has been approved by the correct manager in line with the correct hierarchy.

In the form "Purchase requisitions for all my reports" a manager should view only the PurchReq of his direct report.

On the contrary, we encountered an error since another manager can see the PurchReq of a worker who is not a worker of his team.

Digging deep, the current employee was once assigned to that manager in the past back in 2022

We have found a similar issue reported before in bug#967030

The workaround is to delete and adjust the data in the PURCHREQREQUISITIONERFILTER here we have 2 Main Columns ORIGINATOR (Manager), REQUISITIONER (Employee Reporting to Manager)

However, we are looking for a fix from Microsoft to adjust this as the mentioned above is only a workaround

When consuming items on a work order in the Asset Management mobile app, it is currently only possible to view the item number under the Spare parts and Asset BOM tabs.

However, under the All items tab, both the item number and item name are visible. We need the ability to view and search by item name also under the Spare parts and Asset BOM tabs.

This improvement would make it significantly easier for technicians to identify and select the correct spare parts, since navigating through the All items tab is time-consuming and not user-friendly during daily operations.

When changes are made at the line level of a purchase order—such as adjustments to the unit, warehouse quantity, or site—the system recalculates the line's Requested ship date and Requested receipt date based on the current system date, rather than retaining the original header date.

In this case, the customer initially created a sales order for 90 units, specifying a requested ship date of November 30, 2025 and a requested receipt date of December 1, 2025. After running Master Planning, the system generated a planned purchase order dated November 28, 2025, which aligned with the sales order requirements.

Later, the customer increased the sales order quantity to 100 units and re-ran Master Planning. The system once again generated a planned purchase order dated November 28, 2025, correctly reflecting the updated quantity.

However, after applying the Apply Actions function and firming the planned purchase order, the resulting firmed purchase order unexpectedly displayed a Requested ship date and Requested receipt date of the creation date for example October 1, 2025 .

Currently, the system allows users to create transactions with extremely large quantities in both the Warehouse App and On-Hand Adjustments. This can lead to data inconsistencies, calculation errors, and inventory closing issues, especially when quantities exceed the limits that D365 and Excel can handle.

This idea proposes adding validation limits to prevent users from entering excessive quantities, ensuring system integrity and reducing the risk of errors. Implementing this would help avoid the creation of “invalid” transactions and minimize the need for manual corrections or workarounds, improving operational safety and confidence for users.