How to set the number of records initially loaded for a reference field on Service PortalDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Description This article explains how to limit the number of records which are initially loaded when clicking or searching in a reference field on Service Portal. Procedure Create the following property in the instance and set the value as needed: Name: glide.service_portal.ac_max_search_matchesType: integerValue: <number_of_records_to_display> Applicable Versions Kingston Patch 11 and aboveLondon Patch 4 and aboveMadrid and above Additional Information Before Kingston Patch 11, London Patch 4 and Madrid, the default number of records displayed initially was 20.After the above mentioned builds the default has been increased to 100 as a fix for PRB1291290The property glide.service_portal.ac_max_search_matches is not in the database by default, hence the need to create it.When using this property beware of the following, if the value is: Too high, you'll impact performance.Too low, users risk seeing "no matches found" if they don't have read rights to see the first N records returned from their query.