Unit Sequence group id needs to be on the Create Released product screen
We really need the unit sequence group id to be on the Item creation screen! When I choose an advanced warehousing storage dim group, the "reservation hierarchy" appears on that create screen but no unit seq group! The unit seq group id should also appear. This should have been done years ago. ...
Navigate to product configuration model from Item list (detail) page
It currently requires a custom report to identify what product configuration model is attached to a particular item making maintenance difficult. There is no navigation path from item to PCM or vice-versa This enhancement would treat the PCM similar to a BOM for an item/product in the manufact...
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Beatriz Nebot Gracia,
Microsoft.
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...
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
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.
Modify Default Version in Engineering Change Order Module
In the engineering change order module, include a flag/toggle to update the Default Product Variant in released product details to the new version upon completion of the ECO. It is typically the case that the newest version is desired for future manufacturing or procurement. Updating the defau...
Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap.
Sincerely,
Beatriz Nebot Gracia
Senior Product Manager, Microsoft
Automatic bar code creation for a released product
When you create a new released product, or release a product to legal entity, the user must set up the bar code manually.
It would be helpful for the user if the bar code being created automatically when the released product being created.
Once created, the parameter ‘...
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
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
Administrator
Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Beatriz Nebot Gracia
Program Manager, Microsoft