Kareem Essam

In Dynamics 365 Supply Chain Management, batch jobs related to sales order processing (e.g., SalesOrderConsumptionAndConfirmation) can dynamically create new tasks during runtime using FormLetterServiceController and related classes. However, these dynamically created tasks do not inherit the parent job's task dependencies, causing tasks to trigger out of sequence.

This behavior leads to race conditions where tasks execute simultaneously instead of sequentially, resulting in:

• Incorrect order processing
• Task cancellations
• Significant business impact, including lost sales

We propose a product enhancement to ensure:

• All dynamically created batch tasks automatically inherit appropriate dependencies, especially when part of a chain (e.g., Job1 → Job2 → Job3).
• This would preserve execution order and maintain task integrity even when additional tasks are generated on the fly.

This change would improve the reliability of complex posting jobs and reduce the need for custom solutions or manual workarounds.

In intercompany scenarios, when a Purchase Order is created in one legal entity and automatically generates an intercompany Sales Order in another, the value entered in the line-level "Text" field does not sync across. This causes the text to be missing on the intercompany Sales Order, which impacts downstream documents such as order confirmations and invoices where this information is expected by end customers or for compliance reasons.

This idea proposes enhancing the intercompany synchronization logic to include the "Text" field (PurchLine.Name → SalesLine.Name) so that relevant business details are preserved across legal entities in intercompany transactions especially in cases involving direct delivery or automatic intercompany flows.

Currently, Dynamics 365 SCM allows deletion of tracking number groups even when they are assigned to released products. This can lead to system errors like “Number group does not exist” when users process purchase orders or other transactions involving these products.

I propose adding a validation that prevents deletion of any tracking number group that is actively assigned to a product with existing transactions. This safeguard would help maintain data integrity and avoid operational disruptions caused by accidental deletions.

Additionally, if deletion is necessary, the system should prompt users with a clear warning and provide guidance on how to safely reassign or update products before removing the tracking number group.

Implementing this validation would improve user experience and reduce support cases caused by this issue.

Issue:

When a purchase order contains a bundle item with a charge amount, after the bundle explodes in Dynamics 365, the bundle item line is set to Canceled status as expected. The charge amount on the canceled bundle line is correctly removed from the totals and other related financial documents. However, the VAT (tax) associated with that charge remains calculated and included in the sales order totals screen, causing a discrepancy between the displayed totals and the actual financial values.

Impact:

This results in the totals screen showing incorrect amounts, which can confuse users and cause discrepancies when comparing POS transactions to Dynamics 365 sales orders. Although this issue does not affect invoicing or confirmation documents, it creates operational challenges and reduces trust in the accuracy of on-screen totals.

Business Need:

The VAT amount related to canceled bundle item lines with charges should be fully excluded from all totals and calculations in Dynamics 365 to ensure consistency and accuracy of displayed financial data.

Currently, in Dynamics 365 Finance and Supply Chain Management, when using a saved view with filters in the All-Sales Orders form, clicking New to create a sales order clears the saved view filters and marks the view as modified. Even if the new order creation is canceled, the filters remain removed until the form is closed and reopened.

This behavior is confirmed as by design, but it can be counterintuitive for users who rely on saved views to quickly filter and access customer-specific orders. Preserving saved view filters when creating a new sales order would improve usability and reduce additional steps for end users.

Proposed Improvement:

Provide an option or enhancement to retain saved view filters when clicking “New” in the All Sales Orders form, allowing users to maintain their context without reopening the form.

Benefits:

• Streamlines workflow for users managing frequent or filtered sales orders.
• Reduces confusion and perceived loss of saved views.
• Improves user experience and efficiency in Accounts Receivable / Sales Order Management.

Currently, the “Archive with Dataverse long-term retention” feature in Dynamics 365 Supply Chain Management archives all sales orders that match the filter criteria provided by the user (e.g., date range, legal entity). There is no built-in way to automatically exclude intercompany sales orders.

In some environments, like the customer’s, nearly all sales orders are intercompany orders. As a result, running an archive job could inadvertently archive records that are part of intercompany chains, which can break transactional relationships across legal entities.

Proposed Idea:

Introduce an option in the archive job to exclude intercompany sales orders automatically or provide a dedicated filter/flag that identifies intercompany orders, so admins can safely archive non-intercompany sales orders without risking data integrity.

This enhancement would align the system behavior with the documented guidance that intercompany orders should not be archived, making the feature safer and more flexible for customers with a high volume of intercompany transactions.

Currently, when a Product Group acknowledges a bug and confirms that no ETA is available, the LCS issue is marked as "Resolved" even though the underlying issue is not actually fixed. This causes confusion and frustration for customers, as the "Follow" option is no longer available once the status is marked as resolved.

I suggest adding a distinct status for such cases (for example, "Acknowledged – Fix Pending") and keeping the "Follow" functionality active until the issue is fully fixed and deployed. This would give customers clear visibility that Microsoft is still working on the problem and allow them to continue tracking progress automatically, avoiding the impression that the issue is closed prematurely.

Description:

Currently, the Customer/Item statistics report in Dynamics 365 Supply Chain Management retrieves data only from the InventTrans table. When inventory consolidation or archiving is performed, detailed transaction records are moved to InventTransArchive, and summarized entries are created in InventTrans.

As a result, when users run the Customer/Item statistics report for periods that have been consolidated, cost amounts appear missing or incorrect, since the report does not read from the archived or consolidated data. This leads to incomplete or misleading figures, especially for items or customers affected by consolidation.

Proposed Improvement:

Enhance the Customer/Item statistics report (or its underlying data model) to:

• Include data from InventTransArchive for relevant periods.
• Optionally, detect when the selected reporting range includes consolidation periods and alert the user.
• Ensure consistent cost figures across reports such as Inventory value report and Customer/Item statistics.

Business Impact:

This limitation causes reporting discrepancies that can confuse end users and require manual reconciliation or custom reporting solutions. Including archived data or adding a system notification would greatly improve accuracy and transparency in post-consolidation reporting, reducing support incidents and custom development needs.

Currently, when a purchase order line is cancelled, any markups or charges that were previously associated with that line remain included in the purchase order totals. This leads to an incorrect total value, as the markup from a now-irrelevant (cancelled) line still contributes to the PO total calculation.

This behavior can cause confusion and inaccurate financial reporting, especially when users rely on the purchase order totals for cost validation or approval processes.

Expected Behavior:

When a purchase order line is cancelled, any markups or charges linked to that line should be automatically excluded from the purchase order totals, ensuring that the total value accurately reflects only the active lines.

Business Impact:

Prevents incorrect financial totals on purchase orders.

Reduces manual effort needed to review or remove markups after cancellations.

Improves accuracy and transparency for users handling large or complex POs with multiple lines and charges.

In the current system, it is possible for users to create inventory transactions with excessively large quantities (e.g., 18 digits) through both the Warehouse app and On-hand quantity adjustments. While the system allows these transactions, they cause significant issues during inventory closing and reconciliation, as the system cannot process or correct these invalid values automatically.

We propose implementing stricter validation rules to prevent the creation of unrealistic quantities in inventory transactions, both in the Warehouse app and On-hand adjustments. This enhancement would:

• Prevent invalid or extreme quantity entries.
• Reduce the risk of data corruption.
• Avoid manual interventions, workarounds, or corrective scripts in both sandbox and production environments.
• Improve system reliability and user confidence during inventory closing and reconciliation.

This idea addresses a real-world scenario where currently, extreme quantity entries can disrupt business processes, and provides a proactive way to prevent similar issues in the future.