Hi folk,
When we migrated to the new ticket history tables (12.something?) we pulled across some of our legacy system data. This seemed to work well, but I have recently discovered when trying to pull some lists of constituents who purchased really old performances that for most of our legacy data, the production season field is null as the data did not relate to a Production Season built in Tess. Therefore, List Manager filters like Production Season obviously don't pull through that legacy data. I have to use the Performance Name criteria and manually type in the name of the event. It works, but it's clunkier than selecting from a dropdown of production seasons.
Has anyone dealt with this kind of thing before and found a way around it? I wonder if there is a way to create some pseudo Production Seasons for a List Manager criteria so I can select from a list? Or turn Performance Name into a dropdown, not a text field..?
Cheers
dgh
Hi DG,
This could be done quite easily but it would need some custom work. You would need to create a database view and then base your List Manager/Extraction criteria upon it.
Happy to help if you like - you know the email address to write to
Martin
Hi David,
I've done this using some SQL in the back-end. You'd just need to create the Titles, Productions, and Production Seasons in the front end and then update the corresponding perfs using some code like:
UPDATE T_TICKET_HISTORYSET prod_season_no = 1996, prod_no = 1769, title_no = 1768 WHERE perf_name LIKE '%Alice%' AND season = 18 AND prod_season_no IS NULL
I'd recommend testing first of course. The query below will give you an idea of what's missing:
SELECT s.fyear, s.description AS season_desc, th.*FROM T_TICKET_HISTORY AS thJOIN TR_SEASON AS s ON th.season = s.idWHERE prod_season_no IS NULLORDER BY s.fyear, s.description, perf_name, perf_dt
Thanks Martin, I might try 's idea below first then will give you a shout if that doesn't work out...
Thanks , this sure looks like a good way to go!
this works PERFECTLY!
Glad to hear that