- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 01:01 PM
I'm very confused with this as it worked correctly in DEV.
I imported 100+ records via CSV through an Import Set. All the records processed correctly in DEV and all data was there, however once I repeated in PROD the short description and description fields were truncated.
I've seen a lot of posts mentioning adjusting the field length but I'm unsure if this would be the issue since I don't believe we've ever modified this between instances.
Any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2024 10:09 AM
I was able to fix this using the following solution:
Explanation: The system property on the sys_properties table "com.glide.loader.verify_target_field_size" allows for dynamic resizing of import set fields. When false, this samples records to determine the import set field length. This can often not correlate or align to an actual table field (description being a prime example which is around 4,000).
Solution: set the "com.glide.loader.verify_target_field_size" system property to true. If not found, create it and set it to true. This ensures that any import set field to increase the column size by 100 to match the length of the data. Creating this system property and setting it to true resulted in the full data being imported.
Source material: https://www.servicenow.com/docs/bundle/xanadu-integrate-applications/page/administer/import-sets/ref...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2024 10:09 AM
I was able to fix this using the following solution:
Explanation: The system property on the sys_properties table "com.glide.loader.verify_target_field_size" allows for dynamic resizing of import set fields. When false, this samples records to determine the import set field length. This can often not correlate or align to an actual table field (description being a prime example which is around 4,000).
Solution: set the "com.glide.loader.verify_target_field_size" system property to true. If not found, create it and set it to true. This ensures that any import set field to increase the column size by 100 to match the length of the data. Creating this system property and setting it to true resulted in the full data being imported.
Source material: https://www.servicenow.com/docs/bundle/xanadu-integrate-applications/page/administer/import-sets/ref...