• Replies 2 replies
  • Subscribers 337 subscribers
  • Views 12 views
  • Users 0 members are here
Related

Re: Adding Prod SeasonintoListManager criteria

Tina Treants
$organization
Heather,
Yes, we have vs_prod_season
 which basically has the fields seen in the Production Season tab of Ticketing Set Up> Production Elements:
prod_season_no
prod_no
season
premiere
edit_ind
 
we have history written to lp_tck_hist which does NOT include prod_season :
tck_no
customer_no
performance_name
performance_code
performance_dt
matinee_or_evening
tcK_amt
ticket_type
num_seats
registrant
price_type
comp_code_reason
seat_location
source_code
season
mos_category
 
As for my prowess in sql, I can read it  well enough to get the gist but can't figure out inner/outer joins. So, help is appreciated. I have been trying things in our test environment, I am usually the one who makes (simple) entries in our T-Keyword table for such purposes but this one is baffling me.
Thanks
Tina

>>> "Heather Kraft" <bounce-heatherlaidlawkraft3507@tessituranetwork.com> 05/30/2012 6:37 PM >>>

Hey Tina -

Without knowing how much access to the DB you have, you'd have to do a join on your local ticket history table out to some more tables to get production season. That isn't actually stored in your local table. 

I know lots of people have custom views which link productions, prod season, seasons together - I'm still using one from Andrea Crain in Chicago (thanks Andrea!). If you let us know how much (if any) SQL access and knowledge you have, I'm sure more suggestions will start flying!

- Heather

From: Ryan Rowell <bounce-ryanrowell5634@tessituranetwork.com>
Sent: 5/30/2012 6:08:35 PM

Great, so you want !.season instead of !.prod_season

Data Type = Number
Edit Mask = (blank)
Detail Tble = (name of your local table)
Detail Col = !.season
Ref Tbl = vrs_season
Ref Idcol = id
Ref Desccol = description



--
View this message online at http://www.tessituranetwork.com/Community/forums/p/7341/23053.aspx#23053 or reply to this message
--
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!
  • $organization

    Oops, sorry Tina!
    I didn't grasp what you were looking for, for some reason. I'll play around with this when I have a little time and get back to you if I come up with some ideas.

  • $organization in reply to Ryan Rowell

    Hi again Tina,

    Someone may have a better way about this, but I think you might want to just make a local view of your ticket history table and append prod_season_no onto it.
    Looking at the fields you have currently, I think you would need to do a left join to t_perf on perf_code (performance_code).
    We don't use performance codes in our table but I was able to create a version of the same view using perf_no to join on (which we do have in our table) and it appears to be working fine.
    Once this is all tested you would probably want to replace the Detail Tbl contents in t_keyword from your local table to the new local view.

    Again, someone may have a better plan of attack but feel free to shoot me an email if you want some help building this local view.

    Cheers!

    rrowell@acttheatre.org



    [edited by: Ryan Rowell at 1:20 PM (GMT -6) on 1 Jun 2012]