• Replies 12 replies
  • Subscribers 361 subscribers
  • Views 76 views
  • Users 0 members are here
Related

Adding a wife(N2) to a record in v11?

Heather Hoyt
$organization

Okay, so is it correct that the only way to add a second person/individual (typically the wife) is to create a new individual record for the wife, then create a household record and then affiliate the two records to the household?? This seems rediculously long.... And the address information doesn't carry over to the second individual record? This can't be right can it?? I know this seems basic, so I appolgize, if there is a good tutorial on the network, please direct me to it... just seems so silly if these are the steps.

Heather

Parents
  • $organization
    To piggyback on Boann's suggestion... it's the method we've chosen, even though there a couple of options that "appear" to do the same thing...

    (and I've totally just read Heather Kraft's response - who was thinking along the same lines - just faster at pushing the button!)

    1) Create new household and "fill" it (our chosen method):

    Creating a new household and putting the primary affiliates into it (whether they both existed previously or not) allows you to keep some individual settings on the individual's account, that would otherwise be stuck on the household account. We also transact on the household, so the final step of creating a household is to "Move Transactions" from each previously created individual (also in that Constituent/Household Operations menu).

    Picking the address for the household is also super easy at creation time, as Boann said. And it will "move" the address to the household, so it can be inherited. Less cleanup!

    This method is preferred for us because it keeps attributes, interests, emails, business addresses, and other such things on the individual, which would be complicated to pull back out of a household. "Move Transactions" makes the household moves that we do need to make possible.

    I have still found some transactions that don't get moved using "Move Transactions" - like events, donated seats, solicitations - but weighing the pros and cons, we're sticking with this method for now.


    2) Convert an individual to household and then add additional member (we started this way, but quickly changed):

    This turned *all* of the individuals' info into household info - and if that works for you, then great - but we started to find problems with email sign-ups and such that it was better to keep the individual an individual.


    "Swap A1/A2" in the Constituent/Household Operations menu will help you with your salutation formatting. Much easier than trying to do N1/N2 by hand in v10. :)


    This has been our experience thus far (live in v11 for about 2.5 months now). YMMV.

    Beth

     

     

     

     

    BETH GILLILAND

    Tessitura System Administrator 
    bethgill@umich.edu
    734-615-9579 //  734-276-4816 cell
    www.ums.org  //  www.umslobby.org

     

Reply
  • $organization
    To piggyback on Boann's suggestion... it's the method we've chosen, even though there a couple of options that "appear" to do the same thing...

    (and I've totally just read Heather Kraft's response - who was thinking along the same lines - just faster at pushing the button!)

    1) Create new household and "fill" it (our chosen method):

    Creating a new household and putting the primary affiliates into it (whether they both existed previously or not) allows you to keep some individual settings on the individual's account, that would otherwise be stuck on the household account. We also transact on the household, so the final step of creating a household is to "Move Transactions" from each previously created individual (also in that Constituent/Household Operations menu).

    Picking the address for the household is also super easy at creation time, as Boann said. And it will "move" the address to the household, so it can be inherited. Less cleanup!

    This method is preferred for us because it keeps attributes, interests, emails, business addresses, and other such things on the individual, which would be complicated to pull back out of a household. "Move Transactions" makes the household moves that we do need to make possible.

    I have still found some transactions that don't get moved using "Move Transactions" - like events, donated seats, solicitations - but weighing the pros and cons, we're sticking with this method for now.


    2) Convert an individual to household and then add additional member (we started this way, but quickly changed):

    This turned *all* of the individuals' info into household info - and if that works for you, then great - but we started to find problems with email sign-ups and such that it was better to keep the individual an individual.


    "Swap A1/A2" in the Constituent/Household Operations menu will help you with your salutation formatting. Much easier than trying to do N1/N2 by hand in v10. :)


    This has been our experience thus far (live in v11 for about 2.5 months now). YMMV.

    Beth

     

     

     

     

    BETH GILLILAND

    Tessitura System Administrator 
    bethgill@umich.edu
    734-615-9579 //  734-276-4816 cell
    www.ums.org  //  www.umslobby.org

     

Children
No Data