Variables are not visible in Service Portal for some catalog itemsIssue <!-- 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; } --> Variables are not visible in Service Portal for some catalog items. Upon opening the affected catalog item in service portal the console will give the below error. RangeError: Maximum call stack size exceeded at useDisplayValueForValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54777) at Object.hasValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54757) at Object.get (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:64403) at Object.hasValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54757) at Object.get (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:64403) at Object.hasValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54757) at Object.get (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:64403) at Object.hasValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54757) at Object.get (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:64403) at Object.hasValue (js_includes_sp.jsx?v=02-14-2019_1004&lp=Tue_Feb_05_08_46_43_PST_2019&c=6_56:54757) ReleaseAll versions and releases affected.CauseIssue occurs when variable names are the same as the variable set names. These should be unique under best practices.ResolutionVariable name and variable set name should not be the same, this is not the best practice. Make sure variable names and variable set names are unique in the instance.