Originally, our teacher records were inadvertently set up as OI records - with the teacher's name on both N1 and N2. And now, in light of the migration, we're trying to figure out the right course with the following background:
So, should I also change the n1n2_format field in TR_CUST_TYPE and what effect does making that change have on the existing records (is it safe)?
As it turned out, when I went to fill out the TRU_CUSTOMER_MAPPING table row for Teacher (because the pre-migration script complained that it was not completely mapped), reasoned that the manual change to the T_CUSTOMER teacher entries should not be necessary with the appropriate changes made to the TRU_CUSTOMER_MAPPING teacher entry. Admittedly, there was a bit of wishful/magical thinking involved here fueled by my experimental nature. And I was wrong.
In the aftermath, it turns out that teachers were created as a School constituent type, with the original N2 information as the A1 affiliate record.
How should I have done this in order to have the original records migrate to a new individual record with constituent type of Teacher and no affiliates (associations to current school employer, yes)?
Thank you for your suggestions.
Hi Matt
We had a similar problem with the way our schools where setup. In the end we decided to convert all of the records to Corporate Contacts (IO names) before we carried out the migration. I wrote a script that went through an converted any records that had a last name 2 and were setup as organisations (OI) to Corportate Contacts.
I can send this over if you need it?
Thanks
Nick