Subscription Question

Greetings, Tessiturians.

It's another slow summer day in the off season.  Perfect time for silly questions like:

I know that Subscription information from seasons past (including the current season, though technically not over yet) can be found in T_SUBSCRIPTION_HIST.  But, where do I find subscription information (including data like the SERIES_NO and LOCATION) for upcoming seasons?

I'm assuming the information gets updated into the T_SUBSCRIPTION_HIST by some stored procedure call at the appropriate, pre-designated times, which is why my development contact didn't get next year's information like she wanted from Output Set Builder.

Any takers?  Or too early in the morning for silly questions from people that don't like going through reams of boring manuals before lunch?

Thank you in advance, as always, for your assistance.  Crowd surfing is my Tessitura research tool of choice.

BONUS TOOL-RELATED TRIVIA:  The opposite end of the striking face of a hammer is called the 'peen'.

Parents
  • Hi Matt,

     

    I’m going to try and not take that comment about boring manuals personally.  J  Besides, I don’t think you would have found the answer you were looking for anyway.

     

    I just wanted to jump into the conversation to make a little clarification.  The T_SUBSCRIPTION_HIST table is generally not used.  It is vestigial piece of Tessitura evolution, kind of like an appendix.  The subscription history you find on the Ticket History tab of a constituent record is usually stored in the LT_SUB_HIST table.  It’s an LT table because it is customizable and frequently customized.  As others have mentioned, that table is updated by a scheduled procedure and you need to add in new seasons to the procedure parameters as they are added.

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Reply
  • Hi Matt,

     

    I’m going to try and not take that comment about boring manuals personally.  J  Besides, I don’t think you would have found the answer you were looking for anyway.

     

    I just wanted to jump into the conversation to make a little clarification.  The T_SUBSCRIPTION_HIST table is generally not used.  It is vestigial piece of Tessitura evolution, kind of like an appendix.  The subscription history you find on the Ticket History tab of a constituent record is usually stored in the LT_SUB_HIST table.  It’s an LT table because it is customizable and frequently customized.  As others have mentioned, that table is updated by a scheduled procedure and you need to add in new seasons to the procedure parameters as they are added.

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Children
No Data