Brandon Best

10.0.25 went backward on data management workspace. An import job was able to read a file and determine the type by extension and then determine the entity by name. Manually entering both of these to load a file a literally two steps backward for no discernable reason. Please revert this.

The feature: "Sales order details performance enhancement" causes bugs and issues with call center orders. This would be for a new feature that does the same thing (improve sales form performance by bypassing the sales table list page for the sales details form) for sales orders created with call center/retail channel.

When Site/Warehouse is given on a Sales order header and we use the SALES ORDER>NEW>Purchase order or Direct delivery, it should copy this information to the created purchase order header to match the pass-thru or destination warehouse on the Purchase confirmation.

Currently, the purchase order header fields, including site/warehouse are copied from vendor defaults. A vendor that delivers to multiple warehouses will then have purchase confirmations with INCORRECT delivery addresses or otherwise have BLANK delivery address in standard D365 using the default values on vendor master. This is a big oversight in design of purchase order creation from sales order.

We should at least have the option to select on purchase order creation "use defaults from vendor master". But this would need to be configured in parameters for automatic PO creation as well. Best solution is to copy PO header inventory dimensions from the sales order header.

Saved views for sales orders do not support call center functionality. Using call center and saved views for sales orders (soon to be mandatory feature) causes unintended warning and info messages throughout sales order entry. This should be updated to make saved views for sales orders include call center sales orders without undue interruptions.

System asks for Account type (Prospect or Customer) when creating a new sales quotation. We want to change the default value of the dropdown for companies that use sales quotations but not prospects. We could have a parameter in A/R to choose the default value of the dropdown in the event that Customer quotations are vastly more common than for Prospects.

The bulk update function on demand forecast lines should allow query on vendor and item category for instances where demand needs to be adjusted for changes in the ecosystem (e.g. COVID).

D365 often returns a 400 error on recommended browsers when logging in after a period of time: Bad Request - Request Too Long. Http Error 400

Dynamics should be compatible with the Microsoft recommended browsers (Edge, Chrome) and not require users to clear their cookies on a daily basis to login.

Suggestion: Optimize the cookies/cache to accommodate regular use of the product.

See related links for additional information and implied votes:

Everytime I start my browser, the Dynamics 365 FO tab that opened from last session always gives error: Bad Request - Request Too Long. Http Error 400. The size of the request headers is too long - Dynamics 365 Finance Forum Community Forum

Details for issue 624489 (dynamics.com)

Official microsoft documentation for hazardous material management explicitly states how to handle the 4 hazmat classes that don't have divisions. Haz classes 3, 7, 8 and 9 have no further division / subclass to them. Documentation says:

For classes that don't have any divisions, create a division where the code is 0. For example, in the IATA regulation, class-7 radioactive materials have no subdivisions. In this case, you will create a 0 division that you can associate with a released product when you assign the class."

If you do this, and create a HazMat division of "0" for class 3 and then again for class 7, you will get an error about uniqueness on the table. Alternatively, creating a single hazmat division record of "0" and hoping it can be used across multiple hazmat classes is also a bust. The class field dictates the automatic filtering of the field.

The easy solution of course is to change the system to match the released documentation so we can use multiple divisions of "0".

The BETTER solution would be to make HAZMAT division not mandatory because tons of regulated products do not have a division within their class and it was a foolish assumption to make in the system.

Saved views for sales orders do not support call center functionality. Using call center and saved views for sales orders (a mandatory feature) causes unintended warning and info messages throughout sales order entry. This should be updated to make saved views for sales orders include call center sales orders without undue interruptions.

This would make it possible to use call center channel orders in D365 SCM with saved views. The feature is available and forcibly enabled for companies using commerce functionality, but there are several known issues that would be resolved by intentionally developing and testing the saved view functionality with commerce/call center order management.

Order fulfillment policies should respect and ignore direct delivery lines when calculating fulfillment percentages for release to warehouse. A direct delivery line will never be reserved and released as part of the standard process and should not count against the order's fulfillment rate, much like a service item shouldn't.