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.
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.