I'm having issue with Domain reference picker

[ccorscadden]

Hi I've recently start learning Servicenow and I've activated the Domain separation plugin for my instance to have play around with those feature.

I wanted to try my hand at using domain visibility by giving a domain visibility of another domain with the same parent but domain reference picker is only providing me access to child domains and the domain itself. Which doesn't make alot of sense to me, why would the reference picker only give me domains that my domain already has visibility of. The same happens for the domain picker for the domain contains field and the reference picker for the parent domain(which makes no sense at all because selecting one of the child domains would cause a circular dependency).

If I turn off the data separation from the configuration view I can fix my issue but this isn't exactly ideal solution. If anyone experienced with Servicenow domain separation could tell me where I am going wrong it would be much appreciated.  

[Michael Fry1]

Giving a domain visibility doesn't put the domain in the picker. If you are in the Parent domain for both of these domains in question, you won't notice anything since you already have access to the domains. If you impersonate someone in the domain with visibility rights, they will have access to the other domains records.

Does that help?

[ccorscadden]

Not really my issue isn't with domain visibility by itself, when I have been able to choose the domain I want a group to have visibility of it works fine but I shouldn't have to turn domain separation on and off from the config view to be able to see domains that the group doesn't already have access to. It is like what you said "If you are in the Parent domain for both of these domains in question, you won't notice anything since you already have access to the domains" but when I go to the slushbucket for domain visibility the only option I have available is the domain the group is apart of and all of it's children, I don't get the option to choose other domains that group doesn't already have visibility of.

I'm having this same issue with domain contains as well. The example MSP domain has a contain relationship with TOP but can't replicate that relationship with another domain because when I go to make that relationship the only options I get provided are the child of the domain I'm giving the contain relationship to. I can't give ACME domain the contain relationship with TOP but clearly from the MSP example I should be able to.

[Michael Fry1 · Accepted solution]

Let me try again . . . check your Properties. If the 2 below are checked, it's causing your problems. I have the same problem where I have to uncheck those, make my change and then recheck them. If I understand, I think that's your problem.

[ccorscadden]

That's interesting your domain admin module has more views than mines. I unfortunately don't have the properties view that you are showing me but I'm guessing that is because I'm using a free developer instance. I'd guess that the domain separation plugin isn't as feature complete as the plugin for a proper instance.

I'll have to try this once I get my hand on a proper instance, thanks for you help Michael.