We were needing to do an audit of hold codes for a 2 week run of a show in our main hall. They wanted totals for the entire run and the hold code reports break everything out by individual performances, meaning we would have to manually add all the numbers together. I created an analytics dashboard with the data fields Seat Hold Code and then a value using Total Seat Unsold Count. We used this number to perform our audit, but then we needed to generate maps for all the hold code locations. Upon finishing the maps and comparing to map totals to the audit totals from Analytics, we are off by several hundred for a few different hold codes. I looked through the hold code map applications from the T_SESSION table and no new hold codes were applied today for those performances.
I looked through the documentation and it says that the Seat Unsold Count datafield is determined by a Seat Sold Flag, with the definition "Y is returned for reserved and ticketed seats and all SLIs." Am I reading that correctly that any seat associated to an SLI, even if that SLI was voided or for a returned ticket, then it counts it as a sold seat? Or is there perhaps another reason behind such a huge discrepancy? Does anyone have any ideas on how to just simply get seats that are currently available?
I'm glad I went to the forums and didn't submit a ticket for this because I think I was just not calculating things correctly. So I think I can honestly say, nothing I claimed in this post is accurate.