Hi all,
So this may be obvious but I can't seem to find any info on how constituencies are carried across with the new households model after reading through all the doc's.
If a current v.10 account with 2 names has 1 or more constituencies, do the constituencies carry across to both A1 and A2? Or do they just stay on the household account and the new accounts are blank?
Also, the ticket history in general, would that go across all 3 accounts (household + A1 and A2)? Or just on the Household? Or...is this in the mapping and we can decide what we do?
Thank you!
Tash
I think it's mappable but the default would be based on whatever the N1N2_ind is; if N1 it goes to the new N1's account, if N2, to the name2's account and if it's "both" it stays on the household account.
Amanda is right for constituencies. They follow the N1/N2 indicator. Visibility applies to constituencies, though, so even if a constituency goes to one of the individuals you’ll still see it on the household (and vice versa), including in the constituent header. Constituencies in the constituent header that come from primary affiliates are listed in parenthesis.
Ticket history stays with the original record, which becomes the household. Visibility applies to ticket history, though, so you’ll still see the ticket history on the individual accounts. And in lists and extractions there are options for considering household data when evaluating an individual as well as adding affiliates of selected households to the results (just like you can do now with associations).
For full details on what will happen in the migration, see the Migration Toolkit Documentation. And if you want to see the details of the list and extraction options for dealing with households, see the What’s New in v11 document.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Hi Kevin and Amanda,
Thank you both, all makes perfect sense.
Natasha