In Service Portal, g_form.setValue does not work in List Collector variables when displaying large dataIssue <!-- 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; } --> Symptoms No values are displayed in a List Collector variable when the table has large data and the g_form.setValue API is used. Release All current supported versions. Cause g_form.setValue API is not supported for List Collector Variable. However,List Collector with glide_list attribute works correctly with the g_form.setValue API. This is documented in the topic Types of service catalog variables. Where the following two important lines can be found: Only when the glide_list attribute is true, can you set a value for this variable using a setValue() function in a catalog client script. Table with large data causes performance issues when loading the page. Use reference qualifiers to reduce data or use the glide_list attribute. Resolution Set the List Collector with glide_list attribute to true, be aware large data causes performance issues.