If multiple rows come in for the same person and are routed to the " New Records" bucket because a match is not found in destination, clicking "Send All/Page" sometimes creates duplicate contacts/constituents. We need matching capabilities in the New Records bucket to prevent duplication if all bio data matches exactly.

Currently, the work around is to ensure a unique ID is populated, so that any new records that are duplicates will be sent to exceptions. Those exceptions then need to be reprocessed in order to match. However, this only works when a unique ID field is available from the source. For connectors where the ID is being mapped to an Alias, this doesn't work, because Alias isn't a unique field. It also doesn't work for data files where no unique ID is present. In this case, the current process is to review the New bucket, identify duplicate rows (ex. multiple gifts in file/connector), add one as new, and then reprocess all.