Data Import Manager jobs - where do errors go?

SOLVED

I have a set of data import manager jobs configured to run on a nightly basis. Basically the SSIS job schedule has been adjusted via SQL management studio to run every night instead of the one time schedule set up by DIM. All is working well in testing, but it will soon be opened up to end users who will populate a shared Excel file. I am concerned about mistakes being made in the file and how I can report import errors to the group responsible for maintaining the Excel workbook. So I was wondering where MAS500 stores file validation errors when they occur. These would be the errors reported in the crystal report that runs after a job is run and fails in MAS500.


I suspect this might not happen the same way if the job is launched from SQL Agent instead of MAS500, as a search of various tables seems to result in no results (tdmMigrationLogWrk table does not include the imports). The import is for the Sales Order entity (StgSalesOrder and StgSOLine)


Is anyone able to shed some light onto this or has a way to report import errors? Thanks in advance!

  • 0

    Well without getting into the actual code,  I would recommend running a SQL trace when processing a known bad file from the client to see if it is storing the results in a SQL temp table for Crystal Reports to use (Most reports in 500 work this way).  From this you might be able to figure out how you could incorporate the file validation reporting into the process you are planning on..

  • 0
    verified answer

    I figured it out. If I create another step in the SQL job that runs a query to dump everything in tdmMigrationLogWrk to a custom table, I can then query this custom table with an Explore view and provide users a way to see what went wrong. This works pretty consistently so far. I guess tdmMigrationLogWrk gets wiped out, but not if you query it soon enough after the job is run.

    Thanks Lou for your input. I did already run a trace, but didn't mention it.