- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2015 12:04 PM
Below are the steps that I followed
- On one Fuji instance, I have published my Application to update set
- I have exported above update set to xml file.
- After that I have imported xml file to another Fuji instance.
- Now I am trying to preview the update set, but preview fails with error
Cannot commit Update Set 'xyz' because: Update scope id 'xxx' is different than update set scope id 'global'. Resolve the problem before committing.
Other observation- Publishing application to other Fuji instance is working fine.
What I am missing while importing xml update set to Fuji instance? Any help on this issue will be highly appreciated.
Thanks in advance.
Best Regards,
Rahul
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2015 06:48 AM
I just found the problem that was causing Rahul Borate issue. The issue was caused by an old UI Action from the pre-Fuji Certified Application Support update set. The UI action is "Export to XML" on the update set form. The solution is to revert the UI action to the Fuji release version.
The Certified Application Support update set should not be installed on Fuji instances since this function has been replaced by the "publish to store" action.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2015 06:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2015 03:45 AM
Hi Pradeep,
I hope your doing well and thanks for your response.
If I publish Application from Dev Fuji Instance to test Fuji instance then application creation and its scope creation happens successfully. No issue around this.
My requirement is to keep the back up of my work. For that, on Dev Fuji instance I have published application to update set and that update set is exported to xml file. I imported update set xml file on Test Fuji instance. Now, when I run preview for the update set it fails with error - "cannot commit Update Set 'xyz' because: Update scope id 'xxx' is different than update set scope id 'global'. Resolve the problem before committing."
My observations for error:
On test instance, I crated scope for my application under "sys_scope" table manually. (Here, application name and scope name I used as per my Dev instance). Now If I run preview again on test Fuji instance, then preview result is successful. In addition, commit is also successful.
Could you shade some light on below or do you have any pointer for solution?
It looks like, in update set "Export to XML" task, the ServiceNow do not add instruction in xml file to create application and its scope name under "sys_scope" table.
Thanks in Advance.
Regards,
Rahul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2015 06:48 AM
I just found the problem that was causing Rahul Borate issue. The issue was caused by an old UI Action from the pre-Fuji Certified Application Support update set. The UI action is "Export to XML" on the update set form. The solution is to revert the UI action to the Fuji release version.
The Certified Application Support update set should not be installed on Fuji instances since this function has been replaced by the "publish to store" action.