I have some confusion understanding the correct way to complete the TRU_ASSOCIATE_MAPPING and the V11_pre_upgrade_check.
I have reread the documentation and re-watch the webinar Anne gave.
I’m still getting errors for example that TRU_ASSOCIATION_MAPPING, Association pair friend/ friend not completely mapped. Which is in the ‘O’ other category and we have mapped new assoc type to friend and new other assoc type to friend.
My concern is why do I have to assign a New affil type; which means I have to create a new type to stop getting these errors in the V11_pre-upgrade_check.
Hi Joseph,
You need the affiliation to cover the scenario of a v10 individual record with name 2 being converted to a household during migration being associated to an individual record with no name 2 (I'm assuming the later will remain an individual in v11).
Because associations are between like for like records (individual to individual, group to group etc) , the association will be converted to an affiliation because the relationship is now between a group and an individual.
Basically, the columns 'New Assoc Type', 'New Other Assoc Type' and 'New Affil Type' in TRU_ASSOCIATION_MAPPING need to have values for all hard associations or you will get an error message.
Hope that makes sense.
Patrick.
We have run into the same kind of issue. It was Friend Associations that showed up 8 time once we get it into Version 11. I’d open a TASK online ticket to get support to help with the specifics of your circumstances.
Our issue appears to be a small number of records in TX_XREF that had NULL in the type column. This was causing the scripts that checked the database to add records to TRU_ASSOCIATION_MAPPING, which I think caused the multiple associations across the database. We are still working out the issues. We think we are close to a resolution.
I believe you can clean up TRU_ASSOCIATION_MAPPING. I’d make some kind of backup of the table before trying. Then delete all the records in the table. Then run the Migration – Check Database Report it will populate the TRU_ASSOCIATION_MAPPING table.
--Tom
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Richard JacksonSent: Monday, July 09, 2012 4:50 PMTo: Thomas BrownSubject: Re: [Tessitura Next Generation Forum] tru_association_mapping question
We've successfully converted out TEST system to v11 and while our inital mapping table did look "off" - I'm sure it was from converted data (we converted in January of 11 and now have to upgrade to 12), the issue we're having on duplicate associations is stumping me.
One pair of records I'm looking at as a reference is duplicated on each record so that customer A is associated to customer b 8 times in v11. Looking at TX_XREF, they have only two rows with matching assoc_id's and such and I'm not sure if we "over" mapped TRU_ASSOCIATION_MAPPING in zeal to get no errors on our database check or if the bad converted data is at play here. Any quick way to tell?
Followup question - is there a way to "wipe" the TRU_ASSOCIATION_MAPPING table and repopulate it via code now that we know what we're doing better so we can remap from the beginning?
From: Anna Wessely <bounce-annawessely5607@tessituranetwork.com>Sent: 2/23/2012 5:24:17 AM
Dale - these are ones where you should probably do the cleanup since there my be some affect on the migration. The choices are to try and cobble together the proper connections between the associations or if they are truly bad data then you may remove them from the table. That is going to be a bit up to you.
Anna
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!