Update set movement in domain separated instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2025 08:53 PM
Hi everyone,
We’re facing a strange issue in our domain-separated ServiceNow instance and wondering if anyone else has experienced this.
We made some changes to case and incident form fields in our Dev instance under a lower domain, then moved the update set to UAT. Since we can’t commit update sets in the lower domains directly, we switch to the global domain before committing.
The problem is — once we commit the update set in UAT (as global), it ends up creating duplicate sections on the form. One appears under the global domain (new section created) and another under the lower domain(updated the section as expected). The updates apply correctly to the lower domain, but we now have this extra section in global, which causes confusion.
Has anyone run into this before? Any ideas on how to avoid these duplicate sections when moving update sets from lower domains to global?
Appreciate any help or suggestions!
#csm #domain #domainseparedinstance
Thanks!
Khalid