Allow the AddressFinder process to update the Do Not Mail flag when a new valid address is updated onto the constituent record.
When an address is updated via address finder, the details of the orignal address, such as the do not mail flag, are copied over or retained on the new address. A record may have an address that is marked "do not mail" and when a new, mailable address comes back in that do not mail flag is retained on the new, valid address. This is currently done because the do not mail flag may not necessarily just indicate that the address is undeliverable. Instead, for example, it may also mean that the address should not be mailed to by preference of the donor, which in that case, would apply to the new address.
The flag remaining on the records is impacting solicitation pulls, as they do not pull mailings for records with the Do Not Mail Flag.
-
Deleted User
- Aug 4 2015
- Reviewed: Voting Open
| Organization Name (Please enter full organization name) | University of Michigan |
| Reported Version | 3.0 |
Related ideas
Beyond this, it would also be beneficial to put a start date on the new addresses and not remove the type when the old address is kept, if you choose not to apply a type to the old address. The start date seems like it should be available since the batch table for Address Finder includes the NCOA move date.
Adding a setting of somesort to turn off the transfer of the Do Not Mail flag would be ideal...