CSV imports can be a challenging and tedious task in any system. In NetSuite however, once you have an understanding on how to solve some of the more common problems, one can complete import tasks relatively quickly. You will find tons of documentation on what to do when a particular error shows on a failed import results file. But, what about imports that do not get a runtime error? How do we locate and troubleshoot those? Here are some suggestions to avoid those common hidden import errors.
Always assign a unique id for time imports
Unlike the import of most new records in NetSuite, time records do not require a unique id. This does not become an issue until there is bad data inadvertently imported and the records need to be corrected. Attempting to find those records could be like trying to find a needle in a haystack. By assigning the optional unique identifier, you would have an easier time finding and correcting the records with bad data.
Use a system notes search to find and isolate records with bad data
A search on system notes of a particular record is another way to find records with bad data. If you’ve imported bad data for a subset of records and the only known commonality is the user who imported and the date of import, then use a system notes search with the user and date as the criteria to find those records. If there are any other distinguishing criteria add those too. Be sure to only specify the “Create” system notes type because it shows once in the system notes. Also capture the internal id value.
Save CSVs with UTF-8 encoding
Sometimes characters get changed when exporting a csv source file from a legacy system. To avoid character errors when you try and add the file for import, save the file with a UTF-8 encoding. This will help you to avoid a time-consuming file search and correct.