Segmented product data entry
With the number of fields available on a product (or item), it would be ideal if we could create data entry segments governing, which fields a user role should fill in and give the user a guided data entry experience. This should be combined with a workflow where the product enrichment process...
Enable product configuration also for formula items (BOM txpe formula)
In some industries and scenarios it is necessary to advise the customer to work with formula. It is then a clear competitive disadvantage not to be able to use the variant configurator with all its functions.
Fix unit conversion bug not allowing standard conversions to be used with base units
We're unable to convert from OZ to LB when converting through two base units when the standard conversion is set up as LB to OZ.
The converter should be able to use the LB to OZ setup to infer the OZ to LB conversion.
This is due to a bug @ UnitOfMeasureConverter_Product...
Separate default order setting for different order type and enable setup down to warehouse level
Currently default order settings will combine the request from production and transfer order. For example the minimum order quantity setup. If user setup a specific value, then it will affect on both production and transfer order. This is not convenient for the real business requirement. Usual...
Mandatory labels for price fields
On Released products, when adding Purchase price, Sell Price and Cost Price to the overview grid view, all have the same label Price.
This is a bit confusing for users.
The label should be mandatory, e.g. Purchase price, S...
Shelf Life Period in Days must be in New Released Product dialog
Shelf Life Period in Days must be in New Released Product dialog for the Batch-enabled Items with FEFO-controlled Model group.
That's Mandatory field, which remains empty otherwise.
Shelf Life is critical in LifeSciences.
Provide Option to Set Unit of Measure during Engineering Product Creation
There is no option to specify the Unit of Measure when creating an 'Engineering Product'.
This causes a problem when using dual-write to integrate Products to CRM. This is because CRM requires a Unit Class/Group to be specified at the point of creation, with no option to work...
Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap.
As a workaround, you can create a released template product, assign it to the release policy that is assigned to the engineering category, and thus, when the item is created (released) in the engineering category it will get by default the unit of measure assigned to the released template item.
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft
Add the ability to filter Released items by item dimensions (tracking, storage)
Often, especially when testing or checking for issues, you need to find items that match a particular storage or tracking dimension - for example, when you want to check items that are batch or serial controlled, or you realise in testing that some items have been setup incorrectly.
...
Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft
Approved vendors by product variant
Allow the approved vendor list from Released products to include product dimensions. It is entirely possible to have approved vendors that are different according to some combination of product dimensions.
Thanks for your input! If it gets votes, we will consider adding it to our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft
Block purchase order creation but not open purchase order lines.
Hi Team,
In release products , Engineer - > default order settings we have an option under Purchase "Stopped" checkbox.
If we are enabling it, it blocks creation of purchase orders manually or from Master Planning and also open purchase order lines.
Thanks for your input! This is already posssible to be done by using the detailed business processes of the product lifecycle state.
You will need to enable the Engineering Change Management configuration key. When you do, in the form "Product lifecycle state" you will see a more controlled business processes. You can create your own lifecycle states and create one that does not allow purchase. When you assign this lirfecycle state to a proudct, it will prevent the product to be added to new purchase orders, but it will still allow the existing lines to be continued. You do not need to use any of the existing Engineering Change Management functionality.
There is an idea that is to make the product lifecycle state indpendent of the Engineering Change Management configuration key, and you can vote it if desired on: Microsoft Idea (dynamics.com)
Sincerely,
Beatriz Nebot Gracia
Administrator
Thank you for your feedback. We are not considering the suggestion at this time due to the following reason:
For unique referencing of a SKU in the User interaction, we suggest to use the unique product ID instead of using a segmented entry of Item + Dimensions.
In other context, for example Apparel, a table based selection would be needed, but this would require a complete redesign of the user interaction, and a generic segmented control might not be the solution.
Sincerely,
Conrad Volkmann
PM, Microsoft