Service Catalog | Troubleshooting - A lookup select box variable points to an extremely large table causes performance issues when catalog item loadsIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } --> A lookup select box variable pulls available choices from any table specified in the "Lookup from table" field. A catalog item or order guide with a Lookup Select Box type variable may experience these symptoms: Catalog item takes a long time to load (same on Service Portal)Order Guide on Service Portal takes a long time to loadCatalog item on an order guide takes a long time to load CauseWhen the lookup select box type variable is configured with an extremely large table, the system will pull in all available values from this table and display them on the catalog item order page. In most cases, the available values are available from the Choices [sys_choice] table. The best practice is to use the Choices table whenever possible. Otherwise, use reference qualifiers to control the number of values returned. For example, the Incident table has a preferred contact type field with choices like email, phone, web. A lookup select box variable was used in a catalog item with Incident table as the lookup from table field. This will evaluate the whole Incident table field and provide the available options. If the incident table grows, a user will experience slow performance. In this case, it is better to refer to the Choices table where the options for the preferred contact type field of the Incident table is stored. There will be only 3 options and catalog item will load significantly faster.ResolutionThe performance issue is related to a large number of results that have to be retrieved and displayed on the screen. Control the number of results by using reference qualifiers to help lower the data retrieved. Questions to ask: Are all the data retrieved needed? If not, what reference qualifier to use to retrieve only the needed data (a subset of data)?Are the values available from the Choices [sys_choice] table? If yes, use the Choices table instead. The data retrieved from the Choices table will be significantly smaller. Can Select Box type be used or Multiple Choice type be used instead of a Lookup Select Box type? Any of these alternatives will help improve the performance on a Lookup Select Box variable type. For other troubleshooting articles related to performance, click here.