How to decrease the limit of records of a Lookup Selectbox variable?

Rufino · ‎04-25-2023

I know that the maximum limit of records that a Lookup Selectbox variable can show is 10000. I wanna to decrease this value to have a better performance on my catalog item.

Is this possible? If yes, how can I do that?

Rahul Kumar17 · ‎04-25-2023

Hi,

Yes, it is possible to decrease the maximum limit of records that a Lookup Selectbox variable can show in ServiceNow. You can achieve this by modifying the glide.ui.lookup.max_rows system property.

To modify this system property, follow these steps:

Log in to ServiceNow as an admin user.
In the navigation menu, go to System Properties > All.
In the search bar, search for "glide.ui.lookup.max_rows".
Click on the "glide.ui.lookup.max_rows" property to open it.
Change the value of this property to the desired maximum number of rows that should be displayed in the Lookup Selectbox variable.
Click the Save button.

By default, this system property is set to 10000. By decreasing this value, you can improve the performance of your catalog item by reducing the number of records that are loaded into the Lookup Selectbox variable. However, be aware that setting this value too low may limit the functionality of the Lookup Selectbox, as it may not show all the necessary records.

Thanks,

Rahul Kumar

If my response helped please mark it correct and close the thread.

Thanks,
Rahul Kumar

View solution in original post

Joe S1 · ‎04-25-2023

Hello Rufino,

A Lookup Select Box is just a dropdown view of a table of choices. You can limit the number of values that come back with a Reference Qualifier on the field. I'm curious though, if you have so many choices why not just use a Reference type field instead of a LSB?

Rufino · ‎04-25-2023

I was using a reference field, but my end users doenst know the contains (* before a search) funcionality. They are always complaining that dont find their numeric sequence.

I'm trying to give to they a better user experience on a catalog item, because they need to find a numeric sequence, but some records have zeros in front of them (example in prints bellow).

I don't know why, but when I use a Lookup SelectBox, the contains(*) functionality comes in background. That's why I'm using it.

Joe S1 · ‎04-25-2023

Thanks,

You can switch the default search context on reference fields to a "contains" search. However this is a system property and thus would be a platform wide change that would affect all reference fields.

Enable contains auto-complete searches

Rufino · ‎04-25-2023

This is what I'm avoiding. I don't wanna change this property because gonna impact all the plataform. It's just for this specific catalog item that we have this issue.