Conditions field getting truncated

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2016 12:00 PM
I have a condition field:
I upped the max length to 8000 as an attempt to see if it would help. The max length was originally the default length of 4000.
The condition is truncated when trying to save the following condition:
Notice that the condition string in the xml is truncated at 40 characters.
I've tried changing the max length as already stated. I have also dropped and re-added the column.
Any ideas? *This is in my free developer instance:
Build name: Helsinki
Build date: 06-05-2016_1542
Build tag: glide-helsinki-03-16-2016__patch1-05-18-2016

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2016 12:23 PM
I created a brand new table outside of my scoped application and the condition field works fine. Guess I might have to rebuild my table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2016 07:49 AM
I've added another Condition field to the table that I recreated and now it is truncating. Has anyone else experienced this? I obviously can't keep recreating the table every time I want to add a field.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2016 02:17 AM
Hi,
Have you checked the details in System Logs > Table Changes module. What information is written into the table?
I have seen this type of error in our production, if a large change has been saved e.g. in the task table and it has failed:
This is what you would see in the Node Log File Browser after a failed field length update:
There is a HI-portal KB-article related to this:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0547328
And this is fixed by editing the UI Transactions -Quota Rule to include:
So if your field length updates are still failing, try to find more information from the Node Log File Browser. Maybe your are having timeout issues?
All errors/warnings and additional information related to the update in question is written to the log.
- Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-02-2017 03:26 PM