An import job imports data from an external CSV file or directory of files into the data store. The external files must be in UTF-8 format or the import will fail. For Excel files, re-open the file in a text editor and then save as UTF-8. Excel does not support saving with UTF-8 encoding.
The following fields are included:
Field |
Description |
Import Map |
The map that enables import of data from an external file to the data store. Import maps are defined in CRM Studio and are available for selection in this drop-down list. |
Import File |
The full path and name of the CSV file containing the data to be imported. You must have read privileges for this file. This entry can be a single file, a directory of files and subdirectories, or a file name with wildcard characters (wildcard character = *). |
Reject/Error File Directory |
(Used only if Write Failed Records to Reject File or Write Error Details to Error File are checked.) The directory that holds error files and data that is rejected when a job is run. Rejected data is contained in a .rej file and error details are contained in an .err file. This directory requires write privileges. |
Import File Start Index |
The number of the record you want a job to start from. This is useful for restarting jobs after a failure: if, for example, record 50 failed, you could start the job at 51. |
Import File Stop Index |
The number of the record you want the import to stop after. If the value is greater than 0, the import stops after processing the stop index record count. Values 0 or less are ignored. |
Commit Threshold |
The number of records to update in a single transaction. This setting affects performance. |
Error Threshold |
The maximum number of errors this job can tolerate before aborting. |
Input File Has Headers |
Check this box if the first row of your CSV is a header. |
Rename File After Import |
Check this box to rename the source file or files after importing their data. Use this option for convenience when importing all files from a directory on a periodic basis to avoid the need to manually remove files that have already been imported from the directory. This option requires write access on the import source file. There is no error if the files cannot be renamed. |
Insert Only, No Updates |
If checked, updates are treated as errors. Check this when data is fresh and updates are not applicable. |
Trial Run |
A means of troubleshooting import jobs. During a trial run, data is not committed to the database. If checked, a trial run is enabled to catch errors on new import maps. Metadata error messages are captured in the Epny.log4j in the application installation directory and must be fixed in Studio. You must reload metadata for corrections to take effect. Data error messages are shown in the .err file. Fix the data and re-import. |
Write Failed Records to Reject File |
When checked, failed records are written to reject files (.rej) in the Reject/Error File Directory you specify. |
Write Error details to Error File |
When checked, details about error encountered are written to error files (.err) in the Reject/Error File Directory you specify. |
Write Remaining Records on Import Failure |
When checked, if the job fails, records not imported are written to reject files. This may be time-consuming if the failed job is large. |
Related Topics