Scenario: v10 individual account has a name 1 and name 2. Name 2 is deceased. Does this still create a household in v11? Will the household be inactive? If we set INACTIVATE_NEW_ACCOUNTS in TRU_MIGRATION_DEFAULTS will both the new individual accounts be inactivated?
From: "Heather Kraft" <bounce-heatherlaidlawkraft3507@tessituranetwork.com>To: bvarro@smm.orgSent: Tuesday, December 20, 2011 1:27:05 PMSubject: Re: [Tessitura Next Generation Forum] Households with deceased N2Hi Beth - I can confirm (poking through my own v11 beta data) that if the Name2 is deceased you will still end up with three accounts - Household, A1 & A2 and only the A2 account will be inactive. So yes, it is smart enough! I don't have any other status info other than deceased, so I'm sorry I'll have to punt that part of the question to someone else! HTH, HeatherFrom: Beth Varro <bounce-elizabethvarro6946@tessituranetwork.com>Sent: 12/19/2011 2:33:10 PMDitto Brian's question. I'm hoping it will do what Amanda described; can we get confirmation on that? What's confusing me is that the migration documents say that if the status on Name 1 OR Name 2 is Deceased, it will inactivate "the records" if the INACTIVATE_NEW_ACCOUNTS is set to Yes. That kind of sounds like it will inactive ALL the accounts it creates (household and both the N1 and N2 individual accounts) if either N1 or N2 is marked as deceased in V 10. That seems excessive; is it smart enough to inactivate only the Indiv account that is marked deceased, and to only inactivate the Household if both indivs are deceased? Also, in a related vein: We have a couple other statuses in that field, other than deceased. When we migrate, will it just copy those statuses over so we can then move that data to whatever field is more appropriate, or do we need to clean out everything except "deceased" from that field? In other words, is the migration checking what value that field actually has, or is it just assuming that any value = deceased? Thanks! BethYou were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
Hi Beth -
I can confirm (poking through my own v11 beta data) that if the Name2 is deceased you will still end up with three accounts - Household, A1 & A2 and only the A2 account will be inactive. So yes, it is smart enough!
I don't have any other status info other than deceased, so I'm sorry I'll have to punt that part of the question to someone else!
HTH,
Heather
From: Beth Varro <bounce-elizabethvarro6946@tessituranetwork.com>Sent: 12/19/2011 2:33:10 PM
Ditto Brian's question. I'm hoping it will do what Amanda described; can we get confirmation on that? What's confusing me is that the migration documents say that if the status on Name 1 OR Name 2 is Deceased, it will inactivate "the records" if the INACTIVATE_NEW_ACCOUNTS is set to Yes. That kind of sounds like it will inactive ALL the accounts it creates (household and both the N1 and N2 individual accounts) if either N1 or N2 is marked as deceased in V 10. That seems excessive; is it smart enough to inactivate only the Indiv account that is marked deceased, and to only inactivate the Household if both indivs are deceased?
Also, in a related vein: We have a couple other statuses in that field, other than deceased. When we migrate, will it just copy those statuses over so we can then move that data to whatever field is more appropriate, or do we need to clean out everything except "deceased" from that field? In other words, is the migration checking what value that field actually has, or is it just assuming that any value = deceased?
Thanks!
Beth