Is there any risk in renaming item name/number SKU numbers on inventory items that are used in assembly items?

AI generated answer (using internal Slack threads):

Renaming item name/number SKU numbers on inventory items that are used in assembly items does carry some risk. The main risk is that any existing references to the old SKU in your system, such as in open sales orders, assembly builds, or scripts, will not automatically update to the new SKU. This could lead to confusion, errors, or even data loss if not handled properly. If you decide to proceed with renaming the SKU, you should first identify all places where the old SKU is used. This could include saved searches, reports, scripts, workflows, and transaction records like sales orders, purchase orders, assembly builds, etc. After renaming the SKU, you would need to manually update these references to use the new SKU. An alternative approach, which is generally safer and recommended by many NetSuite professionals, is to create a new item with the new SKU, and then phase out the old item over time. This allows you to gradually transition to the new SKU without disrupting existing processes or data. You can use a CSV import to update open sales orders and other records to use the new item. In any case, you should carefully plan and test the changes before implementing them in your live system, to minimize the risk of disruption or data loss. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******