AnsweredAssumed Answered

isolating import errors

Question asked by raygeeknyc on Feb 8, 2010
Latest reply on Feb 8, 2010 by philmodjunk


isolating import errors



 Apologies for a seeming FAQ but this is surprisingly difficult to find a solution to, but I cannot believe that there is no good answer.


When I am importing in a script, from an ODBC data source, I am getting an error 729 -  a generic "Import error" with no ODBC error.  When I perform the import manually (in other words, interactively outside of the script) I get the same error with the usual summary of how many fields and records were skipped, etc.


Here's my question - how can I determine which fields and values actually cause the error? I am assuming that there's some data coming in that violates either a data type's constraints (such as an invalid timestamp value) or validation rules for some field but without knowing what records to look at this is very difficult to debug.


Any pointers or advice are welcome