We are getting an exception caused by one of the fields in an object being null. When we call SaveChanges() the before Insert trigger detects this condition and throws the error.
I need some assistance in determining which of the 3 million or so rows in the entity has the null value. I have a couple of thoughts on how to approach this issue.
- Try to determine when the faulty row is added to the collection. This has been my approach, but so far no rows look bad when they are added to the collection.
- Try to determine which rows were are going to be saved when SavedChanges() is called. Only a few of the rows are updated or new. Find the faulty new or updated rows and remove them from the collection.
- Have dotConnect ignore the exception. It does stop the insert which is fine. I don't know if this is possible.