sys_choice element length update impact

[Ravish Shetty]

i am updating the length of the field 'element' in sys_choice to 100.

this is being done because with the current length of 40 i am facing issues with studio apps which have length over 40 and because of this the dropdown values do not reflect correctly.

is there any impact if i increase the length of this field?

[Ravish Shetty]

bump

[J39]

Hi Ravish, 

Did you end up increasing the length of the field 'element' in sys_choice?

If so, have you encountered any issues?

I don't understand why ServiceNow would allow up to 80 characters for a field name, but then leave the sys_choice.element length capped at 40 characters. Seems like an oversight.  But I have over 100 fields that I need to change from String to having Choices, and am considering doing as you asked about - increasing the Element max length to 80 to match a column name's max length.  I really don't want to have to either recreate these fields, or create a reference table for choices.

In any case, I'm curious if you ended up increasing Element's max length or not.

-Joe

[Ravish Shetty]

we didn't increase the length. i re-created fields with shorter names

[J39]

Thanks for the response Ravish.

I've confirmed that increasing the max_length of the sys_choice.element column to match the max_length of a field name (80 characters) does allow fields with more than 40 character long field names to be configured with Choice lists.

So we're going to request permission from our admin team to implement that change, instead of trying to rename over 100 fields to be 40 characters or less.

I'd love to hear if anyone else has implemented this change and, while I can't envision it, I'd love to hear if they had any negative fallout from it.

Thanks again Ravish.