- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2014 09:27 AM
I know this might sound crazy, but, currently I am having issues with a long condition I need on a business rule, and the current size of the field (254) is not attending my needs. Do anyone knows of any impact of changing this size to maybe 400 ?
What I need to know in summary is, if I change the size, will it continue to work as usual?
Thanks and regards,
Felipe
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2014 11:54 AM
Hi,
So there are two ways:-
1. Best practice of ServiceNow is to write a script include and call it in the condition. The Script include will do all your calculations and return true or false. This way you do need to update the OOB feature i.e. length in your case & so you will not have any upgrade issues in near future.
2. If you still want to go with the same, then you can surely increase it, but remember that it will not be updated by the Upgrade process when you do an upgrade form your current version to the version out by ServiceNow.
Thanks
Ashish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2015 01:58 PM
It should be up to Felipe Bueno Barbosa to mark it correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2015 02:15 PM
Thanks Geoff!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2016 06:21 AM
I would like to add that, if you decide to go ahead and change the field max_length value, the best way to do this would be:
1. Make a backup of all the records that will be impacted with the change, from the table and the children of that table
2. Change the max length on sys_dictionary
3. Import the conditions back in case they went missing
It might happen that, depending on the length of the field, in the database end, the column typo changes from a varchar(length) to a mediumtext, and if this happens, the content of that field is lost of all impacted records.
Cheers!