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.
Data not transferred from one form to another when content of description is more than 4000 characters - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Data not transferred from one form to another when content of description is more than 4000 characters
KB0695409

Data not transferred from one form to another when content of description is more than 4000 characters


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

Issue

Symptoms


Data not transferred from New Call to request when request initiated from call and content of description is long if it has more than 4000 characters.

Release


ALL

Cause


System property "glide.tiny_url_min_length" changes the url to tiny support url if the number of characters exceeds the specified value in the property. 

Resolution


-- By default the value of property "glide.tiny_url_min_length" is 1024 characters, so when we are trying to pass description with more than 1024 characters, the url will change as below
 
Decoded url: http://<instance-name>/nav_to.do?uri=/com.glideapp.servicecatalog_cat_item_view.do?sysparm_tiny=f4498c6ccccc2300964faf77e5defea3
 
-- So when we try to get the "sysparm_additional_information" query parameter in our client script, it will return undefined.
 
-- Tiny url creates an entry in the "sys_tiny_url" table, and as you can see it passes the sys_id of that record in the above URL
 
-- To handle this scenario you need to fire an Ajax call on "sys_tiny_url" table and fetch the record with sys_id, there you will get the value of the field that has long valu..

Additional Information


Here you can read more about 'Examples of navigating by URL':

https://docs.servicenow.com/csh?topicname=r_NavigatingByURLExamples.html&version=latest


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.