Rename ITEM NO

JAYESH wrote:

The item is used from long time and its consists lots fo entries.

the system will go thru all related tables and change it everywhere. If this is an old item and your DB is larger than 10gb - I suggest you do this over a weekend because it will take a lot of time.

we usually just make a new item# - it's not worth the trouble for us. Then set the Substitues item# for the old item to the new item.

This way if anyone accidentally enters the old # on a sales order then new item # will come into play.

Savatage wrote:

JAYESH wrote:

The item is used from long time and its consists lots fo entries.

the system will go thru all related tables and change it everywhere. If this is an old item and your DB is larger than 10gb - I suggest you do this over a weekend because it will take a lot of time....

Its very fast on SQL though.

garak wrote:

yes on SQL Server its fast, but u must sure, that all table are changed:!:
In same cases you can't use the Tabelrelation Propertie and must develeop the relation by using the lookup triggers. These records in rel. Tables are not changes. so, you must do this manuell / function after Rename.

I mean its an bad idea to rename Primery Keys with many entries in rel. Tables. Its also locks the tabels.

Well there is not much you can do to allow for poor programming practice. But yes you are correct that there are some bad developers out there that don't know how to follow Navision standards and can mess up a database.

I have never had an issue with renaming Items.

If there is an external POS system connected via an interface with daily batch imports, renaming the item can cause lots of trouble because the item nos. don't match during the renaming and processing. NAV has the new no., the POS system sends the old one until the next export ( and successful processing in the POS) of the changed item.