Review which import rows will create new constituents vs update existing constituents
Better support for troubleshooting and correcting information when constituents in the import file don't match an existing constituent record.
Guest
Jun 25, 2025
To specify further on this request-- Bloomerang clearly has a way to scan records prior to imports in order to indicate # of records that will be newly created and # of records that will be updated. There should then be another level to this where we are able to review the exact records prior to importing so we can determine if those new/updated records are legitimate again, prior to importing. Maybe replicating the similar function that merging duplicates has where we can say "this is not a duplicate" or "do not update this record" or "create a new record anyway" -- something to that effect. See my screenshot as example: If Bloomerang has managed to isolate 3 records that are going to be updated, it should be able to show me those 3 records and allow me to accept or reject these updates prior to the import. I should be able to say "yes update these records" or "no, create new records anyway". At the very least, I should be able to access a link or list to see who those "3 updated" and "22 new" are so I can refer to those in the database and make whatever changes are needed later. The more control the user/client has with our records, the better.
It has been very frustrating to import constituents into Bloomerang. Users should be able to do a final review and edit of which constituents the database will add as a new member especially if the system cannot even detect small errors like an extra space or a one letter typo. It seems like the system should be able to detect these errors, but it is not so. This is one feature that I think bloomerang should AT LEAST offer. Importing bulk transactions had been very disappointing.
To specify further on this request-- Bloomerang clearly has a way to scan records prior to imports in order to indicate # of records that will be newly created and # of records that will be updated. There should then be another level to this where we are able to review the exact records prior to importing so we can determine if those new/updated records are legitimate again, prior to importing. Maybe replicating the similar function that merging duplicates has where we can say "this is not a duplicate" or "do not update this record" or "create a new record anyway" -- something to that effect. See my screenshot as example: If Bloomerang has managed to isolate 3 records that are going to be updated, it should be able to show me those 3 records and allow me to accept or reject these updates prior to the import. I should be able to say "yes update these records" or "no, create new records anyway". At the very least, I should be able to access a link or list to see who those "3 updated" and "22 new" are so I can refer to those in the database and make whatever changes are needed later. The more control the user/client has with our records, the better.
It has been very frustrating to import constituents into Bloomerang. Users should be able to do a final review and edit of which constituents the database will add as a new member especially if the system cannot even detect small errors like an extra space or a one letter typo. It seems like the system should be able to detect these errors, but it is not so. This is one feature that I think bloomerang should AT LEAST offer. Importing bulk transactions had been very disappointing.
YES PLEASE this would help streamline errors in reports!