Users processing custom fields using the Data Translation Module may experience the following error:
Error on record 2: Column 'Custom Field Name Here' does not belong to table Table.
This error can be reviewed in the log file in the
Logs folder located at: C:\Program Files (x86)\jProg\DTM\Logs by default.
The error occurs because the custom field was not a column in the PDI file. If the option Create Single File was checked, previously processed imports didn’t include the custom field. If Create Single File was not checked, the PDI Template.mdb may not have the custom field columns in it, because the PDI Template.mdb file in the DTM folder is not a custom PDI template containing the custom field.
To resolve the error: Uncheck Create Single Output file or move the PDI files from the output folder before processing the new custom fields.
To resolve this error if Create Single Output File is unchecked: Make sure the custom PDI Template is saved in the DTM folder and the custom PDI template file in the DTM folder is called PDI Template.mdb.
The custom template created in the Provider Data Import menu needs to be named to PDI Template.mdb and replace the PDI Template.mdb file currently in the DTM folder, located at C:\Program Files(x86)\Jprog\DTM by default. Once the custom PDI template is in the DTM folder, the DTM will use that template for processing import files. The custom fields can then be mapped in the CSV Specifications.
Click
here to download these instructions.
Back to
Recent Build Fixes