Closed leehockhin closed 7 years ago
When I re-run the Data Import with ReportingNumber = 5, the error came up earlier, and fewer records had valid Addresses (which I believe is from the Family Import section of the run)
When I rerun with ReportingNumber=500, the run was successful, with no error reported!
So it cannot be an input data problem
*\ Notice the number of "progress dots" is less for this run with ReportingNumber=500
@leehockhin What version of Rock are you running against? It sounds like the ReportingNumber reached the middle of a family and then saved.
Also the number of dots is determined by 10% of your ReportingNumber, so that's why there's less.
@dcs619 I am now at "Rock McKinley 4.4" And Excavator is using "Rock.dll v1.4.3.0"
@leehockhin Have you completed your migration? A recent pull request changed the way the Individual.csv file saves the families as it's parsing (to make sure there are not family members that cross the ReportingNumber in their row positions). I wonder if you would have the same problem using the newest pull.
Hit this error (see attached log) during Family Import stage. It could be due to my data, but it would be a good opportunity to debug. ExcavatorExceptions.txt
Data imported is usable