- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2018 11:59 AM
What are the impacts of using queryNoDomain() in an instance where Domain Separation is NOT enabled. Will it have any impacts ? The reason I ask is because, I see a behavior related to this method where it works fine some times, and it doesn't in some cases.
Sample Script:
var usr = new GlideRecord('sys_user');
usr.addQuery('active', 'true');
usr.addQuery('user_name', userid);
usr.queryNoDomain();
if(usr.next()) {
//further Code goes here
}
Thank you,
Aman Gurram
Solved! Go to Solution.
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2018 12:13 PM
It should not really matter, but I would just switch back to "query" instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2018 12:24 PM
Thank you for the responses. Ill do some more research ad debugging and update this thread.
Ill change it to query() anyways to be on safe side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2019 04:27 AM
Hi,
According to doc :https://developer.servicenow.com/app.do#!/api_doc?v=newyork&id=r_GlideRecord-queryNoDomain_Object_Ob...
queryNoDomain() works similar to query() in case domain sepration plugin is not enabled.