Scoped app - Configure a specific sys_ref_list view?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 07:18 AM
Hello ServiceNow Developers,
I am working on a scoped application that uses the core_company table (read-only).
I have a requirement to show specific company fields when looking for the records I want (let's say "vendor", "customer", ...)
My issue is: the view opened when clicking on the reference lookup search (magnifier) is forced to sys_ref_list and this view is global so I can't change it from my scope. Anyway, I would not like to change this view as other applications and the global scope may already use this one with the fields showed (see screenshot attached).
So I would like to know if there is a way for me to force the view showed for this very "Company" field.
I have created a specific view on the company table
I even created a view rule (global scope) to force my custom view for users with my application role, it works on lists, on forms, but not on this specific context...
Thank you

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 07:32 AM
Hi,
See below link.
Thank you,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 07:41 AM
Hello Ashutosh,
Thank you for your answer, but this is not what I am looking for.
I am talking about the sys_ref_list view, when clicking on the Reference Lookup icon. Not about the sys_popup when clicking on the Reference icon (see difference here: Decorations )
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2020 03:37 PM
Pierre,
Did you ever come up with a solution? I have a similar use case.
Thanks,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2020 03:00 AM
HI Michael,
Unfortunately no, we ended up working out a compromise between the Application Owner and the Platform Owner to add a few fields on this default view