Replace on upgrade

[praveen86]

I see that the out of box customizations, lets say, business rules for example have a replace on upgrade field set to false as default value. Should it not be true by default considering that i have not made any changes to business rules??

[Michael Fry1]

I would think no. If you change something and forget to uncheck the box, your customization's will get over written. Otherwise, assuming you haven't changed it, the system knows to upgrade it whether the box is checked or not.

[Goran WitchDoc]

Yea, It might some contradictory. It sounds like it should have true and if you do something on it, it would go to false. But than again, not sure what this does. Since it keeps all the customization in the sys_update_xml table. So if you customize a OOB Business rule, it will end up there and that is where SN looks what to not replace on a update. Meaning that if you customized a OOB thing, it isn't enough to revert it to original version, you need to remove it from that table as well.

//Göran

[SebinDuke]

Hi,

This field determines if your component (business rule) for example should be replaced by System Upgrade. i.e. if this field is set to true it will be replaced will be replaced by service-now when you upgrade to a newer version of service-now.

By default all components that comes with service-now have "Replace on upgrade" set to true (so they will be replaced by their newer version when you upgrade service-now). For all components that you create (or comes with service-now but is edited by you) will have this field set to false (so they won't be replaced by their newer version when you upgrade service-now).

For more information please refer to 

Overwrite customizations during an upgrade

Thanks,

Sebin