Fatih Gork Dynamics 365FO Func. Consultant

When you tick both picking requirements and registration requirements in your item model group setup, application applies these requirements to purchase orders and sales orders, all fine. However, registration is forced for transfer orders while picking is not forced. You can ship transfer orders without updating transactions as picked, however you can not receive shipped items without updating transactions as registered. If registration was not for transfer orders, we could have used this functionality in one of our projects. Separating these requirements as transfer order and non-transfer order would really help in future implementations.

Allow users to create setups for transfer orders in quality associations form to create automatic quality orders upon transfer order registration/receipt. It is possible to create automatic quality orders when items are received from purchase orders but there isn't such functionality for transfer orders. Some companies require monitoring items' temperature during transport and there is no way to block received inventory until quality department checks items and approve quality.

Currently application can create quarantine orders when items are registered through a purchase order, but there is not such a functionality for transfer orders. Separating "Quarantine requirements" in Item model groups form as "Transfer order", "Non-transfer order", letting users to manage quarantine order requirements per order type and creation of automatic quarantine orders upon transfer receipt would be helpful.

In category access policy rule, there is a check box labeled "Include subcategories". It is used to add subcategories of the selected category as well. This is quite practical. Can a similar option be added to automate including new sub nodes as well? There are many companies that design their procurement category nodes similar to their main accounts. In such scenarios there are many policies as a result of updating them every time a category is created, and hundreds of categories in each policy. This increases the record size in tables and also users have to remember to go into related policy and add the new category every time. Can an option named "automatically add subcategories" be added and can application record selected category's RecId when policy is saved? Then, while creating A PR, application can go into that table, pull the saved RecId and add its subcategories into category lookup by using NestedSetLeft and NestedSetRight properties.