Hello, after running Migration - Check Database report , a list was created 'V11 Check-Sol/Task Diff n1n2'. We only have a few records in it but I can not see what is wrong with these records. What should I be looking for ?
Thanks,
Sabina
Thanks Heather. It actually does.
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Heather KraftSent: Wednesday, January 11, 2012 10:24 AMTo: Sabina SpilkinSubject: Re: [Tessitura Next Generation Forum] V11 Check-Sol/Task Diff n1n2
Sabina -
I think that list is solicitations that have n1n2_ind where a task doesn’t have a matching n1n2_ind. See if that rings true!
HeatherSeattle Rep
From: Sabina Spilkin <bounce-sabinaspilkin7252@tessituranetwork.com>Sent: 1/11/2012 12:01:47 PM
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!
For the same message from the Migration Check Database report, but in our case, many differing n1/n2:
Report says, "N1/N2 will be ignored on task." This message seems pretty clear to me, but some colleagues question my interpretation, so I'm looking for an experienced opinion. We just want to know if it's a requirement to clean these up in order to keep them.
Say we are migrating solicitations and associated tasks to household, should we expect:
1) task moved to household with solicitation record ignoring only the N1/N2
OR
2) task ignored (not moved) with solicitation record, due to the N1/N2 situation
Thanks!
John,
1-ish. The parent solicitation will be moved (or not) based on the N1N2 indicator on the solicitation, any tasks affiliated with that solicitation will be moved with the solicitation regardless of the N1N2 ind. You will not orphan any tasks by not taking any action.
Best,
Anna