Dynamics 365 Supply Chain Management

The Vendors V3 entity has two main issues affecting performance:

1 - It is very slow, likely due to the number of data sources.

2 - It does not allow parallel processing due to the need to support a self-relation.

These issues together conspire to make data migration and integrations with vendors challenging. For data migration, the only option is to manually split the import file to achieve some level of manual parallel processing.

The Customers V3 (CustCustomerV3Entity) entity suffers from all the above issues and it has been addressed by creating two separate entities with the following design.

Customer definitions (CustCustomerBaseEntity) entity - Contains only the most common fields and significantly less data sources and performs an order of magnitude better than Customers V3. It also removes support for the self-relation so it allows parallel processing which is another option to increase performance.

Customer details V2 (CustCustomerDetailV2Entity) entity - Contains the self-relation and other less common or low performing fields, such as the default dimension, and also supports parallel processing.

Thanks in advance for the assistance. We have customer using IV, integrated with Fno. Also, using IOM. There is a need to begin to allow non-admin users to submit inventory queries in IV (Operational Visibility) as well as Reservation Postings. Right now, the only non-admin role in Power Platform is Dynamics Inventory Service Role. This seems to give a user access to all functionality in IV. It would be nice for another role to exist, than limits the functionality in IV. Such that a user can run Operational Visibility functions..like queries and posting to soft reserve measure in Reserve Posting. A way to give a user access to IV, without giving them everything. Thanks.

After registration in Purchase order, stock is getting increased in the system. This stock can be issued in production also for consumption which is causing negative inventory. A feature needs to be developed to restrict this stock increase without posting GRN.

We should be able to create manual routes with multiple route segments or add/update route segments for an existing route after it has been assigned to a load. Currently, the manual routes cannot have multiple segments and always need route plan and guide setup which we cannot do for adhoc routes.

During the inventory closing and adjustment process the business has a requirement as below-

1. If the Closing is performed on August 31^st (Month-1) - the closing must happen on 31^st August 23- Which is working as expected
2. If the Closing is performed on August 31^st (Month-1) the recalculation must also happen on 31^st August 23 – Which is not happening in the current process

When a user changes the transfer order header ship and receipt date, the transfer order lines ship and receipt dates are not updated when Transfer order status is "Shipped" and the user is not prompted to update the lines.

This means that if a transfer order ship or receipt date needs to be changed, the user must update the dates on each individual transfer order line.

It would be nice to have the ability to update transfer order lines ship dates and receipt dates after modifying transfer order header ship date and receipt date when Transfer order status is "shipped", similar to how Transfer Order in Created status is updated after updating the date in header.

The issue is related to display issue and seems it happening only if the multiple warehouses having a same location ID, it is giving incorrect information to user.

Path: Released Product/ Warehouse item

In the Location tab, the warehouse is not displayed correctly.

For example, in the case where a single row is selected on the "Voucher transactions" list screen, if you select it using the following procedure, the last focused row will be processed, not the row with the checkbox ON.

I want to process the rows where the checkbox is ON.

---------------------------------------------

1) Turn-on the check box in the second row.

2) Turn-on the checkbox on the 4th row.

3) Turn-off the checkbox on the second row.

4) Press the "Transaction" button from the menu at the top of the screen.

5) The transaction information on the second row is displayed.

---------------------------------------------

Given there are two companies where one is a sales only company and the other one holds all the items in stock. This implies that all sales orders will result in the creation of the intercompany chain and intercompany sales orders. If the reservation is manual for the sales company and automatic in the stock company and the sales quantity that is synced to the intercompany sales order exceeds the quantity that can be reserved in the stock company, there is no warning shown or "Autoreservation" form triggered in the sales order within the sales company.

For regular sales orders inside the stock company there is such a function available to tells the user to either change the product/quantity or acknowledge the lack of items in stock. This should be available within the sales company as well, since the order management and completion is always done within the original sales order.

Autoreservation form: https://imgur.com/a/QEAQsH3

The system has inconsistent validation between the mode of delivery form and the shipping carriers form. This can lead to major data integrity issues. The screenshot below shows that the validation already exists on the mode of delivery form so it cannot be a performance issue. Even if it is a performance issue that should be fine since it is very rare that services would be deleted. That also is a significantly better outcome then having to manually update thousands of customer records, SOs, Pos, transfer orders etc which now have invalid MOD on them. 

I would argue in most cases it is not best practice to delete master data records that have transactions logged against them. However, this issue is not just impacting invoiced sales orders it also impacts open transactions. If a mode of delivery is deleted it now also prevents the posting of any sales orders using that mode of delivery. It also requires customers that have that set as a default to be updated to prevent the issue from happening on new transactions that default from the customer. So the impact is very significant.