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
We created a new local history table with the missing pieces we needed and replaced the screen in the application with a new one. We then updated the old ticket history and output set elements to point to the new tables (subs and tickets). Create a new nightly job to populate them.
I have not tried it, but could you not just mix these two ideas? Create a new local view instead of table so you do not have have a nightly job populating a local table, and then create local versions of all the regular List Manager elements (that you actually use) in a folder labelled something like "Ticketing - UMS" that all point to this new view then.
That seems like it should work, but I have not tried it.
Ahh, very interesting idea! That was another thought I had. I don't want to mess with Tess standard criteria but yes, I like the idea of another folder with the "good" criteria that uses the new local view. Thanks!