Addresses on Quick Search
When you look up a name in the search bar, the person's name and a listed address populate as you type. The problem is, even if we mark the address as "Do Not Mail" or list it as Previous or Incorrect/Invalid, it will still populate under the searched name.
This is causing issues for staff who want to find an address quickly and do so in this manner, not realizing what the address is listed as (see above examples). There needs to be a solution where if we mark an address as "Do Not Mail" or list it as anything other than a Primary, it shouldn't populate in the search bar.
-
Rachel DeRosa
- Mar 3 2021
- Reviewed: Voting Open
Related ideas
For incorrect addresses or addresses where we are not to mail anything or don't want to mail anything; I delete them in database view. After you do that, the system is okay that there is no Primary Address marked. We used this specifically for visitors under age 14; in our old system the kids would have the address of the family who brought them. When we started using CMS, I deleted all of these kids addresses in database view because that really wasn't their home address. I just had a situation where a family in our church is moving, but in temporary housing right now. In database view I deleted their old home address (they are not living there) but I do not yet have their new address. Address is just blank right now in web view.
While I'm here... I'm working within Addresses right now, and came across another issue. When you make changes to a shared address, shouldn't the changes take effect on all records who share the address? I'm finding this isn't the case and I have to manually make the same changes to all records in a household.
Something else to note that we're running into!
I went to update a returned mailing address on the constituent's record and we already had this wrong address marked as "Do Not Mail" and under an "Incorrect Address/Mail Returned" category. It has to remain the "Primary" because that's the way Blackbaud works. (This is inconvenient and causes much confusion among our staff.) I attempted to delete this obviously wrong address from the record but it isn't possible because apparently there has to be a Primary address, even if it is wrong.
You shouldn't have to mark an address as Primary, necessarily. It should primarily (haha) function using the categories each church customizes to work for them. The "Do Not Mail" flag should prevent any address with that distinction from populating.
It's becoming a hindrance to productivity, and the purpose of these buttons doesn't make sense to me.
This is a great idea and would eliminate mail going to the wrong address.
This is terrible! I hope the issue is resolved promplty.