RE: Affiliations - Migraition Tools for Lay person

Here are the few items we noticed.  I think Leslie’s list is far more inclusive.

When we went through the affiliations and set everything up one distinction that caused us a few problems was around son and daughter affiliations.  These got mapped as child members and they typically got added with their parent as a household.  In several cases this isn’t what we wanted as it was an adult child and it should be two separate accounts.  I know that this was a mapping issue on our side and a mistake we made but I think that it is worth mentioning.

We also found that when moving N2 to N1 it didn’t move the indicators as we had thought.  This is just something to be aware of because in v11 those indicators is how it decides which things go to the individual accounts.

Finally we saw some issues with staff using reciprocal affiliations instead of primary affiliations which created some issues when we converted.

If you want more information feel free to contact me directly.

Thanks,

Dave Alton

213.972.7539

Center Theatre Group  

I keep wondering if the Alpha sites might want to let the rest of us know what they have learned about Affiliations now that they are up an running that they wish they knew when they were setting things up

Being a Beta site and looking at the first pass of test data in v. 11 --I know there are few things I wished I understood a little better and had a tool that would have helped in dealing with Affilations coding.    I am sendingi this out to the community in hopes that the  Alpha and other Beta sites might chime in.

Our AppSupport folks have been great at getting the data converted but while we were working to get the data clean for the initial pass  there was another layer -- that of coding the Affiliations so they appear correctly in v.11 which was missed.  

What I have finally begun to develop is a spreadsheet to track all the components across the 3 tables used (Affiliation, Relationship and Customer Type).   It would be great if the Migration package could provide a report that would provide this same information from the tables themselves  for reveiw by Development and other departments who then mark up for updates to the AppSupport.   Missing from below is Show Salary.

Having this would also assist in testing to see if things behave the way we thought it would.  

In just using this spreadsheet it helped me see how I might break out the 4 standard Relationship Categories.  For instance once in v.11  -- it becomes apparent that Family should be Family and Extended Family.  

In this way adult children and/or mother-in-laws don't become part of an empty-nester Household. 

Employment is another Relationship Category that will want to be expanded in its affiliation types  so they can be ranked for display as well and to exclude employee affiliated only for matching gifts purposes from jumping ahead of Executive/Managment. 

Hope this helps some of you and I'd love hear more about how folks are navigating through things.   

Just one more thing -- I want to thank whoever it was who added the Bill Gates data to the Sandbox.   Stumbling across that helped me understand so much more about Affiliations etc.

--
View this message online at http://www.tessituranetwork.com/COMMUNITY/forums/p/6578/20769.aspx#20769 or reply to this message
--
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!