How can a URL do a lookup of a USER using their USER_ID?

[servicenownewbi]

Hi,

I'm new to ServiceNow, but have read the 'CTI' page, and 'navigate to url' page because I have to screen pop Service Now in a few different ways. I'm working on a customer instance, and have had difficulting finding a URL that pops Service Now to a page for a specific user:

Example:   USER-LOOKUP, where USER_ID = 206458353

https://<instance>.service-now.com/nav_to.do?uri=sys_user.do?sysparm_query=sys_user=https://<instance>.service-now.com/nav_to.do?uri=sys_user.do?sysparam_query=sys_user=206458353206458353  

What am I missing here? I don't have access to any administration pages for Service Now.

Also, if I navigate to a specific URL, for example (https://<instance>.service-now.com/task.do?sysparm_query=number=INC0261581)

how do I add URL parameters to populate additional data on the page?

Thanks!

Claudio

[Mike Allen]

You are using a field called user_id, not sys_id, so:

https://<instance>.service-now.com/nav_to.do?uri=sys_user.do?sysparm_query=user_id=206458353

or

https://<instance>.service-now.com/sys_user.do?sysparm_query=user_id=206458353

[servicenownewbi]

Hi Mike and All,

I tried https://<instance>.service-now.com/sys_user.do?sysparm_query=user_id=206458353

but I keep getting a specific (non-matching account) show up, and the 'Cost Center' field in focus, which I find strange. Is this standard behavior, or is it a customization gone wrong? Another vendor is handling service now administration. Do I tell them that the USER lookup is broken, because I'm not getting the right result? I just want to make sure I'm not missing anything here. Thanks all for the quick direction.

Note that I was able to get the lookup to work with the following URL:

https://instance.service-now.com/sys_user.do?sys_id=a56d52956f15610023314702be3ee4f5&sysparm_record_...

however, I have no idea how my 3rd party client application would get the current sys_id to open a new browser with this URL. Any ideas? I would prefer the simpler approach everyone has mentioned (without a sys_id).

Thanks!

Claudio

[servicenownewbi]

All,

Thanks everyone for your guidance. The issue was that the sysparm_query had to use 'user_name' instead of 'user_id' in the URL. Problem solved.

Thanks!

Claudio