Using update sets with domain separation configaration - best practice?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2015 01:26 AM
We are planning to implement a domain separated structure with several domains under the top, each having some unique configurations. Now we are only testing it in a developer environment, using one update set and backing it up regularly.
Normally (in a non-domain separated model) it is enough to export the update set and import it to another instance (e.g. other dev or a non-prod), and it works like a charm, but what about importing an update set from a domain separated structure? What is the best practice to do that? We've just had our first try, but ran into hundreds of errors. Does the update set contain everything about the domain separation? Or do we have to manually configure the hierarchy first before importing the update set?
Thanks for sharing your experiences!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2015 07:45 AM
It would likely be best to move your domains over as an XML update set.
Pretty sure managing domains is 'data' and so would not move over in an update set.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2015 08:04 AM
Hi Akos,
Please refer the below link for more info on Update Set best practice.
http://wiki.servicenow.com/index.php?title=Update_Sets_Best_Practices#gsc.tab=0

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2015 09:23 AM
Domains usually do not get transferred in the Update Set, so yes, setup domain structure first.
Loading the update sets is the same except you need a company field which maps the domain on the record. You can just use a script on the transform map to set the company. Example:
if (source.u_company == '')
target.company = '8b053d26dc7a3dc83a71074814145f9a';
The company field needs to be in the Maps Fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2015 10:32 PM
Hi Michael
Even we do have the same kind of requirement.
We are trying to move an update set from a domain separated instance(Non-Prod) to another domain separated instance(Prod).
How can we achieve the perfect results.
I want to know what are the per-requisites before we go and move the update sets from one instance to another.
I have already tries doing this, i only get the preview records button/commit only if i change my domain to "Global".(I want my update set to be part of my specific domain not in global domain).
Even though i did change my domain to global and then tried to commit, i get few error where in My application, modules and workflow throw an error, and cannot be moved to that instance.
Please help how can i move in whole update set from one instance to another in a domain separated SNOW Instance.
Thanks in advance.
Darpana