[Music] in this video we'll cover some of the system properties related to import sets first there are many system properties involved with import sets this video looks at some of the more common ones to be familiar with a link to the docs page with the import set properties is provided below in an earlier video we mentioned that we may want to inspect the import set field lengths during a test import to make any necessary adjustments to string field lengths the system can do this automatically by setting the property com.glide.loader.gov verify target field size to true the system default is false which means any fields longer than the specified length are truncated by setting this to true if the imported data needs a string field longer than is currently available the corresponding import set row field length is adjusted let's say we have imported 20 rows of users and nobody's email address was longer than 40 characters in that test set the length of the field would be the default string length of 40 characters however if later the system encounters an email longer than 40 characters it would truncate the email address if this property were not set or set to false by setting it to true the email field on the import set will be adjusted to be just long enough for the longest address it encounters but be aware this could have a performance impact since the database needs to do an alter operation every time it changes a field length if we have a lot of import set rows in our system it could take a while to do each alteration let's look at another property if we're running a scheduled import that requires successful completion of the parent we may want to consider setting the property glide dot scheduled import dot stop on error to true this way if the parent has an error the import will stop preventing the child from possibly creating additional errors by default the test import retrieves 20 records in some cases we may want more setting the property com.glide.loader.max scan rows to a higher value like 50 or 100 could provide a better data sample now interestingly enough this property applies to jdbc xls csv and xml formats but not json and xlsx as we discussed in the episode with concurrent import sets the maximum number of import sets used is 10 but we may want to change that by setting the property glide.scheduledimport.max.concurrent.importsets to another integer value if we're importing csv we may want to set the property com.glide.csv.loader.ignore non-parsable lines to true to allow the import to continue by ignoring csv lines that are not parsable ordinarily the system would stop the import at the first sign of a problem here's one we might want to set if we encounter problems importing an xlsx file set the glide.xlsx.import.debug to true to enable debugging and finally a couple more properties to potentially help with general import set debugging setting com.glide.importset.import log level to info warning or error controls how much import set logging happens the system defaults to info and glide.import.debug is a true false property to enable or disable debug logging for all import processes as noted earlier these are just some of the properties you might find useful check out the link in this video for more information you