string field characters getting truncated on saving the form.!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 02:27 AM
Hi,
I have string field in a table which is derived from task table. max length is given as 4000, but when i save it it gets truncated to 40 characters exactly.
There is another string field with 4000 characters as max length in the same section of the form. but that is working absolutely fine!.
Do anyone have any solution for it?
Note: this is issue is only found in QA(testing) instance whereas it works fine in DEV instance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2017 04:12 AM
I mean if the number of fields in your Dev and QA instance are same or not. If there are additional fields then it might be causing the issue.
Also check if there are any unused fields with large size (4000 characters) that can be deleted.
Thanks
PS: Hit like, Helpful or Correct depending on the impact of the response

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2021 06:41 AM
I just had the almost identical thing happen to me. I am trying to add a Reference qualifier (a string which is filter logic) to a Dictionary Override for the change_request table. This overrides the task table's Reference qualifier setting. The string I am trying to add is over 255 characters, so I increased the length of the Dictionary override table's field "Reference qualifier" from 255 characters to 1024. I was able to get this to work in one of my Development environments. However, when I promoted this to our Quality Assurance environment (xxxxxxxxtest.service-now.com), the field is truncating at 255 characters, despite the fact that the field's length value is set at 1024.
Service Now - there must be an explanation. Why is this happening?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2022 10:23 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2022 12:29 PM
Kalpana, here is what I recall. I quickly resolved my problem by reconsidering the logic that made up my reference qualifier. Once I chose a more efficient logical statement, that was shorter (under 255 characters), it eliminated my need to solve the "mysteriously" reimposed 255 character limit. My guess is that I was able to temporarily increase the field length, but as soon as other, unknown to me, logic fired, it reset the field length back to 255.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2022 12:30 PM
I would still like to get an explanation from Service Now - what is that "unknown to me" logic that is capping the reference qualifier at 255 characters.