We seem to have written a bunch of rows full of nulls to civicrm_value_matching_gift. These were deleted on 2020-10-07 but can still be found in the corresponding log table.
Let's filter these out in the sync.
We seem to have written a bunch of rows full of nulls to civicrm_value_matching_gift. These were deleted on 2020-10-07 but can still be found in the corresponding log table.
Let's filter these out in the sync.
OK, it looks like the NULLy rows aren't being created via the matching gifts extension - log lines with them generally have high-numbered log_contact_id values. I guess they're added when people are editing the rows. We're already filtering them out of the CSV export by specifying name_from_matching_gift_db IS NOT NULL, so we probably don't need to do any work here.