An import that does not complete, is missing data or data is truncated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 09:39 AM
I've worked in a table (u_dameon table) that is importing data from an Excel file and I'm using a transform map to add it to the sys_dictionary table. The table is working just fine but there is just one column (u_license_allowed_usage_scope) that is still not showing all the data that we required, it seems like it is locked at 40 chars, and the column max length was already set up for 300 values.
However, I was digging in for a solution in this community already and I found some really interesting files but none of them worked for this issue, in the beginning this column max length was set up for 40 chars value so I tried to change the value from source table to 256 saved and did a test running but for some reason it was doing the same then I changed to 300 but it didn't work either, here is a screenshot to have a better picture of what is happening.
I'm new in service now so I don't have too much experience moving through it, but I will really appreciate if anybody can help me to find an answer for this
Thanks in advance
Best regards

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2015 02:43 AM
Hi Edmar,
The fields length is set to it's maximum first time the file is loaded. However, the field value remains the same when you load another file, hence the truncation takes place.
Since, you've updated the source table field length, did you re-upload the file? As the data already loaded has incorrect data.
Thanks,
Mandar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2015 08:23 AM
Hi Mandar,
Thanks for your time, and about your question yes after the first time I changed the max length for the field from 40 to 256 I saved it and re-upload the file again and nothing change then I changed the max length to 300 but it didn't work either, as a matter a fact I double checked the file I even used a newer update file with the same columns but different data on it and re-upload it but it didn't change anything, it was doing the same
Thanks and Best Regards,
Edmar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2015 03:38 AM
Hi Edmar,
There is a potential gotcha when increasing the size of a string field to over 256 chars.
Fields being truncated at 40 chars
Try to change the max length to 256 first and then try to put it to a bigger value after.
It seems that if you don't put it to 256 first, the change will not occur at the database end (which you cannot change yourself).
As changing from 40 chars to say 400 requires a change to the field data type.
Introduction to Fields - ServiceNow Wiki
It does seem that you are aware of this and have changed it to 256 - but I thought it worth mentioning...
Best Regards
Tony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2021 06:26 AM
6 years later and this is still an issue... Glad I found this post. Thanks Tony!