Single Name Output at Household and Individual Level?

HI Katie,

Am I right -

• the household is Jane and Joanne Smith  (has a membership
• Ticket was bought by Jane Smith

You want to set up a word fly email output set with Salutation_inside list element as the  WordFly data field?  (probably looks something like {{##First Name## || }} in wordfly)

What Salutation_inside do you have for Households vs Individuals and is that the problem?

Cheers,

H

Hi Heath,

The Wordfly part I understand, but in Tessitura, if I use the output:

• 'First Name' this works on the individuals but is blank for the households.
• 'Salutation Inside' and 'Salutation Outside' does provide results for all, but for the Household this output lists both parties and not just Jane in your example. Also the results are formal, and I'm looking for a First Name only.

I must be doing something wrong!

Thanks,

Katie

Not at all. We are fairly casual with our inside.  The household will be Jane and Joanne and our outside for the household will be Jane and Joanne Smith.  But that's perhaps a different topic

But can I ask you about your list as I think it's due to the selection criteria and/or advanced relationship options.  You can indeed just talk to the ticket purchaser at the individual level.  Are households being selected because there is a Membership Criteria as a list element?

Hi Heath,

The Criteria elements I’m using are:

• Membership Org Name 
• Membership NRR Status
• Membership Campaign Name 
• Ticket Production Season 
• Tickets-Tkt Hist Trans Date 

Thanks again for your time,

Katie.

Hi Katie,

Heath is correct that it's the selection criteria that are the issue. If I'm understanding correctly:

• You are using memberships as products
• For households, memberships live at the household level
• But in your final result you want the individual in the household that initiated the membership purchase

Based on all of that, I think you want to reference the Initiator on the membership purchase orders, which you can do through the Ticket History Const Role criterion. You can learn about working with roles in criteria sets in this help topic:

https://www.tessituranetwork.com/Help_System/Content/List%20Creation%20and%20Management/Roles.htm

You also seem to want to reference details of the memberships that live at the household level in the same criteria set. So for your final result you want individuals but the criteria you are referencing is split between household records (for memberships) and individuals (for the initiator ticket history). This is a perfect example of when you want to use the Include Households checkbox on criteria, specifically the membership criteria. When you check that box, data from the primary affiliated household of an individual is treated as if it is on the individual record. Here's a link to the help topic that explains these household considerations in detail:

https://www.tessituranetwork.com/Help_System/Content/Criteria%20Sets/Household%20Criteria%20Considerations.htm

Putting it all together, here's what I think your criteria should look like:

• Membership Org Name (Include Household checked)
• Membership NRR Status (Include Household checked)
• Membership Campaign Name (Include Household checked)
• Ticket History Prod Season
• Ticket History Order Date
• Ticket History Role (value set to Initiator, Owner/Initiator, and Owner/Initiator/Recipient)

These criteria should catch initiating individuals with a primary household because checking the Include Household box on the membership criteria will treat the membership on the household as if it was on the individual record, and the Ticket History Role criteria will find the entries for the membership as product purchase where the individual is marked as the Initiator.

Individual members who do not have a household should also get picked up because they have memberships on their records (the Include Household box doesn't do anything if a constituent doesn't have a household) and the Ticket History Role values of Owner/Initiator and Owner/Initiator/Recipient will find their membership as product purchases (because in orders without an explicit Initiator and/or Recipient specified the owner is used for those values, leading to the OI and OIR entries in the ticket history; single role values are only attributed when a constituent when all roles in an order have been specifically set and the constituent has only been set for one of them).

All of this Role functionality working is dependent on using the standard ticket history and corresponding standard criteria (all of which start with the words Ticket History in their description). When you listed the criteria you are using, they didn't look like the standard criteria so I wanted to be sure to highlight this. Mixing the standard Ticket History Role criteria with custom ticket history or order criteria is not going to give you the desired result. The reason why brings me to my last tip... be sure to use the IN operator for any of your criteria that use dropdown values (which should be all of them except the order date) so they are looking for a single entry in the same table that meets all three criteria. If you need a refresher on the differences between In and Has, we have some videos resources available here:

https://www.tessituranetwork.com/Support/Training/Intro-Courses/Lists-and-Output

I hope that all helps.

-Kevin

Hi Katie,

Heath is correct that it's the selection criteria that are the issue. If I'm understanding correctly:

• You are using memberships as products
• For households, memberships live at the household level
• But in your final result you want the individual in the household that initiated the membership purchase

Based on all of that, I think you want to reference the Initiator on the membership purchase orders, which you can do through the Ticket History Const Role criterion. You can learn about working with roles in criteria sets in this help topic:

https://www.tessituranetwork.com/Help_System/Content/List%20Creation%20and%20Management/Roles.htm

You also seem to want to reference details of the memberships that live at the household level in the same criteria set. So for your final result you want individuals but the criteria you are referencing is split between household records (for memberships) and individuals (for the initiator ticket history). This is a perfect example of when you want to use the Include Households checkbox on criteria, specifically the membership criteria. When you check that box, data from the primary affiliated household of an individual is treated as if it is on the individual record. Here's a link to the help topic that explains these household considerations in detail:

https://www.tessituranetwork.com/Help_System/Content/Criteria%20Sets/Household%20Criteria%20Considerations.htm

Putting it all together, here's what I think your criteria should look like:

• Membership Org Name (Include Household checked)
• Membership NRR Status (Include Household checked)
• Membership Campaign Name (Include Household checked)
• Ticket History Prod Season
• Ticket History Order Date
• Ticket History Role (value set to Initiator, Owner/Initiator, and Owner/Initiator/Recipient)

These criteria should catch initiating individuals with a primary household because checking the Include Household box on the membership criteria will treat the membership on the household as if it was on the individual record, and the Ticket History Role criteria will find the entries for the membership as product purchase where the individual is marked as the Initiator.

Individual members who do not have a household should also get picked up because they have memberships on their records (the Include Household box doesn't do anything if a constituent doesn't have a household) and the Ticket History Role values of Owner/Initiator and Owner/Initiator/Recipient will find their membership as product purchases (because in orders without an explicit Initiator and/or Recipient specified the owner is used for those values, leading to the OI and OIR entries in the ticket history; single role values are only attributed when a constituent when all roles in an order have been specifically set and the constituent has only been set for one of them).

All of this Role functionality working is dependent on using the standard ticket history and corresponding standard criteria (all of which start with the words Ticket History in their description). When you listed the criteria you are using, they didn't look like the standard criteria so I wanted to be sure to highlight this. Mixing the standard Ticket History Role criteria with custom ticket history or order criteria is not going to give you the desired result. The reason why brings me to my last tip... be sure to use the IN operator for any of your criteria that use dropdown values (which should be all of them except the order date) so they are looking for a single entry in the same table that meets all three criteria. If you need a refresher on the differences between In and Has, we have some videos resources available here:

https://www.tessituranetwork.com/Support/Training/Intro-Courses/Lists-and-Output

I hope that all helps.

-Kevin

Just reposting what I said in email because it talks about the output a little. 

Having a salutation type that works for both HH and Individ is handy.

TR_SALUTATION_FORMAT system table which has the wonderful rules for everything Salutations.

https://www.tessituranetwork.com/Help_System/Content/System_Tables/TR_SALUTATION_FORMAT.htm

The Rebuild Salutation utility is the number that will assign that salutation to your constituents

https://www.tessituranetwork.com/Help_System/Content/Reports/Rebuild%20Salutations.htm