Suppressing Deceased Constituents

Hello, we're having some troubles in suppressing deceased constituents and I'm hoping someone will be able to offer some assistance. We've been trying for quite some time now to figure out a way to suppress individuals who are deceased and households where BOTH members are deceased from lists and extractions. The way we've gone about it is to suppress any record where A1 is marked as deceased (as any household with a living member should have that member in the A1 position). Unfortunately, this suppresses any record in which one person is marked as deceased, even if the A1 constituent is not marked as such. We currently are not marking deceased individuals as inactive, but I know that's any option. Does anyone know of any pros or cons that go along with marking deceased constituents as inactive, especially within a household that has a living member? I assume it would not disrupt pulling the living member of that household, correct? And does anyone know why pulling on A1 Status = Deceased pulls in households with a living member? Thanks, Colleen
Parents
  • What I’ve always done is  if A1 is deceased is swap it with the living A2.   Would that work for you?

     

    If you don’t want to inactivate if both are deceased – why not create an Attribute for the HH to code as Deceased HH. 

     

    From: Terry Stevens [mailto:bounce-terrystevens8563@tessituranetwork.com]
    Sent: Monday, February 06, 2017 4:01 PM
    To: McKinley, Leslie <LMcKinley@nycitycenter.org>
    Subject: Re: [Tessitura Development Forum] Suppressing Deceased Constituents

     

    Colleen, I also struggled for months with this. No matter what I tried I was constantly finding my list manager query was not catching everyone. So what I found I had to do was create two different list manager queries. One for finding households with A1 deceased and one for finding (true) Individual accounts with A1 deceased. I then use both of these lists in my suppression for extractions and/or run my list manager lists against these to be sure I am not mailing to deceased. I have attached the queries to because they will not post correctly here.

    From: Colleen Robinson <bounce-colleenrobinson8213@tessituranetwork.com>
    Sent: 2/6/2017 12:18:21 PM

    Hello, we're having some troubles in suppressing deceased constituents and I'm hoping someone will be able to offer some assistance. We've been trying for quite some time now to figure out a way to suppress individuals who are deceased and households where BOTH members are deceased from lists and extractions. The way we've gone about it is to suppress any record where A1 is marked as deceased (as any household with a living member should have that member in the A1 position). Unfortunately, this suppresses any record in which one person is marked as deceased, even if the A1 constituent is not marked as such. We currently are not marking deceased individuals as inactive, but I know that's any option. Does anyone know of any pros or cons that go along with marking deceased constituents as inactive, especially within a household that has a living member? I assume it would not disrupt pulling the living member of that household, correct? And does anyone know why pulling on A1 Status = Deceased pulls in households with a living member? Thanks, Colleen




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • What I’ve always done is  if A1 is deceased is swap it with the living A2.   Would that work for you?

     

    If you don’t want to inactivate if both are deceased – why not create an Attribute for the HH to code as Deceased HH. 

     

    From: Terry Stevens [mailto:bounce-terrystevens8563@tessituranetwork.com]
    Sent: Monday, February 06, 2017 4:01 PM
    To: McKinley, Leslie <LMcKinley@nycitycenter.org>
    Subject: Re: [Tessitura Development Forum] Suppressing Deceased Constituents

     

    Colleen, I also struggled for months with this. No matter what I tried I was constantly finding my list manager query was not catching everyone. So what I found I had to do was create two different list manager queries. One for finding households with A1 deceased and one for finding (true) Individual accounts with A1 deceased. I then use both of these lists in my suppression for extractions and/or run my list manager lists against these to be sure I am not mailing to deceased. I have attached the queries to because they will not post correctly here.

    From: Colleen Robinson <bounce-colleenrobinson8213@tessituranetwork.com>
    Sent: 2/6/2017 12:18:21 PM

    Hello, we're having some troubles in suppressing deceased constituents and I'm hoping someone will be able to offer some assistance. We've been trying for quite some time now to figure out a way to suppress individuals who are deceased and households where BOTH members are deceased from lists and extractions. The way we've gone about it is to suppress any record where A1 is marked as deceased (as any household with a living member should have that member in the A1 position). Unfortunately, this suppresses any record in which one person is marked as deceased, even if the A1 constituent is not marked as such. We currently are not marking deceased individuals as inactive, but I know that's any option. Does anyone know of any pros or cons that go along with marking deceased constituents as inactive, especially within a household that has a living member? I assume it would not disrupt pulling the living member of that household, correct? And does anyone know why pulling on A1 Status = Deceased pulls in households with a living member? Thanks, Colleen




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children