Catalog client script is not able to autopopulate the lookup select box variable.Issue In catalog items there will be variables that will be referencing the existing tables in the instance.The issue here is the variable is not being autopopulated using the catalog client script where it is setting the value based on the logged-in user cost center. Steps to reproduce:1.Create a catalog item by applying the command 'sc_cat_item.do'2.Create a variable 'cost center' with the lookup select box type referencing to the cmn_cost_center table.3.Create a catalog client script with the setvalues for setting any of the cmn_cost_center record.4.Now open the catalog item and try it.5.We can observe that the cost center variable is not auto populated.CauseThe access control restriction is causing the issue.If there is any access control restricting the access to the cmn_cost_center table then the catalog client script will not be able to set the value as the choices itself will not be present in the variable.ResolutionThere are two ways to resolve the issue.1.Provide access to the table 'cmn_cost_center' instead of restricting the access then the choices would be visible and the catalog client script will work fine.2.Another way is to change the variable type to single-line text so that there would be no requirement of choices display and indeed the restriction issue would not occur.Related LinksCheck if the variable internal name is given properly in catalog client script.Check if the choice internal value is given properly catalog client script.