How to correctly transfer scoped application and resolve application scope validation issues?

Todd O
Tera Guru

I have built a scoped application in my dev instance. It has many things (tables, forms, workflows, business rules, etc). My goal is to transfer the entire scoped application (from source instance) into another dev (target) instance. The problem is that I'm having errors during the import to my target instance and I'm not sure how to resolve.   Below are further details to clarify the steps I've taken thus far. Thanks in advance for any help here.

  1. I started with my source instance and navigated to the "System Applications -> Applications" section.   I then chose to "edit" my scoped application.
  2. Within the edit of my scoped application, I chose the option to "Publish to an update set." I then downloaded the xml output that it created during that process.
  3. Next, I went to my other target instance and navigated to the "System Update Sets -> Retrieved Update Sets."   Within this location I chose the "Import update set from XML." I proceeded to upload the xml file that came from my source instance described in #2 above.
  4. The import process worked but it contains over 1,200 errors.   Most of them look like the sample below. I'm not sure how to resolve. I tried a few things such as the following...
    1. I created an empty scoped application with the same name has my source application (i.g., 'TDO').   Then I tried "Run Preview again" on my update set but still same errors.

Sample error:

Cannot commit Update Set 'TDO' because: Update scope id '3dbfd5170f1b42008e030dbce1050e04' is different than update set scope id 'global'. Resolve the problem before committing.

p.s., I've read the SN documentation on how to resolve these types of errors but it did not address the items I'm seeing.

p.s., I've also read Cory's post about the philosophy of scoped applications and I think I'm doing everything correctly (although I must not be).

6 REPLIES 6

Lane Roberts
ServiceNow Employee
ServiceNow Employee

Hi Peter,



If your goal is to move the application so that it is only developable from the new instance, then after installing it on the new instance and verifying that you can 'Edit' it ok, then you would need to Delete the application from the original instance where you were developing it, in order to prevent any additional confusion as to which instance the application should be developed in in the future. Once the application is deleted, you could then download it from the Repo, and it would only be be read only at that point and no longer 'Edit'able.



Cheers,


Thank you, Lane.   That did the trick.   Once again, ServiceNow gives me the tools to "[re]configure without fear."