Version 12 Season Maintenance - Pricing

Hi

Hands up ticketing set-up folk who are now on Version 12? Do you remember good ol' faithful version 11?

Question: I have added a standard price type to select number of performances (the same title and season - well the same everything) using Season Maintenance (thank goodness for Season Maintenance a saving grace). However, when I applied the standard price type, I accidentally missed a few performances of the same title and so the Standard price type was not added. Are you with me so far? So, I search for all the dates again, including the ones I missed, using Season Maintenance. I then went back to find a little green circle (you know the ones? They tell you that a price layer does not exist on all performances performances) on the Ticket Price 1 tab. Are you still me reader?

I made sure the All performances was showing thinking that if I right clicked and added a price type it will apply the Standard price (or is that layer?) to all the performances that didn't have this price type. To my bafflement it didn't nor would it let me remove the current price type on the other performance - an error message appear stating something about subline items...bearing in mind no sales have taken place on any of these performances. Now if you remember in Version 11 - when one did the same process in Season Maintenance, it would pick up all the performances that didn't have the price type - remember good ol' 'View Current' and 'View result's' and 'Update buttons' in v11 pricing? and then apply the price type to the relevant performances.

So what did I do I hear you cry - yes I can hear you...I had to manually apply the price type to every single performance as I could not fathom out or find any of the literature to tell me how to unpick this muddle. Perhaps someone out there could tell me how to unpick it for future reference.

Any, once I had done all of that I wanted to change that start and end dates of this price type. Now I always set the Start Date as the date I am working on it (makes sense doesn't it, so that I can access there and then) and then set my End Date as -1 (remember good ol' minus in v11?). Now you are probably sitting there asking why would anyone do that? Well if a performance had to be reopened the following day for whatever a reason - returning a ticket for example on a past / matured performance - the end date and therefore the price type would still be active.

Now for some reason the duality of Start and end date fields in the new v12 Modes of Sale tab in Season Maintenance have stayed the same. So I can have the start date fixed and a calendar date 12/09/14 and then the extra combo on + or - as my end dead - brilliant. Well done one and all. However, when I am trying to do this in the pricing I am faced with either 'relative dates' OR 'absolute dates' but I can have a bargain bucket Kentucky fried chicken combo of both...why? I seriously do ask myself why? This was a brilliant function in v11. Now what I am faced with or rather finding myself doing is adding the price types at various start and end dates, then going in to Season Maintenance,  selecting the relative start date and checking the box and applying the changes. Then changing the start end dates option back to specify absolute date, checking the box changing the date to -1 sorry 1 date 'after' then applying the changes (its that little button to the left that doesn't really scream out to you). So my question is - am I doing something wrong here as well or has this process now become a little bit so involved? Why can't we see both relative and specify date boxes at the same time and exactly as the MOS tab. Is there a quicker option to all of this as we set-up folk use to do on v11?

And finally copying a performance. Do you remember when you copied a performance the default field was the perf code then tab to date and time and save - magic! Now were are faced with Prod Season as the default blue highlighted field - why? I don't want to change this? I don't ever want to change this? I'd be very grateful if someone could tell me why I would need to. So my final question is: can a sites IT team override this in the 'behind the scenes' world of Tessitura? So that the default field is the Perf Code? This now makes copying performances even more challenging? which is fine but I had hoped for something more. Well I live in hope.  

Very much looking forward to v12.5.

Many thanks and I look forward to your replies rolling in.