Importing through data entity "Released products V2"
Unnecessary field "CostCalculationBomLevel" as it doesn't allow the user to edit the field and that may lead to confusion for the user, it should be removed or be edited not restrict the action upon it.
Configuration models
If you define large range for integer attribute type then we can see performance issue when calculating constraint
It is expected that the calculation of feasible solutions takes longer time when the range of the calculation is bigger. We have so far improved the performance.
However, if you have any more suggestions we can keep this idea open to capture them.
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft
Free txt integer attribute and defined calculation based on it.
Free txt integer attribute and defined calculation based on it.
The problem is that when we define a value which is out of the range, we get model in contradiction error with no details on it.
Customer will need to get more details on the attribute which is failing.
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
An issue with readiness policy of an engineering version, and you get an error message: ”Processing BOM table and BOM version for item 30000-657.BOM version conflicts with version 30000-657-large-v1. Check date interval, from quantity, and site.”
In our scenario, it is important to our customer to automatically work without this warning message, not to be manually deactivated for the BOM and Route. Please consider this in the future releases.
Hi, thanks for your input. We'd like to understand the issue better. Could you explain what are the repro steps you are following or what you are trying to accomplish that it is not allowing you to?
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft
AI Item master
Hi
Auto alpha numeric number sequence with respect to item group
Ex: item group FG : number sequence auto generate as FG0001.....,,,,
Ex : item group RM : number sequence auto generate as RM0001....
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
Dynamics 365 Recycling description field within the product information descriptions
Wish there is a field to maintain the item recycling description within the description group of fields (e.g. features, introduction, specification....)
Not featuring or including the recycling field description, user may potentially track outside the system or conventionally ...
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
To be able access view only for some users in the product categories from Released products page.
To be able to access view only to some users in in the product category page after opening it from released products page.
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
The volume field in the manage stock tab of the released product is not a calculated field, when will this become a calculated field?
Would it be possible for MS to add a parameter to the volume set up to mark as Yes if the product is cubic metre on the release products form? The majority of products will be, and this will allow for both cubic and spherical.’?
Item Master Screen :
- Volume field NOT...
STATUS DETAILSDeclined
It is by design that the volume is not calculated as there could be cases where the product is not cubical.If for your case, it is always cubical, you would need to defaultField() method on InventTable table to add some defaulting.
Allow the Unit Sequence Group to be populated on Released Products even if the the smallest unit is not the 1st in sequence
We have populated the Unit Sequence Group ID field on our released products.(This happens after released product creation)
The issue occurs when we do populate that field with the following combination of parameters initially.
Purchase UOM – Cs
Inventory UOM – Pc
...
Thanks for your input! Are you able to provide a document with the specific repro steps, what the system is currently doing (the error you are seeing) and what you are expecting?
We would like to understand better the issue.
Thanks,
Beatriz Nebot Gracia
Product Manager, Microsoft
Correct Spanish translation: "Multiple" field for Purchase order, Inventory and Sales order
The appropiate general Spanish translation for the "Multiple" (en-us) field for Purchase order, Inventory and Sales order in the Default order settings form, from the Released products option in the Product information management module, must be "Múltiplos"
The word "Varias" w...
Thanks for highlighting this translation issue. We treat this as a bug and will address this in a future release.
Sincerely,
Søren Vagn Andersen, Principal Group Product Manager, Microsoft Dynamics 365 Supply Chain Management
Administrator
Thanks for your input! We will be looking into this issue.
Sincerely,
Beatriz Nebot Gracia
Product Manager, Microsoft