I am asked every new season to create new campaigns and elevated events that are nearly identical to previous years save for the start and end dates, designations and fyear. Doing this one at a time is tedious even with the copy mechanism in the campaign setup screen in the client.
What are the implications of writing some sort of script that will create new campaigns and elevated events for whatever date range I supply on the back-end rather than go through the front-end in Tessitura?
Thank you, Tessiturians.
That sounds like what I’m looking for, Gawain. Thank you for the follow-up. I look forward to this information.
Matt Gonzales
Database Administrator
510 Preston St. | Houston | TX 77002
T: 713-980-8702
E: mgonzales@hgo.org
Click here to view our website.
This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Gawain Lavers Sent: Monday, August 25, 2014 12:21 PM To: Matt Gonzales Subject: Re: [Tessitura Technical Forum] Cumbersome Campaign Creation
Funny you should ask: a very brief overview of my season setup script will be available on this site when the conference slides are posted: Code Solution Roundup was the session title, I think.
My code is a little rough in places, and has a lot of specific stuff for our organization, but I'm going to be reviewing and fixing it up shortly as we've made some major changes in our campaign structure, and maybe when I've had a chance to touch it up I might be able to share.
There are a few gotchas: there are a number of tables that are updated by going through season/campaign setup that are not obvious or enumerated in the System Tables. There are a few keys that are not proper identity keys, but are managed in the T_NEXTID (sp) table. That sort of thing.
From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com> Sent: 8/25/2014 11:34:21 AM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!