I have been asked to essentially unravel a ticket order in one account and take the 110 seats from this one order and divide them into 62 different constituent accounts so that the ticket history is accuratley reflected. To make this even more fun... its from a season that has already ended.
My thoughts are that I need to first turn the season back on and reactivate the MOS and Price Types and then return the seats in the original order and "buy" them back in each of the 62 different accounts.
If anyone has any better creative ideas, I welcome them.
Thanks!
Amy Aldrich
Ticket Operations Manager
Boston Symphony Orchestra
aaldrich@bso.org
If you are running version 9 you could try working with the new ticket import/export process to get what you want.
As a more direct route, one that I certanly have not tried and would approach with a great deal of testing before deploying...
You could create your new constituents and create dummy orders for each. Then you create a cross index table of the lineitms in the big order to the new destination orders. At that point, you could try to re-map the lineitems, sublineitems, ticket history, tx_perf_seat and so on to the desired values. I am not sure how the data in the t_order is populated, you might need to update the aggregate values in that table too. I might be missing other things you'd need to update. Try running a pord on the order on question to see what all you would need to think about.
Or you could do it the way you describe... Which is what I am thinking I would do if I were you. Probably a lot safer. But you did ask for creativity...
Good luck.
Matt