Education - Children's Classes

Hi Robert -

Just a clarification question for you - are you talking about a system table/way of migrating these already created associations or are you talking about a way in version 11 of continuing to create them via the web?

- Heather

Hi Robert -

Just a clarification question for you - are you talking about a system table/way of migrating these already created associations or are you talking about a way in version 11 of continuing to create them via the web?

- Heather

In versionn 10.0 of Tessitura we have a stored procedure for the web that will automatically create an association in tessitura if a constituent purchases a child's class, based on a content field. The constituent must fill out all of the children's information then two constituent records are created with an association are created in Tessitura. The constituent has the ability of defining the type of the association via a drop down (Parent -Child, Grandparnent .....)

We have just started with our Version 11.0 project.  In version 11.0 is there a way of defining in some kind of system table that if an association of a particular type will automatically place the constituent as an affilate under the constituent who purchased the record?  

Bob

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!

We do something similar for our education classes and camps on the web.  For v11 we had to make several modifications to our sales procedure including:

• Updating where we store age and gender information.  It used to be stored on the association but we changed to storing gender on the general tab in the normal field and birthdate as an attribute.
• Updating the local stored procedure we call to return the children affiliated to a household and verify that they meet the age requirements for the class.  This procedure references a custom line in T_DEFAULTS where we have the ID # of the correct affiliation type.
• Writing a new local procedure to call to add the birthdate attribute to the child's record since the API doesn't natively allow for adding attributes to records that aren't logged in.
• Updating the call we are using when setting up new accounts to UpdateAccountInfoEx2 so that we can convert them to household accounts (you may need to put in a ticket to Tessitura for a bug fix on this call - we did).

I think that covers it though I may have forgotten something - basically we tried to move as much of the functionality as we could to standard Tessitura functionality rather than leaving it customized. Let me know if you have questions.  My best advice is to test early and test often.  We were delayed in our testing for several reasons and have had to scramble a bit more than I prefer though overall things are working well.  

We do something similar for our education classes and camps on the web.  For v11 we had to make several modifications to our sales procedure including:

• Updating where we store age and gender information.  It used to be stored on the association but we changed to storing gender on the general tab in the normal field and birthdate as an attribute.
• Updating the local stored procedure we call to return the children affiliated to a household and verify that they meet the age requirements for the class.  This procedure references a custom line in T_DEFAULTS where we have the ID # of the correct affiliation type.
• Writing a new local procedure to call to add the birthdate attribute to the child's record since the API doesn't natively allow for adding attributes to records that aren't logged in.
• Updating the call we are using when setting up new accounts to UpdateAccountInfoEx2 so that we can convert them to household accounts (you may need to put in a ticket to Tessitura for a bug fix on this call - we did).

I think that covers it though I may have forgotten something - basically we tried to move as much of the functionality as we could to standard Tessitura functionality rather than leaving it customized. Let me know if you have questions.  My best advice is to test early and test often.  We were delayed in our testing for several reasons and have had to scramble a bit more than I prefer though overall things are working well.  

Hi Robert -

Just a clarification question for you - are you talking about a system table/way of migrating these already created associations or are you talking about a way in version 11 of continuing to create them via the web?

- Heather

In versionn 10.0 of Tessitura we have a stored procedure for the web that will automatically create an association in tessitura if a constituent purchases a child's class, based on a content field. The constituent must fill out all of the children's information then two constituent records are created with an association are created in Tessitura. The constituent has the ability of defining the type of the association via a drop down (Parent -Child, Grandparnent .....)

We have just started with our Version 11.0 project.  In version 11.0 is there a way of defining in some kind of system table that if an association of a particular type will automatically place the constituent as an affilate under the constituent who purchased the record?  

Bob

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!


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!