Kevin Beskalis

Current design:

After initial release to warehouse after performing batch balancing process, there is no way to add additional formula lines/components to the batch order as the work for it will not be created and will result in the below error:

"Batch order %1 was not released to warehouse because the batch order is part of the batch balancing process."

Suggested design:

It should be allowed to release additional lines especially of the type "none" as they do not affect the batch balancing process calculation and it is a common scenario in many industries where replacement for fragile components could be needed to proceed with the production process.

Batch balancing - Supply Chain Management | Dynamics 365 | Microsoft Learn

Current behavior:

Purchase agreements V2 (PurchPurchaseAgreementHeaderV2Entity) does not allow to use filtering in document templates "Apply current record"

If we choose to export data through this entity, all data must be exported since it doesn't allow to filter for a certain record.

Details for issue 281875 (dynamics.com)

Suggested behavior:

Since it is a growing need for many organizations to export specific headers and lines to be used elsewhere, this entity should allow for filtering like it works for purchase orders for example.

Pricing management (when enabled) should replace price models when calculating price of items configured using a product configuration model.

Currently, the sales order line will calculate the price of the product based on its default attributes and not the ones selected while configuring it using the model.

The current behavior is that when "Count non-discountable items towards threshold" is enabled, it will include those items towards threshold qualification which are added to the discount line section as "Include", but have been either marked as "Prevent all discounts" (Under Commerce tab of Released products) or have another Exclusive or Best price discount applied.

The above behavior is according to Issue 449997 that can be found in LCS.

Proposed behavior: this parameter should allow for items that aren't included to count towards the threshold as well. (or a separate parameter) To allow for more scenarios to be applied in the system.

Currently the only way to decide the number of custom labels to be printed is to set it on the label layout when creating it. (Whether by setting a static number or adding a variable field that would reflect a different number per record)

Suggestion:

Copies to be printed field to be added to the menu item for printing custom labels to allow the user to select the number of copies they need manually per each printing session.