Households with deceased N2

I think it'll create a household and 2 individuals, and the second individual will be inactive, but the household and the first individual will not.

Hi Brian -

To add to Amanda's answer -

You can set what you want a deceased name to do in your TRU_MIGRATION_DEFAULTS -> INACTIVATE_NEW_ACCOUNTS. This will determine whether you want a deceased name to be automatically inactivated.

As for household account creation - it will ALWAYS create a household if there is name 2 info in order for the data to be consistent with v11 and beyond data since name 2 will not exist in v11 and you'd just lose that info. If you don't want a household to be created you could do something like move the deceased name 2 to an alias and remove it from the customer, but I'd argue against doing that.

As for the household name the rule in 'name creation' currently is (and David, pipe up if I've got this wrong) if you have one of the N1/N2 as deceased the household will only be named after the still living person so your box office doesn't ask after the deceased person. If BOTH are deceased then the household name reverts to using both names. Hope that makes sense.

- Heather

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

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