Just starting the data migration work and we have an association pair
Gala Guest -> Gala Host
Gala Host -> Gala Guest
We are hoping that there is a way to force this pair to only show up as an Association and never an affiliation.
Can this be done?
How does one setup TRU_Association_type to make this happen.
Heather,
I think that the key point here for us is
“You'd just make sure your associations are set up indicating N1/N2 and never use "both" in the association.”
And I’m fairly sure that both is what has been used?
Then the questions is:
To “Cleanup” or Not to “Cleanup” what is the cost and what is the benefit?
--Tom
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Heather KraftSent: Friday, November 18, 2011 5:57 PMTo: Thomas BrownSubject: Re: [Tessitura Next Generation Forum] How to "force" only associations during V11 Constituent Migration
Hi Tom -
I think this is dependent on several things - some you can control and some you can't.
A) v10 Corporate type of account associated with v10 individual
- Nothing you can do about this, if left, it will turn into an affiliation. The only way you could change this would be to change the Corporate side of the association to use an individual contact if that existed.
B) v10 account 1 with N1/N2 associated with v10 account 2 with N1
- If you want the relationship in v11 to be on the household of account 1, again it will be an affiliation between account 1 and account 2.
- If you want the relationship in v11 to be with N1 or N2 individual accounts linked to account 1 (I hope that makes sense) then you can assure that the relationship will migrate as an association by cleaning up your v10 associations. You'd just make sure your associations are set up indicating N1/N2 and never use "both" in the association. You'd also NOT check the 'Force Both' checkbox in the migration table as this would force the association to go to the household (if it existed). If
Does that make sense? I'm not nearly as coherent in my explanation as the Next Gen Team so maybe I should just let them answer this. :P
The really short answer is: If you have v10 organization types in the mix or want this relationship to be with the v11 household you are going to end up with both associations and affiliations for that particular v10 association.
- Heather
From: Heather Kraft <bounce-heatherlaidlawkraft3507@tessituranetwork.com>Sent: 11/18/2011 3:29:36 PM
Tom -
It's my understanding that you can't force a pair to be only association because the association/affiliation determination is completely dependent on the type of the two accounts it is linking.
The means like type to like type (e.g. individual to individual, corporate/household to corporate/household) will always be an association and unlike type to unlike type (e.g. individual to corporate/household) will be an affiliation. There's no getting around that. The only thing you can do is make sure your current associations won't migrate to one of the unlike type pairs.
Don't take my answer for law, but I *think* that's what I've been told multiple times as I've tried to work through relationships myself.
HTH,
Heather
You 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!