Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

The maximum field length in the imported set table has not work

lipan
Tera Contributor

Hi Everyone

 

issue:import set table‘s field max length is 4000,Importing strings exceeding 4000 characters without truncation

 

I created a table using load data, set the maximum length of each field, and then imported two data with a length equal to the maximum length of each field and a value that is 1 longer than the maximum length of the field. All other fields truncated the string to the maximum length normally, but the 'note' field did not, Characters that exceed the maximum length are still imported, Why 'note' field max length not work?

 

lipan_1-1707035272561.png

 

lipan_0-1707035252000.png

 

lipan_2-1707035314211.png

 

lipan_3-1707035329367.png

 

1 ACCEPTED SOLUTION

Anand Kumar P
Tera Patron

Hi @lipan ,

Refer below link

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0623379

 

Mark it as helpful and solution proposed if it serves your purpose.
Thanks,
Anand

View solution in original post

4 REPLIES 4

Anand Kumar P
Tera Patron

Hi @lipan ,

Refer below link

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0623379

 

Mark it as helpful and solution proposed if it serves your purpose.
Thanks,
Anand

Alternatively, if we set max length of a column of string type to 4000, ServiceNow would allow to save a string of length more than 4k, right, and up to 16MB characters, correct?

Markus Kraus
Kilo Sage

Had the same problem, only solution was to manually change the field length a few times... (I'm literally talking about changing it several times).

There is also a property involved with handling the import column size (com.glide.loader.verify_target_field_size):
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1588592

 

I've had two cases for this topic already but none of the solutions worked, and i restored into fiddling around with the column size until it worked because I couldn't wait for a in-depth analysis by SN's dev team...