Date range for configurator model version
Constraint based configurator model is linked to a product master in the version screen. This version , just like a BOM version, has a from.. to date. The defaults popping into the TO date is rather meaningless. "TODAY". So if the user does not pay attention to the dates, his configurator model w...
Add external item number associated with defult vendor on released products details
It is quick and easy way to find company item number v.s. vendor item number.
Thank you for your feedback.
We need some more details to understand your suggestion better.
Can you please help us clarify the business scenario(s), where you would need access to the vendor item number from the Released product details form?
Who is the typical user of this information, and what are they doing when they need this information?
Sincerely,
Søren Vagn Andersen, Principal Program Manager
Microsoft.
Constraint based configurator should create part numbers
The constraint based configurator can only produce config id's for a product master. Many customers want the configurator to produce new part numbers just like Product Builder could do. This is a much more user friendly way of working with configured products.
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,
Søren Vagn Andersen,
Microsoft.
Bring enhanced item search to other screens
The sales order and purchase order screens have a nice feature where you can type in any part of the item number, search name, product name, variant name directly into the item number field and it will suggest items that match any of the criteria. This is configurable on the Search criteria sc...
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,
Søren Vagn Andersen, Principal Program Manager,
Microsoft.
Retail Kit versions
Suggest to have kit version functionality, similar to BOM versions, to allow user to setup multiple versions, approve the versions, deactivate old version and activate new versions, and with date and quantity ranges.
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,
Conrad Volkmann
PM, Microsoft
Modification des tables dasn azure synpase Spark
Permettre la modification des champs de tables dans synapse & Spark pour les tables ajouter via azure Link (Gen 2) afin que les personnalisations de champs dans D365 F&O soient prises en compte
In "Multilevel Explosion" mode: inaccurate rounding of consumption per lot size quantity of an BOM level item
The consumption per lot size amount of a finished good with multilevel BOM lines isn’t correctly rounded when choosing the “multilevel” explosion mode while viewing the calculations. However, the rounding is correctly calculated in the “make-to-order” explosion mode. This leads to discrepancie...
Add dimension name & description (e.g. colour name & description) to the variant suggestions form
When a user creates product variants for a product master, they can use the 'Variant suggestions' function to select from the available colour, size, stye dimensions on the product master to create product variants.
The issue with the 'Variant suggestions' form is that it only...
Add 'Modified by' field available to be added to 'Sizes' table (RetailEcoResSize)
'Sizes' table (RetailEcoResSize) has 'Modified date and time' field, but lacks 'Modified by' field. This is a very informative field to be utilized with already existing field 'Modified date and time' and can be used to track changes made by end users (in cases where customer needs to know onl...
Option to display size, color and style ID and name where product variants are displayed
Dynamics 365 dimensions like size, color and style (RetailEcoResSize, RetailEcoResStyle, RetailEcoResColor) only contain 1 value field. So Dynamics expects you to use values that are readable/recognizable. If only numeric values are used it will be almost impossible for users to recognize whic...
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
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