New Zones

UP_UPDATE_ZONE_NO is similar to UP_UPDATE_LOGICAL_NOS, except that it should be run if the zone of any seat is changed after performances or packages have been built. This procedure has an optional parameter of Season.  If that parameter is not passed, then all performances and packages are reviewed.  NB: Seats that have had their zone changed with the new dynamic zone function, introduced in v5.5, will not be affected by this utility.

J

I think I know the answer to this, If we and new zones to a zone map, is there any procedures I need to run. I have a feeling the answer is no.

Thanks

Marty

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!

Yeah, I did read that. But I am not changing the zone on a seat (well not yet) but just adding the zone(s) to the zone_map. I see the new zones on the existing price maps and in the Pricing details at the performance set up.

The next question is, What is this new dynamic zone function from v5.5? I think that is about the time I got introduced to Tessitura so as far as I know, we have always used the "New dynamic function"

Thanks,

The “new dynamic function” is the ability to rezone seats at the performance level from Season Maintenance.  Essentially these are temporary changes to a performance, instead of permanent changes to a facility.  They don’t affect any other performances and don’t affect any new performances.

If you want to permanently add a new zone to a seat map in Facility Manager and have it affect existing performances, you have to run those procedures.  If you only want the changes to affect new performances, you don’t have to run the procedures.

Adding the zone to the zone map, if it is not being assigned to an active performance or package, doesn’t require any additional utilities to be run.

The dynamic zone functionality that it speaks of is actually the Zones tab of Season Maintenance.  Up until that v5.5, it wasn’t possible to change the zone on a seat outside of adjusting the zone map and changing all performances for a season (using UP_UPDATE_ZONE_NO).  Using Season Maintenance the zone tab allows you to change the zone on a seat after the performance or package has been built without the utility.

Ok, I get it now.

Can I throw a "What if" at you?

If I decide that I do not want it to affect existing past performances and I choose not to run them but then later on I have another change to a different map and choose to run those procedures, all of my existing performances for the first map are going to get updated providing the two are in the same season?

Another question, When I run these procedures, what table(s) are affected? Little concern with custom reporting on zones. I assume that I should pull zone_no from t_sub_lineItem instead of tx_perf_seat?

The “master” if you will, for orders is always T_SUB_LINEITEM.zone_no.

You won’t be able to change the zone on a perf seat once it has been assigned to a ticket, so theoretically once an order is created, TX_PERF_SEAT and T_SUB_LINEITEM should be in sync for the relevant seat/perf/pkg.

-Ryan