Get rid of domain separation

vanessaheux
Tera Contributor

‎01-25-2018 12:52 PM

Hello


My instance is domain separated (by groups) and I'd like to get rid of this domain separation as I only need one global domain.

I have the list of all domainized tables but even if the documentation explains how to get rid of domain separation, it is not very clear how the system will react.

Imagine 2 groups "comp A" and "comp B".

This means 3 domains created : the global and the domain group comp A and the other comp B.

A domainized table can have entries on global, comp A or comp B domains.

All my users today are in comp A only. But I have very huge number of items defined directly on global or in comp B domain.

How could I get rid of my domain separation ?

  1. 1. I can't delete all comp B domain records in all domainized tables as there are really too many tables and too many entries (as I would have imagined to delete all the records in order to deal only with my comp A)
  2. 2. I can't reset all the records to global domain as all records from comp B domain could give results I don't want
  3. 3. I can 't delete the group comp B as it automatically reset all records on domain comp B to " " and then if I get rid of my domain separation, I   will also have first to reset the records on domain " " to global which is false.

Does anybody here succeed to get rid of domain separation ?

Or is anyone has an idea about it ?

Regards

Vanessa Heux

Labels:
0 Helpfuls
  • 1,537 Views
2 REPLIES 2

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

‎01-25-2018 12:59 PM

Hello Vanessa,



You may find the below blog helpful.


How to Deactivate Domain Support


0 Helpfuls

vanessaheux
Tera Contributor
In response to Pradeep Sharma

‎01-25-2018 02:04 PM

Yes I saw that blog but my question is what will become records existing on domain "comp B" that do not interest me ?


They belong to another company which is not mine and most of them are active.


So when I fllow the blog and reset all records to global domain, all those records from comp B will belong to global domain after (like all those from comp A).


Thus I'm pretty sure that I could have many problems for all those records becoming from comp B.



And as I told you, deleting all the compB records could be a nightmare as really too many records.



Even without of those comp B records, I don't know what will happen when my comp A records will coexist with all old "global" records.


0 Helpfuls