Dynamics 365 Supply Chain Management

The back button is a systematic feature and cannot be manipulated in terms of placement—whether at the top or bottom of the mobile menu items. While the system allows customization for the order of custom made mobile device menu items, it does not include the ability to reorder the back button.

This can be challenging for businesses with extensive lists of mobile device menu items, as workers may need to scroll down on their PDAs to access the back button and navigate to the previous screen.

This would be a great feature to let the business decide where they want to place the default back button.

We have a specific requirement regarding the inventory aging report functionality in Dynamics 365.

Currently, the system displays the age of inventory items per warehouse. However, when an item is transferred to a different warehouse, the aging of the item gets reset.

Our requirement is that the aging of the item should not reset upon warehouse transfer. The aging should continue to be based on the original receipt date — that is, the date when the item first arrived or was purchased by the company.

We are considering using the Product Receipt Date or the Physical Receipt Date from the original purchase order as the reference for inventory aging.

ISSUE:

When using the mobile device menu items mode indirect and activity code: data inquiry, you can make list pages (CARDS) on nearly every table ind D365F&O with filters. Enabling warehouse workers to have very intuitive approach to warehouse operations and start up of different work processes based on the lists. The list has a force since they do not give any limitations as to what fields can be displayed on the CARD - just they are on the table or method() . Adding mobile device steps and detours to the data inquiry can kick of the process of different work and later returning to the list / Cards and kick of yet other work. Unfortunately when returning to the list this is not refresh with the query that is actually saved on the mobile device menu items on entry. Meaning you need to leave the list and go back to the menu and back again to have the list refresh and see what is yet left to do.

IMPACT:

The refreshing the data inquiry list after processing work gives the user two extra keystrokes / mouse click that they need to do to manually refresh the list of Cards, sometimes even reentering parts of the filter. Thereby having an impact of workers daily productivity. There is a great deal of gain on time and cost savings of having this done automatically.

IDEA:

Making a parameter on the mobile device step on the BRING BACK step where the query can be set to be refreshed or not. Of course it should be possible even if there is no setup done on the return BRING BACK to the start menu.

Hope this will idea will be considered.

Thank you for your time.

Best regards

Tom Schrader Poulsen

Extend the Price tree, Price attributes, Discounts, Charges, Trade agreements, Base price determination etc. to the Procurement and sourcing Module for Vendors and Purchase prices.

Current setup:

Using Advanced Warehouse Management with Mobile Device

Using Quality Management

Issue: When we create a Sales Order for a part that we purchase to resell, a planned purchase order is generated. The planned purchase order is firmed to a Purchase Order. When the item is received, a quality order is generated. The user completes the quality check but cannot "Validate" the quality order because the system throws the error of unavailable inventory. This issue is due to the original sales order having the same inventory reserved ("Ordered reserved").

Microsoft said their engineering team triaged the bug and determined it was an issue but could not fix it via hotfix. It is a design limitation and will require a change in the underlying design which they cannot take on at this time.

The only way around this is to manually unreserve the inventory on the Sales Order (which quality doesn't have access to do), Validate the Quality Order and then re-reserve the inventory on the Sales Order. This is very time consuming and has to involve multiple users.

It's a common practice for the maintenance engineer to capture and attach images of the asset to the work orders as evidence of certain actions.

Right now, it's only possible to view attached images on the app with no option to create a new attachment, it would be great to add such an option like what we currently have in the maintenance request.

Currently, warehouse workers can initiate the putaway process on clusters that are still in an 'Open' status without closing them first. This leads to a recurring issue where clusters remain locked to a user even after all associated work is completed, preventing their reuse for future receipts.

This behavior stems from the system allowing putaway to begin without enforcing cluster closure. To improve operational efficiency and prevent unnecessary locking, we propose a validation check that restricts the putaway process unless the cluster is explicitly closed.

Using the Inventory Visibility Service (IVS) API's, we would like to be able to request a view of the stock quantities in a different unit than the default 'Inventory unit'.

In Dynamics, you're able to view stock information in any desired unit (through i.e.: mi=InventOnHandItem), but this functionality is missing in the IVS.

Further context:

We sell items as separate pieces as well as by the box and each item has an item specific conversion 'Pcs' <-> 'Box'.

For our web shop we want to be able to give an indication of the stock ("Plenty of stock", "Limited availability", "Out of Stock", ...) depending on the chosen sales unit. As such, we would like to be able to retrieve the stock through IVS in the "Box" unit when the customers selects x boxes:

• ... > 100 boxes : Plenty of Stock
• 100 >= ... >= 1 boxes : Limited availability
• 0 boxes : Out of stock

At the moment we need to do 2 API calls to get the stock information and then another to get the unit conversions and finally do the calculation ourselves. So having this functionality would eliminate the need of the second API call and the calculations.

Enabling the "Select voyage cost" functionality from Pending vendor invoices in D365 F&O would streamline workflows by allowing users to allocate voyage costs earlier in the process, reducing manual steps and rework. It would enhance cost allocation accuracy, improve invoice matching and validation, and provide more timely financial visibility. This early integration supports better inventory valuation, budgeting, and decision-making, while also aligning more effectively with the Landed Cost module for comprehensive cost tracking.

Microsoft decided to cancel the preview feature Rename item number.

https://learn.microsoft.com/en-us/dynamics365/supply-chain/get-started/removed-deprecated-features-scm-updates#rename-item-number-preview

Reason:

"The item number field is a primary key that is used across multiple systems. The (Preview) Rename item number feature allowed users to edit the item number field, but we found that the feature could cause data inconsistencies in multi-system and apps-integration scenarios, leading to data integrity and data corruption issues. The feature was previously in preview and was never made generally available for use in production environments."

Proposed idea:

Do not cancel this feature, because the reason above certainly does not apply to all customers. The existing preview was fine for many customers.

Instead of cancelling the feature, 1) add a clear warning message with the reason above, and 2) add a clear authorization or parameter on the user that grants the rename function only to users that know what they are doing.