Following users through the V11 upgrade process

Hi Gawain,

My understanding is that in the v11 migration, Name1 becomes the A1 affiliate (t_affiliation.name_ind = -1) and Name2 becomes the A2 affiliate (t_affiliation.name_ind = -2). So, you should be able to use that to match up your historical records and fix them.

Thanks,

David

I have a sticky issue.  We add a lot of custom information to our contributions for UC financial reporting purposes, including an attribute we use to identify the key that users are registered under in a university development database.  That database is keyed off of individuals, not users, so the attribute was N1/N2 driven, and was selected based on the N1/N2 choice on the contribution itself.

Now, we _want_ contributions to sit on the household account, we just need to flag, for UC reporting purposes, whether the contribution "belongs" to one or another of the users in the household (foundation, corporation, etc.).  The attribute storing the "CADS Id" will be split to individuals based on it's N1N2 indicator.  Since an individual will now be able to belong to multiple group accounts, I had intended to change our custom data entry screen to allow users to select relevant affiliates on the group account where the donation was being placed.

But I don't see an easy way to fix historical records to point to the correct user.  Is there any connection or record of who belonged to what, and as which name?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!