Hi Keithgagne,
Thanks for sharing your experience above with domain separation. We also stuck in the similar situation and it started causing lot of issue specially with duplication of CI from discovery and other sources. This plugin was enabled mistakenly by user in prod/TEST and we cannot revert it back as per servicenow.
Well we have simple instance with ITSM pro and few integrations. We want to move all the data under TOP/Default to global domain and disable TOP/Default so it has only the default global visible and available for all users.
The challenge is how to analyze the data impacted by this change so we can make the decision carefully before making the suggested changes so we don't compromise with data integrity and platform behavior.
I cant update the domain to global for users or record using the admin right? does it requires security admin to make these changes. advice the best approach here to disable domain separation and move all data into global scope.
Regards
