Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Variables are not visible in Service Portal for some catalog items - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Variables are not visible in Service Portal for some catalog items
KB0749918

Variables are not visible in Service Portal for some catalog items


3895 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

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) 

Release

All versions and releases affected.

Cause

Issue occurs when variable names are the same as the variable set names.  These should be unique under best practices.

Resolution

Variable 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.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.