Hello,
I am doing a report on constituent with ticket exchanges. My question is by looking at some of the SQL tables such as t_order_seat_hist, t_order, t_sli_status. How can I identify that constituent having some ticket exchange transaction in that constituent?
in fact, can I look at the order_no, sli_status for exchangeable??
Thanks,
-Harry
Hey Tom, some time ago I had investigated a number of these with support and we identified some defects. To your knowledge, were any of the "invalid data" you describe the result of "as designed" behavior? From: Tom Brown <bounce-tombrown3568@tessituranetwork.com> Sent: 4/4/2017 2:46:25 AM As you are looking at T_Order_Seat_History, be aware that there are combinations of actions that end users can do to create invalid data in this table. This impacts less than 1% of the data in our system. If you want more info, you can contact the Tessitura Network or reach out to me directly. On Mon, Apr 3, 2017 at 4:27 PM, Nick Reilingh <bounce-nicholasreilingh4883@tessituranetwork.com> wrote: I'm pretty sure you need to dig into the T_ORDER_SEAT_HIST table. Check out the Tessitura Table Structures document; it has a legend for every possible value in the event_code column, including 3 (Returned), 4 (Released), and 16 (Returned for Resale), which you will likely want to look into. I would recommend creating some sequences of actions in your test system and then observing what is written to T_ORDER_SEAT_HIST for each of those scenarios. From: Harry Hoang <bounce-harryhoang8094@tessituranetwork.com> Sent: 4/3/2017 3:29:48 PM Hello, I am doing a report on constituent with ticket exchanges. My question is by looking at some of the SQL tables such as t_order_seat_hist, t_order, t_sli_status. How can I identify that constituent having some ticket exchange transaction in that constituent? in fact, can I look at the order_no, sli_status for exchangeable?? Thanks, -Harry This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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! This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Hey Tom, some time ago I had investigated a number of these with support and we identified some defects. To your knowledge, were any of the "invalid data" you describe the result of "as designed" behavior?
From: Tom Brown <bounce-tombrown3568@tessituranetwork.com> Sent: 4/4/2017 2:46:25 AM
I'm pretty sure you need to dig into the T_ORDER_SEAT_HIST table. Check out the Tessitura Table Structures document; it has a legend for every possible value in the event_code column, including 3 (Returned), 4 (Released), and 16 (Returned for Resale), which you will likely want to look into. I would recommend creating some sequences of actions in your test system and then observing what is written to T_ORDER_SEAT_HIST for each of those scenarios. From: Harry Hoang <bounce-harryhoang8094@tessituranetwork.com> Sent: 4/3/2017 3:29:48 PM Hello, I am doing a report on constituent with ticket exchanges. My question is by looking at some of the SQL tables such as t_order_seat_hist, t_order, t_sli_status. How can I identify that constituent having some ticket exchange transaction in that constituent? in fact, can I look at the order_no, sli_status for exchangeable?? Thanks, -Harry This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
I'm pretty sure you need to dig into the T_ORDER_SEAT_HIST table. Check out the Tessitura Table Structures document; it has a legend for every possible value in the event_code column, including 3 (Returned), 4 (Released), and 16 (Returned for Resale), which you will likely want to look into. I would recommend creating some sequences of actions in your test system and then observing what is written to T_ORDER_SEAT_HIST for each of those scenarios.
From: Harry Hoang <bounce-harryhoang8094@tessituranetwork.com> Sent: 4/3/2017 3:29:48 PM