Hi
I am trying to find people who have booked for a group of concerts but not another. I am suppressing the concert, and then pulling everyone else. All fine so far. However, people who have purchased the concert through a package are still coming out in the Extraction.
I think this is to do with the difference between the local Ticket History table and the local Subscription History table - however I can't work out how to suppress people who have purchased just one concert from a package.
Do I need to make some changes to my custom job that populates the Ticket History table, or add something to TR_QUERY_ELEMENT?
Thanks
Siobhan
We never used the subscription history table, so we have pulled in all the tickets (from T_SUB_LINEITEM) into ticket history regardless of whether they were purchased as part of a package or as a single ticket.
I have also added a couple of lines to T_KEYWORD that exposes the TX_PERF_SEAT table (fields perf_no and seat_status), which allows us to get an up-to date customer list on who has booked (or reserved) seats for particular performance/s (future only) - mainly did this to ensure that we weren't contacting people who had already booked (or reserved) seats for the production we were promoting (as ticket history was only updated over-night and doesn't include reservations).
Mark
Thanks Mark. Would you mind emailing me your Ticket History update script?
Thanks again