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.
Hi Matt Gonzales,
Hi there from the Houston Symphony! This post is pretty old but I thought I'd check in anyways.
We also create lots of campaigns that are pretty much the same except for FYear/date and goal information. I'm wondering if you're still on that kind of Campaign model, where Campaigns are created each FYear that are FY-specific.
A lot of things rely on campaign numbers here, and it works pretty well for future giving (into future FYear etc) to be able to be campaign_no specific. We're looking into a 'reuse Campaigns and change the FYear and dates on these every year' model that would prevent lots of work each year related to Campaign setup and would also stream line our accounting.
Would you have some time to compare notes on Campaigns and their back-end maintenance?
Thank you,
Caitlin