When adding an affiliation to a household, I don't see "Child Member" as an option. Am I missing something? What should I be checking to see if it's set up correctly?
All, due to the issue with the forum not posting the reply from Kevin via email, I'm pasting it here for reference:
Check that the affiliation type exists in TR_AFFILIATION_TYPE and then that it is associated with the constituent type used by the household in TX_CUST_TYPE_AFFILIATE.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
Aha! Thanks Kevin (and Todd!) It was tx_cust_type_affiliate I was missing. Updated that, and it seems to be working.
Learning a lot everyday!
And as the problem is persisting with this thread, here are a couple other replies in this thread that were only via email:
From Sabina Spilkin:
"Does TX_CUST_TYPE_AFFILIATE exist in version 10.1 ?
Sabina"
And a reply from Kevin Sheehan:
"No. It is a v11 table.
Kevin"
And a follow-up question from Sabina:
"Kevin, is it still OK to add an entry to TR_AFFILIATION_TYPE for mapping purposes?
Yes, you can add entries to that table as part of the mapping for your migration.
-Kevin
A couple more posts on this topic:
From Fernando Margueirat:
"Just to clarify, the table is created by the migration toolkit, so you can have a v. 10.1 database with that table in it.
Fernando Margueirat
Business Analyst
The National Ballet of Canada"
And following afterward from Kevin Sheehan:
"To further clarify, TX_CUST_TYPE_AFFILIATE is added to the database when you install the migration toolkit in v10.1, but it is not added to the System Tables screen and it should not be manually edited on the back end as any changes you make will be overwritten (based on your mapping) each time staging is run (including right before the commit step suring the upgrade). Once you upgrade to v11 you will see the table on the System Tables screen and you are free to edit it."