40 character String field is defaulting to multiple line field

kemmy1
Tera Guru

find_real_file.png

 

I have two string fields one is 40 characters (Ticket Number) and the other is 160 characters.(Request Title).  I can't for the life of me understand why Ticket number is showing up as a multi line field and Request title is not.  I would like the Ticket number field to NOT look like multi line.

This is two new fields we are adding to our Change Request form/table.  I'm stumped.  I checked the attributes and the only attributes both have are edge encryption = true.  So I deleted the Ticket number field and added it again except instead of u_ticket_number, I changed it to u_508_ticket_number (sometimes when you delete and add a field with the exact same label and column name, it seems to just duplicate the field you just deleted).

Lisa

We are on Kingston.

1 ACCEPTED SOLUTION

nthumma
Giga Guru

It happens due to storage alias mismatch at the backend, even though you created with 40 max length but in the backend, it might be mapped to a multiline string. It's known the issue you need to open HI ticket to get it fixed. 

View solution in original post

4 REPLIES 4

Ankur Bawiskar
Tera Patron
Tera Patron

Hi Lisa,

So after you did the workaround is the issue still there?

Regards

Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

nthumma
Giga Guru

It happens due to storage alias mismatch at the backend, even though you created with 40 max length but in the backend, it might be mapped to a multiline string. It's known the issue you need to open HI ticket to get it fixed. 

So even if I delete it (which I did) and add it again it will still do this?  (that's exactly what is happening even though I created it with the same label but different column name.)  Ugh, I'll open a HI ticket.  I didn't think I was going crazy!  This is definitely a bug!

I really think adding fields via the Form Layout is really buggy.  I created three fields that were supposed to be Choice fields and they ended up being strings, and the third field didn't even get added.  Plus this Ticket Number field problem.  I did recreate the Ticket Number field on the table itself but still getting issues.

Thanks!

Lisa

This was exactly the issue and ServiceNow is fixing it for me.  It's a Problem and it won't be officially fixed until London release.