Elise Nguyen

Customers reported an issue where inventory marking is automatically applied to a virtual inventory transaction when creating a PO from Purchase Requisition or manually from the All Purchase Orders page. Unlike the first scenario (creating a PO from an SO), where the marking can be manually unmarked and reassigned to another PO, this second scenario does not allow manual unmarking. Attempting to unmark results in the following error:

"Manual marking is not allowed because the inventory transaction is linked to a virtual inventory transaction."

Customer Configuration & Context:

• Project module: Not used
• Item requirement: Not used
• Setup: Customer only creates a Project ID and Contract ID
• Business Impact: Prevents users from manually managing inventory marking as needed, leading to operational inefficiencies.

Investigation Findings:

• The issue is reproducible in standard D365 FnO.
• The FIN team confirmed that this behavior is by design, but they could not provide further details on the logic behind it.
• There is limited documentation on this specific scenario, making it difficult to confirm whether this is the expected system behavior or a potential enhancement area.

Request for Clarification:

1. Can you confirm why marking is enforced automatically in this scenario and cannot be unmarked?
2. What system logic drives this behavior when no Item requirement or Project module is used?
3. Is this behavior expected, or should it be considered for improvement in a future release?

We would appreciate any insights or guidance you can provide

Currently, the “Group by planning priority” option in the manual firming dialog (Planned Orders > Firm) always defaults to “No”, regardless of the global setup in Master Planning Parameters > Firm – Transfer.

This causes significant user friction in environments where the standard business process is to always firm with grouping enabled (i.e., “Yes”). Users must manually tick this checkbox every time they firm orders, which adds risk and inconsistency in high-volume operations.

We would like to request a feature enhancement that allows this checkbox to:

• Inherit the value from the master planning parameters, or
• Be controlled by a user or company-level default setting

This improvement would:

• Reduce manual errors
• Align manual firming behavior with global planning intent
• Improve usability and consistency across the system

This parameter is already respected in batch firming, so having parity in manual firming would be highly beneficial.

Thank you for considering this enhancement.

Business Need:

Currently, users can only update the "Delivery remainder" field on purchase order lines manually, one line at a time, using the "Update remaining quantity" option. There is no way to mass update this field across multiple POs using Data Management Framework (DMF) or any standard bulk process.

Impact:

For organizations that manage a large number of purchase orders, the inability to update “Delivery remainder” in bulk results in significant manual effort, increased risk of errors, and inefficiency. A standard mass update capability would streamline business processes and improve user productivity.

Request:

Please consider enabling the ability to mass update the “Delivery remainder” field on purchase order lines, either by:

• Allowing direct update of this field through the DMF “Purchase order lines” entity
• or
• Providing a standard bulk update feature (e.g., via periodic task, batch job, or additional workspace option)

Comments:

This feature would be especially valuable for large organizations or those with complex purchasing workflows. Community voting and additional use cases can be added to this idea.

We would like to suggest an enhancement to improve monitoring and diagnostic capabilities for auto label printing issues in D365 Finance and Operations, particularly in the Warehouse Management System (WMS) area.

Scenario:

Currently, label printing jobs triggered via WMS Mobile App (e.g. Purchase Receive) are handled via document routing and printer mapping. However, when a print job is delayed or stuck (e.g., print job created but not executed for 30–40 minutes), there is no visibility across the system to understand where the issue lies — whether it’s within D365 processing, the printer server, or the mobile device workflow.

Customer Request:

Add a centralized monitoring mechanism or diagnostic log/tracker that can:

• Trace the lifecycle of a print job (Created > Queued > Sent > Executed > Failed/Success)
• Identify delays between WMS App action and actual printer execution
• Correlate D365 print job with Work ID / LP / User
• Raise warnings or flags if print jobs are stuck in queue over X minutes
• Expose this monitoring view to admin or IT users for faster issue triage

Business Justification:

This will significantly reduce investigation time when label printing fails or delays, especially in high-volume warehouses. Customers expect traceability and diagnostic transparency when using auto label printing features integrated between D365 and external print systems.

In Dynamics 3D365, we noticed that when converting a Purchase Requisition (PR) to a Purchase Order (PO), the system automatically overrides the PR line’s Item Description with the description from the Released Product — if the PR line has an Item Number (catalog item).

This behavior is expected and ensures consistency across product-based transactions. However, it limits flexibility in business scenarios where procurement teams need to:

• Provide customized descriptions for specific orders (e.g., product variations, vendor-specific packaging, labeling, etc.).
• Capture unique notes or requirements per line that are intended to be passed on to the supplier via the PO.

At present, the only supported workaround is to use non-catalog items, which is not feasible for organizations that require item tracking, inventory integration, or vendor item references.

Proposed Enhancement:

Introduce a parameter or policy setting that allows organizations to choose whether to:

1. Retain the PR line description when creating the PO, or
2. Use the Released Product description (current behavior).

This could be:

• A toggle in Procurement and sourcing parameters, or
• An option in Purchase Order creation policies.

Business Impact:

• Provides flexibility for real-world procurement scenarios.
• Reduces need for customization just to control description flow.
• Helps users manage exceptions while still leveraging item-based requisitions.