Skip to main content

Why objects can’t upgrade (ServiceNow)


ServiceNow unable to revert an object to baseline during an upgrade - presented with an error

When a hotfix was provided on a protected script for example

look at the hotfix update set to check if the Replace on upgrade flag is set to true for that file in the update set?  If it is set to false it can cause this issue.  If it is false change the flag in the update set to true which should allow the file to be reverted to the baseline, release version.



Just setting the flag in the already-applied update set seems to do the trick
Labels:

Comments

Post a Comment

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...
Post a Comment
Read more