• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 1383 subscribers
  • Views 209 views
  • Users 0 members are here
Options
Related

Is there a code example for creating a basic constituent record in SQL?

David Dwiggins
$organization

We are hosting a video premiere where our goal is to get as many viewers as possible while gathering e-mails for future followup. So we're looking for a very streamlined signup process that will allow us to gather firstname, lastname, e-mail, and (optionally) zip, and then send them the link to the premiere page. We would obviously like to capture these signups for future communication in Tessitura.

I've set up a wordfly pages form that can gather the info, and presumably this will work for getting the info into a table in Tessitura. But I would like to develop a process for matching it up to constituents, adding a relevant activity flag for those who already exist, and, more importantly, creating a new skeleton constituent record for those who don't.

I have never programmatically created a constituent record before, and don't quite know where to start. I can see that there is code in AP_CONSTITUENT_IMPORT I could probably crib from, but is massively complex compared to the four data fields I basically have to start from.

I'm wondering if there exists somewhere an example of the minimal SQL needed to create a very basic constituent record.

Parents
  • 0 $organization

    Personally I'd sell/register them through TNEW(orother transactional path) and send them the link in the order confirmation.  That way they set themselves up.  We do this a fair bit and I don't think that the pathway is long enough to be off putting to signups especially given the wins on customer sign up.  You can also out a couple of survey questions for data enrichment in the sign up (event detail) page and run that through a stored proc to update their records. 

    To go full WFPages and record the data back in Tessitura WF tables I think that unless you use a link to the WFPage survey with the Tessitura Constituent ID already created you are not going to save it back to Tess (I could be very wrong and want to test it now).  So capturing the survey results in WF alone you could lay out the data according to the constituent import utility and import it but you'd have to do a match up to remove (and update) your current constituent records. 

    That being said you could create a link to your survey using a generic Tessitura constituent (like New 42 did in their attached mini magic which works a treat) and run the match up on the eaddress column.  Then you would be able to do as Andrea says.

    MM19-23.pdf

Reply
  • 0 $organization

    Personally I'd sell/register them through TNEW(orother transactional path) and send them the link in the order confirmation.  That way they set themselves up.  We do this a fair bit and I don't think that the pathway is long enough to be off putting to signups especially given the wins on customer sign up.  You can also out a couple of survey questions for data enrichment in the sign up (event detail) page and run that through a stored proc to update their records. 

    To go full WFPages and record the data back in Tessitura WF tables I think that unless you use a link to the WFPage survey with the Tessitura Constituent ID already created you are not going to save it back to Tess (I could be very wrong and want to test it now).  So capturing the survey results in WF alone you could lay out the data according to the constituent import utility and import it but you'd have to do a match up to remove (and update) your current constituent records. 

    That being said you could create a link to your survey using a generic Tessitura constituent (like New 42 did in their attached mini magic which works a treat) and run the match up on the eaddress column.  Then you would be able to do as Andrea says.

    MM19-23.pdf

Children
No Data