I've got a fairly simple list that's not behaving as I expected it to in regards to households and individuals, and I'm hoping maybe I'm just missing something. I'm trying to get customers who have one production but not another. The criteria are:
Production IN 13382
Production DOES NOT HAVE 13191
I've got "Search Household" checked on both criteria. The problem I'm getting is when tickets to 13382 are on the household and tickets to 13191 are on the individual, the household account is being selected in the list. I've left all the defaults unchanged in the tabs at the bottom.
So how can I make sure that both the criteria are looking at the household and individual accounts? Should I use an extraction instead, or maybe build two lists? Would love to hear any suggestions anyone has.
Thanks!
Brian
Hi Brian,
When criteria sets evaluate constituents, data from the household can be considered for the individual (by checking the Search Household box) but data from the individual is not considered for the household. That means that if the individual has the Does Not Have performance, it will not disqualify their primary household.
I can think of two ways to accomplish your desired result.
The first, and probably safest, option is to use a suppression segment in an extraction. For the suppression criteria you would use: Production Has 13191 and check the Search Household box. The result would be that the segment will find all households with the production, all individuals with the production, and all individuals with primary affiliations to households that have the production and then suppress them. You could also get the affiliated individuals using the Advanced Relationship Options instead of checking the Search Household box.
The second option is to add a Constituent Type criterion to your criteria set and select the individual constituent types. The result would be that only individuals who meet the criteria (through themselves or their primary household) would be selected for the list. You could then use the Advanced Relationship Options to add in the household records for individuals who meet the criteria. The one potential drawback for this option is that if you have some households that don’t have any affiliated individuals but otherwise meet the criteria, they won’t be selected for the list. This is probably pretty unlikely, but still worth noting.
If you are coming the conference, you may want to check out my session, List Changes in v11, which I’ll be presenting twice. In the session we’ll be going over Search Household and Advanced Relationship Options with several examples and ample opportunity to ask questions like this.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com