We need more control over what gets updated in the duplicate check process when considering pending submissions in the new portal.
When checking for duplicate organizations and contacts in the Consider process for pending submissions, BBGM identifies potential matches but doesn't show what information is being matched and what will get overwritten when the request is Considered. I would like to see a tool similar to the Tax status verification. Show us the fields side by side and let us decide field by field what gets updated. As it currently stands, we run the risk of matching with incorrect organization or contact records or of overwriting information that we don't want to overwrite. I suggested to Blackbaud support that I may need to create new records for all organizations and contacts when considering pending submissions and then go in and merge the duplicate records when I can have more control of them, and they said that is an appropriate workaround that other clients use. This is a very cumbersome solution and will create so much unnecessary work when considering the hundreds and hundreds of applications that we will receive in the coming months. Please, Blackbaud, solve this issue as soon as possible.
-
Abigail Lorber
- Mar 11 2025
Related ideas
Can this be addressed? It is incredibly frustrating to spend so much time double checking our data. It needs to be looked into ASAP.
any idea when this will be looked at please? it ought to be a matter of urgency.
The constant frustration this has provided for me is a lot. Our data is being over written as applications pull through and I have to double check and re-organise everytime. This needs to be looked at ASAP as the integrity of our data depends on it, and we are already considering adding this software to our Risk register, never mind looking for alternative products that don't leave us in this position.
I support this (and collectively on this issue you have way over 100 votes) - we should have basic control of what fields are overwritten, or at least parity with the legacy portal (the option to update or not update fields with new application data). The number of times an applicant misspells their org name, lists a different address, or lists their contact details slightly different (with a middle name or with an abbreviated name) is very high. Your solution of telling customers to 'create new' org and contact records instead of associating at consideration (to avoid the overwrite), then merging duplications at a high volume of 200 applications per day is (1) poor data integrity (2) incredibly risky and (3) needlessly and EXPONENTIALLY time consuming.
I cannot agree more!! I am constantly going back and changing the organization's name back because the applicant did not type it in correctly (or they abbreviated it) It's time consuming and frustrating.
I am completely appalled by this - applicant data should not be overriding the data protected by database managers. It's a complete DEGRADATION of the system. I cannot believe that this is coming from a system that previously allowed you to select which data would override. Not knowing this is how it works, intaking new applications we are required to use in the system by August has rewritten important organization data including tax IDs that are used in the audit and 990 process. This is not a tenable solution for any customer.
Admin permissions and rights are set by organizations. They decide who can view or make changes to its Blackbaud database. What this update essentially does is allow every person using the online portal to overwrite and change existing database information. If the update goes through as is, we cannot risk the integrity of our data and will go back to using paper applications.