Dynamics 365 Supply Chain Management

Can you add a Column and Link in Purchase Requistions VIEW for Purchase Order #. I always have to click into the Purchase Req. to get to the PO. It would be real nice to have a link right on my VIEW.

Thank you

Cindy

Issue Description

In the current setup of the “Automatic release of sales orders” functionality, when the release fails, the inventory reservation is not rolled back—even when the parameter “Keep reservation on release failure” is set to No. This behaviour is unexpected from a business perspective and causes operational challenges.

The issue was raised under 1064971 and 227564. The Product Group feedback that the system is working as intended,

It appears that the reason behind the feature limitation here is because In the current setup, users can configure the “Release rule failure option for auto release” to behave in two ways:

• Warn and skip line: The system retains the reservation and skips the affected line.
• Error and skip order: The system removes the reservation and skips all lines in the order.

Proposed Idea

Enhance the “Automatic release of sales orders” functionality to ensure that inventory reservations are always rolled back when release fails—if the “Keep reservation on release failure” parameter is set to No, regardless of fulfilment policy usage.

This change would:

• Align system behaviour with user expectations.
• Prevent inventory from being locked unnecessarily.
• Reduce manual intervention and improve operational efficiency.
• Increase trust in system configuration and documentation.

Issue Description

Currently, when configuring Quality Associations using the “Goods in Transit” reference type, the system does not allow selecting the “Create work only” option. This limitation prevents users from generating work directly from the quality association, which is a key requirement for certain warehouse processes.

this configuration is officially supported only for the Purchase and Production reference types, as per current documentation.

Suggested Idea

Extend support for the “Create work only” option in Quality Associations to include the “Goods in Transit” reference type. This would align its behaviour with other supported types like Purchase and Production, and allow users to initiate work directly from quality associations for in-transit goods.

This enhancement would improve process consistency, reduce manual workarounds, and support more advanced warehouse quality management scenarios.

If the product uses the Product variant name nomenclature setup (the checkbox is enabled for the product and an appropriate value is selected), and in this setup the product variant version is included as part of the variant name, then during the creation of a new variant version in the Engineering Change Order (Impact = New version), the new version value should be updated in the new product name.

Current behavior:

Current: Product name – XL V01 (variant version value: V01)

→ New ECO with new version creation (V02)

→ Product name remains XL V01 (variant version value: V02)

Expected behavior:

Current: Product name – XL V01 (variant version value: V01)

→ New ECO with new version creation (V02)

→ Product name becomes XL V02 (variant version value: V02)

In DMF parameter there is a control for how data is inserted to staging table from uploaded file (or from integration queue). The control "Data Access Mode" has these two possible settings:

Table or view (Fast load)

Table of View

Fast load is the default setting and what it does is add two things to the insert statement via DIXF/SSIS logic: (check constraints, with tablock). This is prudent and efficient since best practice dictates that bulk insert operations are faster when doing a full table lock.

However it is not recommended in parallel processing with smaller payloads where full table locks might slow down performance due to the processing of data starting at the same time as inserts (causing wait times of LCK_MX and delays for inserting into staging table).

When using recurring integration there are many scenarios where parallel processing is of the essence, but since this parameter is global there is no way to currently adhere to best practices for all integration scenarios, either we use bulk insert with table lock globally or we don't.

My suggestion is to either provide this parameter per DMF project, or have it as part of the "Run messages in order" control on DMF recurring integration batch jobs. This will allow for better parallel processing where needed and still allow for bulk inserts of larger payloads to use the table lock for improved performance.

The change will have to be made in DMF components on SSIS as well as having this parameter per DMF project.

When a product is substituted, it must be possible to mark the substituted material as Use-Up, meaning that the old material inventory is consumed FIRST from inventory before the new material or material variant is consumed.

When using plan groups in formulas, it is possible to define the sequence of consumption, however in this case, the old material that is no longer supposed to be purchased or produced must be on priority 1 to be consumed first from inventory - but it is not supposed to be purchased.

One way to solve this would be to consider the lifecycle state for procurement or production. Another way would be to introduce more sophisticated replacement rules.

If the solution is based on planning groups, it would be great to see that concept also enabled in Discrete BOM's.

When filling in the job type field on the 'create maintenance request' form, the job type & job type variant can be selected, but the field will stay empty.

When creating the maintenance request, the fields are added to the maintenance request, so the system saved them, but did not display them in the form.

This should be resolved as u bug.

#bug 1008906

I´m writing this "Idea" after communication with MS support:

For email notifications which are sent out triggered by custom alert for vendor certificates Link in email doesn´t include legal entity which leads to error message and a lack of functionality.

In my opinion this is a technical bug which needs to be fixed anyway.

In the new Warehouse app v4.x, the ability to search for a warehouse when selecting "Change warehouse" has been removed. Can this be added back?

The idea is to allow you to modify the calculation management by first determining the net unit price and only then multiplying by the quantity. In this way, 16 rows of 1 piece would have the same value (added) as a row of 16 pieces (due to rounding).

NOW

price 221.85 , discount 49% , qty 16 the system calculate

221,85*49/100 = 108.7065

(221,85-108.7065) * 16 = 1810.2960 rounded 1810.30

DESIRED

221,85*49/100 = 108.7065 rounded 108.71

(221,85-108.71) * 16 = 1,810.24