When I drill in to a performance using Season Manager>House View>Product Catalog>[performance]>Performance Summary for my current season, I'm getting information for performances this month and next month, but there is no data displayed for anything beyond that. But if I go to Season Manager>Season Overview>[season]>[performance] for the later performances, the data is all there. The season has "display EIS" checked and the season overview scripts are running with the correct arguments (thus it is visible through Season Overview).
Does anyone know why these views would be different?
--Gawain
I’d suggest checking Publish Client Dates in the performance set detail screen.
Julie Ornelas
Ticket Services Director
South Coast Repertory
(714) 708-5572
julieo@scr.org
Want to know more about our plays? Visit our website at www.scr.org!
P Please consider the environment before printing this email.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Gawain Lavers Sent: Tuesday, June 15, 2010 2:22 PM To: Julie Ornelas Subject: [Tessitura Technical Forum] performance summary information missing
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!
Hi Gawain,
Were you able to figure this out?
Gloria
Nope, but the problem went away by itself.
If I'm understanding the problem correctly, we had the same issue - and it was frustrating because it was intermittent/"fixed itself"!
With the help of Karen Sterkowicz at Tessitura, we discovered that in the jobs set up to update the Season Overview - Season Overview Nightly Update and Season Overview Periodic Update, there is a varchar that was set to 256. However, our season string had gotten really long - including commas it was up to over 300 characters; and anything after 256 was being ignored. She changed the varchar to a higher number (350) and voila! we have not had the problem since.
Hope this helps...
Stacey Voigt Database Manager Santa Barbara Center for the Performing Arts (805)899-3000 x128 svoigt@granadasb.org