1st Question
We have two different types of child records in Tessitura
I only want affiliations between the parent & child if the child is under 18. Otherwise I'd like them to remain as hard associations. Can someone check my work below to tell me if this would do it?
Anything prefixed with an X is an actual association I created as a "dummy". If I understand the documentation correctly, everything needs to be mapped unless it's a soft association in which case it's required to leave the CUR_OTHER_XREF_TYPE blank.
2nd Question
Will all soft associations get their own Tess account created regardless of how it's mapped?
3rd Sort-of Question
Also I saw this example in the migration documentation:
I'm confused as to why it wouldn't be mapped this way:
Phew Thanks in advance!
Sarah,
1) Soft associations are migrated as soft associations - no records are created in the migration process for them. If currently the children under 18 are soft they will remain that way in v11. Given that the child under 18 is a soft association the Household Create process will be skipped for those records. On the over 18, the difference between affiliations and associations is based on the constituent types involved. If you migrate an association between an over 18 and a parent and the parent record has two names the relationship will be migrated as a affiliation as the parent record will be migrated as a household, if there is only one name on the parent record the relationship will be migrated as an association as the parent will remain an individual.
2) No, soft associations will be migrated as soft associations.
3) The main reason for this is that in associations there is a reciprocal relationship between constituents, which means that there are actually two rows in the database one from parent to child and one from child to parent. Affiliations are a one way relationship, the individual's relationship to the group. There is nothing wrong with mapping the way you have it in your example, it is just that that Adult Member option will probably never be chosen so it is a little extra step you don't really need.
Best,
Anna
1. If I get this correctly, soft associations will be kept in the migration if I add a duplicate row for the child/parent link but this time mapping the OTHER_XREF_TYPE so it's blank. Soft associations will be lost in the migration if I don't take that extra step. If I want soft associations to create records for those children during the migration - that's not possible in the mapping of TRU_ASSOCIATION_TYPE. Did I get that all correct?
3. I think I understand. If I were to map it this way below - it would be ok because the parent to student affiliation of "Child Member" was already captured when I mapped it in the first row? At that point are you saying I only have to map associations one time? If that's the case are there any exceptions to that rule?
Probably your best bet is either to put them both to child member or child member/adult member. That way in case there is a configuration error or something you at least have the data in some shape to find it. Also a reminder that if you want someone from Tessitura to review your migration mapping you may want to contact consulting@tessituranetwork.com to have a look for you.