Can the field "replace on upgrade" be set to true automatically even if the record has been customized?

hasnalakhrissi
Tera Expert

Hi community!

It looks like the upgrade doesn't consider the field "customer update" for skipping or overwriting customized oob objects. Rather than that, it is the field "replace on upgrade" on sys_xml that is considered for that matter. My question is : we noticed that for a ui macro this field is set to true even if we have customized it, which caused the upgrade to overwrite it. Is there any explanation to this strange behaviour? We are sure that is haven't been set manually.

1 ACCEPTED SOLUTION

Lane Roberts
ServiceNow Employee
ServiceNow Employee

Hi hasnalakhrissi,

 

What you are describing here sounds like a known problem that we just wrote up a known error article for today. that you should be able to find it in the Known Error Portal within the next day or so. 

The problem itself is expected to be fixed in the London release, and we are currently reviewing it for back port to earlier releases as well.

Regards,

- Lane Roberts

 

View solution in original post

5 REPLIES 5

Lane Roberts
ServiceNow Employee
ServiceNow Employee

Hi hasnalakhrissi,

 

What you are describing here sounds like a known problem that we just wrote up a known error article for today. that you should be able to find it in the Known Error Portal within the next day or so. 

The problem itself is expected to be fixed in the London release, and we are currently reviewing it for back port to earlier releases as well.

Regards,

- Lane Roberts

 

Thanks for your reply! Can you please provide the related article?

Should be this one: https://hi.service-now.com/nav_to.do?uri=%2Fkb_view.do%3Fsys_kb_id%3D773ec41ddbac1b00032a7a9e0f961964

 

Regards,

- Lane Roberts

antoinebenzerar
Kilo Contributor

Hi Hasna,

 

This community post and answer might prove usefull to you:

https://community.servicenow.com/community?id=community_question&sys_id=fc790b65db5cdbc01dcaf3231f961960&view_source=searchResult

 

I  tried to find the known error article but nothing came up. Hope it helps