Where does perf_name pull from in T_TICKET_HISTORY? I had assumed T_INVENTORY, but that doesn't appear so...? Unless I am seriously missing something .. which, let's be real, is a distinct possibility. :)
I am trying to clean up some remnants in terms of out dated Performance Name standardization was left over from when we were part of a consortium. Its a mess and my Type A needs it to be fixed. We do not have any orders from prior to moving from our consortium - only ticket history - so I am hoping that T_ORDER and T_SUB_LINEITEM have nothing to do with it.
Also, when the TP_UPDATE_TICKET_HISTORY runs, does it overwrite the existing table or just appends for additional historical items? Considering this just in case I am feeling adventurous and want to update T_TICKET_HISTORY manually. O.o
Any insight would be appreciated!
Thanks!
It pulls it from T_PERF.
perf_no int NULL (from T_PERF)
Tessitura has a document regarding table structures:
"Tessitura Table Structures V12.5"
T_TICKET_HISTORY The T_TICKET_HISTORY table contains a row for each performance/zone/price type/order combination for each constituent
NOTE: This table is used for the standard ticket history introduced in v12. If your organization was using Tessitura prior to v12 and did not choose to implement the standard ticket history, you will not have data in this table. ... 1.2.5. perf_no int NULL (from T_PERF)
Thanks, Neil!
Unfortunately, that's the perf_no, not the perf_name. There isn't a column for perf_name in the T_PERF table. The perf_no in T_PERF pulls from T_INVENTORY which is why I thought that was my table. :)
Oops, your right:
1.2.7. perf_name varchar(60) NULL
It doesn't tell you where it pulls it from.
Perf_name is the short_name column from T_INVENTORY, unless I am much mistaken, which comes from the "Short Name" box when you are building the performances in the Ticketing Setup module.
From what I can glean from the TP_UPDATE_TUCKET_HISTORY stored procedure, John is correct.
The perf_name column of the T_TICKET_HISTORY table gets it's information from the @perf_desc variable; and the @perf_desc variable gets it's information from the short_name column of the T_INVENTORY table. Looks like that is the table that needs to get updated.
Neil Cole | Customer Service Specialist Principal
neil.cole@state.mn.us
o: 952.431.9213 | MNZOO.ORG
13000 Zoo Boulevard Apple Valley MN 55124
________________________________________
Yup, that is what I thought too. And it does appear to be the case. I just wanted to make sure I wasn't overlooking something in the SP. It would seem that perhaps I may have just been impatient with respect to the SP as a lot (if not all) of my data seems to have updated.
Patience is a virtue and all of that. :)