I hope this is the correct forum to post this question. We have just tried pulling an extraction for multiple past performances, and instead of coming up with the number of single ticket buyers, it is giving us the total subscribers for that season. I'm using the criteria "Ticketing Performance Name," which, until now, has always provided us with the results we wanted.
This is a new problem, I'm not sure what we did to cause this. Does anyone have any ideas? Might it have anything to do with how our scheduled jobs are set up to collect history? Any way to sort this out?
Any help would be appreciated.
Depending on how your ticket history is set up, you may be able to distinguish between subscription tickets (‘S’ in our system) and single, individual tickets (‘I’). It’s recorded as price_type in t_tck_hist.
Lucie
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Brian O'Neill Sent: Wednesday, December 09, 2009 1:43 PM To: Lucie Spieler Subject: [Tessitura Technical Forum] Updating Ticket History
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!
Brian -
Depending on how your ticket history is set up, you might also want to consider suppressing subscribers in a segment of your extraction by using the 'Subscription Season' criteria or something along those lines.
- Heather
Hi Brian,
The way it's worded it sounds like you are only getting subscribers, is that correct? If so try running a simple list with just a single "ticketing performance name" to see if you get the same results, if you do you might want start by reviewing the t_keyword system table to see if something has been changed for that keyword number and if not you would want to review your extraction segments to see if they are getting weeded out somewhere. If you are in fact getting both single and subs in your extraction I second Heather's suggestion.
Cheers!
Thanks for the suggestions. For the record it is a large extraction covering several seasons, so the suppression report will show a ridiculous amount of constituents in the single events and then zero for the season. So, everyone is getting on the list, but under the wrong category.
I think my underlying problem lies somewhere in the update history procedures, as it seems to report a season in a constituent's subscription history, but then splits the events within that season and records it also as single ticket history.
We record every ticket in the "performance history" which I assume you mean when you say "single ticket history" regardless of if it's single or subscription, which (I think) is the norm since you would be lacking production records for your subscribers if you did not. It sounds to me like the problem is in the layout of the extraction. If I'm understanding you correctly you'll want to create segments for your subscribers first so that they are naturally suppressed from the segments for single ticket buyers that come after. You might want to post your definition report.