Easy import template text trunacted during import

[TomDickson]

I'm using the Easy Import Template to create new records in the alm_hardware table and encountering an issue with reference fields such as Model and Location. In my Excel template, the values I provide exactly match existing records in the respective reference tables. However, during import, the values appear to be truncated, and I receive an error stating that the entry does not match any existing record.

I’m unsure why this is happening, as the character limit on the Easy Import seems to be shorter than the actual field length defined on the target table, which prevents valid matches. Is there a way I can change this? 

-Apologies if this is posted in the wrong place.

[J Siva]

Hi @TomDickson 
That's OOB behavior. By default the field length is 40.
If you want to make it dynamic, create/update the system property com.glide.loader.verify_target_field_size with value as true. For more details, please visit below support article.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1588592

Regards,
Siva

[Ankur Bawiskar]

@TomDickson 

you should set the system property as shared by @J Siva and it should work for you.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[TomDickson]

@J Siva Thanks for the suggestion. com.glide.loader.verify_target_field_size does not exist in my instance, should I create this as a new record on sys_properties.list?
I was able to find an alternative, possibly permanent solution, which is changing the character limitation on the table Imp Tmpl Alm Hardware on an existing import row as per screenshot.

[J Siva · Accepted solution]

@TomDickson 

1. Yes, you need to create that system property if it doesn't already exist.

2. Increasing the field length on the staging table will work as expected. However, this is a workaround rather than a permanent solution. If you're confident that the character length will not exceed 150 in the future, you can proceed with the second approach—modifying the field length directly on the staging table.

Regards,

Siva