• Replies 9 replies
  • Subscribers 332 subscribers
  • Views 71 views
  • Users 0 members are here
Related

Standard Suppression

Kjersten Schladetzky
$organization

Could anyone who has a standard suppression set up for Extractions share what is on it?  We are planning to set one up and want to make sure we don't miss something important.  Obviously some of it is organization specific depending on our usage of attributes, mail purposes, etc... but just a general idea would be great.  Thanks!

Parents
  • $organization
    To give a little more background, when two records are merged the delete record is not really deleted but rather the status is changed to Merged. This is the record that exists in the T_CUSTOMER table, which pretty much just holds the N1, N2, and a few audit fields like last update. All the other data in a constituent record is stored in other tables and the ID on that data is changed from the delete record to the keep record. Because of that, it's pretty unlikely a merged ID would end up in an extraction (it wouldn't have any data that would meet your criteria unless you were looking at something like name status) but it never hurts to be safe by suppressing merged records.

    Kevin Sheehan
    Documentation & Learning Resources Specialist
    Tessitura Network
    1 888 643 5778 ext 329 Office
    ksheehan@tessituranetwork.com
Reply
  • $organization
    To give a little more background, when two records are merged the delete record is not really deleted but rather the status is changed to Merged. This is the record that exists in the T_CUSTOMER table, which pretty much just holds the N1, N2, and a few audit fields like last update. All the other data in a constituent record is stored in other tables and the ID on that data is changed from the delete record to the keep record. Because of that, it's pretty unlikely a merged ID would end up in an extraction (it wouldn't have any data that would meet your criteria unless you were looking at something like name status) but it never hurts to be safe by suppressing merged records.

    Kevin Sheehan
    Documentation & Learning Resources Specialist
    Tessitura Network
    1 888 643 5778 ext 329 Office
    ksheehan@tessituranetwork.com
Children
  • $organization in reply to Kevin Sheehan

    Hi

    Our standard postal suppressions are:

    Staff members

    Inactive accounts

    Merged accounts

    Customers with 'deceased' flag (in case these have not been inactivated for any reason)

    People with 'Do Not Mail' marked in data protection

    People with our organisations postcode - sometimes this is used for press accounts where we only have an email address

     

    Hope that's helpful

    Siobhan

     

     

  • $organization in reply to Kevin Sheehan

    Thanks Kevin.  That helps alot.  Sounds like something we should throw in just to be safe.

    Unknown said:
    To give a little more background, when two records are merged the delete record is not really deleted but rather the status is changed to Merged. This is the record that exists in the T_CUSTOMER table, which pretty much just holds the N1, N2, and a few audit fields like last update. All the other data in a constituent record is stored in other tables and the ID on that data is changed from the delete record to the keep record. Because of that, it's pretty unlikely a merged ID would end up in an extraction (it wouldn't have any data that would meet your criteria unless you were looking at something like name status) but it never hurts to be safe by suppressing merged records.

    Kevin Sheehan
    Documentation & Learning Resources Specialist
    Tessitura Network
    1 888 643 5778 ext 329 Office
    ksheehan@tessituranetwork.com

  • $organization in reply to Kjersten Schladetzky

    Sorry, I checked the criteria for our "Inactive Account" suppression and it also checks for merged accounts.