Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
Hello Networkers,
We have a unique Tessitura Household situation involving two VIPs.
A VIP named Mrs. X's husband passed away and a separate VIP named Mr. Y’s wife passed away. In an interesting twist, the two widows have met, fallen in love and married.
Now, they would like to combine everything; their names in the program, their partner with a player, their subscription seating and their credit card information.
We obviously do not want their history to be affected, but we would like to honor their request and combine them as a new Household.
What's the best way to do this, while ensuring that their ticketing, individual contribution history, etc. won't be negatively affected? Please, remember, both individuals have a rich history, with sizable contributions.
Thank you!
That makes the most sense. Again note, note. Perhaps add the void merge attribute—just in case. It might require some manipulation in memberships, too depending on the setup.
Their new household lives together will reflect their purchases as a couple and maintain the history they enjoyed with their deceased spouses.
Michelle
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Kristina Williams Sent: Thursday, April 24, 2014 8:27 AM To: Michelle Wohlers Subject: Re: [Tessitura Development Forum] Combining VIP Households
Assuming you store ticket/contribution history on the household level, I think I would try something like the following:
Convert Mrs. X's household account into an individual account. Merge her with the household account and add an association between her and her deceased husband (we have an association type of ex-spouse, but you could use whatever works best for you).
Do the same with Mr. Y's household account.
Create a brand new household account: The Mr. Y and Mrs. X household. Add Mr. Y and Mrs. X as primary affiliates to that household account. At this point you will have a household account with no history, and its 2 primary affiliates will each have all of their individual history.
As you move forward, you can start to put transactions on their shared household account - subscription, program recognition, etc - but you would still always have the history on the individual accounts.
I would also be sure to add a note in the household account (a CSI or Research note, or whatever you use to keep track of things like this) to explain the situation. That way nobody will accidentally move all of those transactions to the household level later.
It's a little weird, but I think it might serve your purposes.
From: Alina Strauss <bounce-alinapopescu2912@tessituranetwork.com> Sent: 4/23/2014 6:59:53 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hello Everyone,
I appreciate each and everyone of your insightful instructions. I will return to this forum to post any positive or negative outcomes that result from this newly formed household which contains clear notes (lots of them!), void merges under Attributes, and many relationship affiliations linking each constituent to their past history. After testing it out in Tessitura TEST, I am happy to announce that Mrs. X and Mr. Y are Tessitura official!
Thanks to all!