Dynamics 365 Supply Chain Management

Customer has extended at a customer our ItemIdBase data type from 20 to 60 characters.

It all goes fine within D365FO until we try to Release a sales order to the warehouse for an item number with a length of 60 characters.

However, as this is a platform kernel issue, PG concluded that it is less likely to be changed from code point of view.

Customer posted on Yammer to raise awareness in case multiple users can benefit from this additional functionality and we have raised this idea for the same to be tracked internally.

The new Advanced Quality Mangement feature made available with 10.0.44 offers the ability to create Quality orders via Quality associations based on Transfer order Event types. We require the ability to restrict Quality order creation based on the Applicable warehouse type, i.e. we only require Quality orders created for Warehouses that are enabled for Quality management for warehouse processes. Currently this option is only available for a Quality association with a Reference type of Purchase and we would like to request this is also made available for a Quality association with a Reference type of Transfer.

Issue Description:

When changing the currency at the header level for a sale order with a Sales Agreement linked via Product Value Commitments, the system will removes the link to the Sales Agreement and retains the discount. Afterward, it is not possible to re-establish the link to the Sales Agreement. In comparison, Product Quantity Commitments are unaffected by a currency change because they are based on units, not monetary value. The current behavior seems to be a design limitation in how Product Value Commitments handle currency changes as per product group feedback on issue number 1037192.

Idea:

Provide an option or enhancement to retain the Sales Agreement link even if the currency changes, or allow re-linking the order to the Sales Agreement after the currency change. This enhancement would accommodate real-world scenarios where exchanging the currency or making corrections should not permanently invalidate the monetary commitments in the system.

When importing customer master data addresses using Data Management Framework (DMF) via Data management > Import, the system currently links the zip code on the customer address to the first found zip code when the same zip code ID exists multiple times with different street number ranges.

Issue:

1. This behavior can lead to incorrect zip code associations, especially in regions where multiple zip codes cover overlapping areas but differ by street number ranges.
2. Instead of intelligently matching the zip code based on the street number of the customer address, the system requires the user to manually select the correct zip code ID based on the street number of the customer address which is impractical and inefficient when dealing with large volumes of customer data.
3. Although the out-of-the-box solution allows zip codes to be categorized as odd/even/all street numbers with a defined range, it does not support correct associations automatically resulting in compromised data accuracy.

Proposed Enhancement:

DMF import logic should be updated. Additional criteria of street number matching should be included.

Benefits:

This would ensure a better alignment with regional postal code standards, data accuracy, accurate geo coordinate validations and improve downstream processes like tax calculation, delivery routing, and compliance.

The customer is using item substitutions (plan groups) on formulas that consist of two lines, each with its own priority. The primary and secondary formula item have corresponding item coverage setup that replenish demand with planned purchase orders at warehouse 12 and transfer this demand to warehouse 13. However, when planning is run with demand at warehouse 13 the system completely ignores plan group setup. It covers the demand with on-hand inventory and replenishes the remaining quantity only for the item with priority 1, without considering the on-hand inventory for the item with priority 2. However, if the demand is for warehouse 12 (where no transfer is required), the item substitutions work as expected, and the on-hand inventory for the item with priority 2 is considered.

In an intercompany scenario, if we have negative or positive charges added as percent on Intercompany sales

order level, the system will cause the charges to double in the Intercompany purchase order, after invoicing the Intercompany

sales order.

The current behavior introduces challenges for our business users and creates inconsistencies in scenarios.

Please consider to fix this in future release. Thank you!

We've received feedback from several users who prefer using 'dark mode' in other Microsoft applications, as they find it easier on the eyes—especially during extended periods of use. Given this preference, we wanted to suggest considering the addition of a 'dark mode' option in Microsoft Dynamics.

We believe this feature could enhance user comfort and accessibility, aligning Dynamics with the broader Microsoft ecosystem and user expectations

Go to Accounts payable > Purchse Orders > All Purchase orders

System is showing all the PO's (open and invoiced PO).

Expectation -

System should show only 'active purchase orders’ by default while opening the form, this will open the form much quicker then currently taking time.

Note: This is inline with standard behavior in All Project form (from Project management) or All free text invoice form ( From Account receivable), they shows only open/active records by default.

Currently DRA will only print PDF files when it is running as an application, this is due to it using Adobe to convert the file.

However when running DRA as an application, there is a known issue with stability and crashes, causing outages.

My idea is to have DRA be able to print PDF files while running as a Windows Service which is much more stable.

The legacy MRP was able to firm batch orders created out as a result of "plan planning formula" process, which can be found from the planned orders page. With Planning optimization this is not supported. This idea is for bringing this process back into planning optimization, since the product team has said the following on the LCS issue 1034725: "Upon further investigation, we have determined that while this is a bug, it doesn’t meet the level required for us to fix at this time."

Full text on: https://fix.lcs.dynamics.com/Issue/Details?bugId=1034725&dbType=3&qc=d2e4a8d6385349223618c136a8fc1724e2709a374db90ced558608bee9bcf5c8