v12 standard ticket history table

Hi All,

In v11, the standard ticket history table (LVS_TKT_HIST) had a column of price type group.  When we went to v12 we used the new standard ticket history table (VS_TICKET_HISTORY) and it no longer has the price type group column.  We had a list criteria for price type group and now I can no longer find a way to build something in T_KEYWORD to have a list criteria for price type group.  In the meantime, I'm writing SQL to plug into list manager so that users can still pull info on price type group but that doesn't feel like the ideal solution.  I considered making a new local view that adds the price type group column in and having T_KEYWORD reference that view to pull price type group.  However, when I use that criteria in list manager with another criteria that pulls the standard ticket history table, I'm getting inaccurate list pulls.  

Anyone have any creative solutions to this problem?  Is there a way to do a join within T_KEYWORD so that I can pull in the data on price type group while still using the standard ticket history?

Thanks!

Jenny Graf

Parents
  • You don’t need to create a new view or custom version of the ticket history table. You just need to add a sub-entity criterion. Sub-entity criteria evaluate sub-entities of other data entries, allowing you to reference data that does not have a constituent ID on it if you can tie it back to a parent entity that does have a constituent ID. In other words, you can reference data that’s not included in the ticket history as long as you can tie it to the ticket history in a single step. We had this in mind when choosing which data had to be included directly in the standard ticket history and which did not.

     

    Here’s a link to the help topic that explains sub-entity criteria: http://www.tessituranetwork.com/Help_System_v125/Content/v12/Updates%20to%20Criteria%20Sets.htm

     

    In this case, you would add a new criterion that evaluates the Price Type Category column in the TR_PRICE_TYPE table and then set the Parent Table to T_TICKET_HISTORY, the Parent Key column to price_type, and the Key Column to id.

     

    Kevin Sheehan

    Senior Technical Writer & Consultant

    Tessitura Network

    +1 888 643 5778 x 329

    ksheehan@tessituranetwork.com

     

  • AHA!  Genius!  I thought it felt weird that the price type group went away but glad to hear that this was still something you all had in mind.  I should have known you would think of everything!  :-)

Reply Children
No Data