Comments
Would be even better if items could change Product dimension group and to go from Product to Product master.
Category: Product Information Management
While I do agree that the function of editing a product name is important. The reason should not be mark it as obsolete or 'ZZ' to resort it. This should be the function of the Product Lifecycle State to determine the behavior in the UI, for example no longer display this end-of-life item in a drop down for order entry. please see idea: https://experience.dynamics.com/ideas/idea/?ideaid=6a9f26a2-407f-ec11-b820-0003ff45920b
Category: Product Information Management
I honestly cannot recall the number of implementations where this has been a much-needed feature. Bring it back Microsoft! Be a hero!
Category: Product Information Management
This is a must, not a nice to have - renaming items is essential for our business
Category: Product Information Management
I will throw my hat in the ring requesting this feature back. This is a huge loss in functionality.
It is understandable why Tracking/Storage Dimensions and Reservation Hierarchies cannot change for a product with transactions, but there are certainly valid reasons why we could need to change how these items are handled. Our example, changing from a "Batch Number" controlled item that now needs to be tracked by serial number is no longer possible. The only solution available is to change the part number, which is not a viable business practice.
Category: Product Information Management
Hello ,
we want it back as well
Just fix the inconcistancy error instead of disabelling this function
Category: Product Information Management
The item setup may be incorrect therefore we need the function to allow the user to correct it after inventory transactions exist.
Category: Product Information Management
Need this back, it's a huge problem that there's no item rename functionality in Dynamics!!
There's also no good way to retire items (de-activate). Having to rely on "stopping" items in default order settings is not a good solution. There should be a category built into the released product which allows an item within a legal entity to be deactivated such that the item cannot be used going forward. This should carry through to all major places where an item can be used.
Category: Product Information Management
We are preparing to upgrade from AX2012 to D365 and we see this as a major concern. Our product numbers are controlled in our PLM system. If a user makes a mistake at creation of a product in AX and the mistake is in a field on the item that cannot be changed once transactions occur, we will rename the existing number by adding "ZZ" as a prefix so that it goes to the bottom of the list and then create a new record for the part number using the desired/correct product number so that both of our systems (PLM & ERP) are in sync. This happens primarily if the incorrect model group is selected, if we should have created a product master, but created a product, or if we need to modify the tracking dimensions. Either provide work arounds for those issues or bring this back. We will be actively working with our partner to solution this as we kick off our upgrade. I see it is under review, so I hope it gets resolved before our GO Live. Thank you!
Category: Product Information Management
Dear Microsoft,
We have used this functions many times to rename items with transactions without issue and avoid any data corruption. An error is required when entering the item number when creating an item or making changes in business requirements.
Note: Some users create the item with space or incorrect information and need to rename it without deleting the items
We appreciate your understanding and we need to update the feature in the new release without any change in performance and avoid any current and future data corruption
Regards,
Yasser El-Hawary
Senior Consultant
PROART Consulting
+201007354710
Category: Product Information Management
Beatriz Nebot Gracia (administrator) on 9/18/2020 8:15:14 AM
Thank you for your feedback. Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap long term roadmap.
Sincerely,
Beatriz Nebot Gracia,
Program Manager, Microsoft