Sometimes, the error message that is returned is not a user-friendly BVDL error message, but actually a SQL message, e.g.:

‘Procedure or function ‘USP_DATAFORMTEMPLATE_EDIT_RELATIONSHIP_ORGTOORG_4’ expects parameter ‘@ISPARENTRELATIONSHIP’, which was not supplied.’

When this happens, although these error messages show up in the Errors window when you view the individual records, selecting them in the Error Message drop down returns no records. If I could exclude specific Error Messages then I could show the records that did not have those and return the records that do have the error message that I am trying to explore. Where records have multiple error messages, just excluding one of them might result in me also excluding the 'hidden' SQL error message, so with tick boxes like this I could determine where the SQL error corresponds to another error message as well to select the right ones.

Currently, when this happens in large imports, it can be frustrating to find the records with these SQL errors to work out what's causing the problem.