Mass price increase in v12

Hello all - I'm faced with a situation where a new fee needs to be added post haste (the money train continues to roll on each day) to all tickets going forward.  We've established here that the easiest thing to do is to add $1 to an already exiting fee on all our tickets.

I tested it via a sql update on one performance on one zone and things were promising.  However, expanding that to an entire production season seems to crash our database.  Once the update is done, I cannot access any performances.  I've also tried using the Season Manager - Season Maintenance way to update the prices - but that seems to throw an error when updating a goodly number of performances even across just one price type.  I've heard rumors of a bug in v12.1 regarding Season Maintenance, so I've dropped that avenue since we cannot upgrade to 12.5 anytime soon due to productions in progress and a relatively new website still undergoing revisions.

This is all done in TEST, mind you - so it's not an emergency.

However, we have 291 performances we need to update with 21 different zones using 30 different price types.  Is there a programmatic way to do this or should I just send the box office flowers and have them update the prices manually?

Any ideas?  I have a script I've written for the test database - that seems to update the necessary table - which I'd be happy to send to anyone that might be able to help in case there is something in the script that is foul.  Any assistance or input is greatly appreciated, all.  Thanks!

RJ

Parents
  • Clean Clean false false false EN-US X-NONE X-NONE

    Hi,

     

    We’ve been following this thread hoping to see a solution. We have had a very similar problem since v12.1.1. We’re a museum doing general admission, but have a large number of active price types. Our problems in Season Manager seem to have been more related to the number of price zones, rather than price types. We have had copy performance issues as well with multiple zone performances, even when the number of price types is just 4 or 5; performances with 30 price types and one zone will copy just fine.

     

    Thanks.

     

    Ray

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Richard Jackson
    Sent: Wednesday, November 11, 2015 1:17 PM
    To: rbernard@smm.org
    Subject: RE: [Tessitura Technical Forum] Mass price increase in v12

     

    Not really – we used a work around.  Any programmatic update seemed to lock up Tess: the best I could manage was to get one zone for one performance updated with the new price.  So it had to be done manually.

     

    Changing the price if an existing fee and copying it across all the price types we had for any given performance crashed Tessitura as well.  So copying and pasting was out.

     

    What we ended up doing was creating a whole new layer and inserting it into every production season separately (one box office manager did our first show, another did our second show, so on and so forth) using a template I built that had the bare minimum of price types built into it (out of a possible 30 different price types that could be on any one show at a given time, I built the template using the 5 I knew would be on every show).  From there, each manager used Season Maintenance to go, performance by performance, add the layer, add it to the price types for that particular performance that it applied to (we did not increase prices on already publicized or fixed prices), saved it the moved on to the next performance. 

     

    With five managers changing prices on 8 production seasons with around 30 performances in each prod season, it took about 5 days to get it all done and we’re still cleaning up various issues like where the fee didn’t get made editable, or the minimum didn’t get set to zero (we’re allowed to wipe the fee for subscriber exchanges and such).

     

    It was a mess – but then any system of raising all prices across the board mid-season probably would have been.  Thanks for the advice though!

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
    Sent: Wednesday, November 11, 2015 12:56 PM
    To: Richard Jackson <richardj@alleytheatre.org>
    Subject: RE: [Tessitura Technical Forum] Mass price increase in v12

     

    Richard,

    Did you ever get this solved?  I would have responded earlier, but I was hoping another solution would occur to me, but alas none did.

    From: Richard Jackson <bounce-richardjackson6492@tessituranetwork.com>
    Sent: 10/30/2015 9:57:36 PM

    Hi John – I’ve tried this in the Season Maintenance view and end up getting the same error as when I tried updating the pricing.  Attached is an image of the error.  However, with the TASK system down, I can’t put a ticket in either.  I was kinda hoping to code my way around this, but that didn’t work either.  =(

     

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
    Sent: Friday, October 30, 2015 4:30 PM
    To: Richard Jackson <richardj@alleytheatre.org>
    Subject: Re: [Tessitura Technical Forum] Mass price increase in v12

     

    Could you use Season Manager - Season Maintenance to add a whole new price layer of your $1 fee to everything?  It might seem like a little much to add a whole new price layer to everything just for $1, but it seems like that would work better than updating existing prices as you could just add the layer with all the existing price types and calculate it all up $1 (excluding the comps).

    That is just off the top of my head; I am sure there are other solutions.

    From: Richard Jackson <bounce-richardjackson6492@tessituranetwork.com>
    Sent: 10/30/2015 5:08:52 PM

    Hello all - I'm faced with a situation where a new fee needs to be added post haste (the money train continues to roll on each day) to all tickets going forward.  We've established here that the easiest thing to do is to add $1 to an already exiting fee on all our tickets.

    I tested it via a sql update on one performance on one zone and things were promising.  However, expanding that to an entire production season seems to crash our database.  Once the update is done, I cannot access any performances.  I've also tried using the Season Manager - Season Maintenance way to update the prices - but that seems to throw an error when updating a goodly number of performances even across just one price type.  I've heard rumors of a bug in v12.1 regarding Season Maintenance, so I've dropped that avenue since we cannot upgrade to 12.5 anytime soon due to productions in progress and a relatively new website still undergoing revisions.

    This is all done in TEST, mind you - so it's not an emergency.

    However, we have 291 performances we need to update with 21 different zones using 30 different price types.  Is there a programmatic way to do this or should I just send the box office flowers and have them update the prices manually?

    Any ideas?  I have a script I've written for the test database - that seems to update the necessary table - which I'd be happy to send to anyone that might be able to help in case there is something in the script that is foul.  Any assistance or input is greatly appreciated, all.  Thanks!

    RJ




    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!




    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!




    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!

Reply
  • Clean Clean false false false EN-US X-NONE X-NONE

    Hi,

     

    We’ve been following this thread hoping to see a solution. We have had a very similar problem since v12.1.1. We’re a museum doing general admission, but have a large number of active price types. Our problems in Season Manager seem to have been more related to the number of price zones, rather than price types. We have had copy performance issues as well with multiple zone performances, even when the number of price types is just 4 or 5; performances with 30 price types and one zone will copy just fine.

     

    Thanks.

     

    Ray

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Richard Jackson
    Sent: Wednesday, November 11, 2015 1:17 PM
    To: rbernard@smm.org
    Subject: RE: [Tessitura Technical Forum] Mass price increase in v12

     

    Not really – we used a work around.  Any programmatic update seemed to lock up Tess: the best I could manage was to get one zone for one performance updated with the new price.  So it had to be done manually.

     

    Changing the price if an existing fee and copying it across all the price types we had for any given performance crashed Tessitura as well.  So copying and pasting was out.

     

    What we ended up doing was creating a whole new layer and inserting it into every production season separately (one box office manager did our first show, another did our second show, so on and so forth) using a template I built that had the bare minimum of price types built into it (out of a possible 30 different price types that could be on any one show at a given time, I built the template using the 5 I knew would be on every show).  From there, each manager used Season Maintenance to go, performance by performance, add the layer, add it to the price types for that particular performance that it applied to (we did not increase prices on already publicized or fixed prices), saved it the moved on to the next performance. 

     

    With five managers changing prices on 8 production seasons with around 30 performances in each prod season, it took about 5 days to get it all done and we’re still cleaning up various issues like where the fee didn’t get made editable, or the minimum didn’t get set to zero (we’re allowed to wipe the fee for subscriber exchanges and such).

     

    It was a mess – but then any system of raising all prices across the board mid-season probably would have been.  Thanks for the advice though!

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
    Sent: Wednesday, November 11, 2015 12:56 PM
    To: Richard Jackson <richardj@alleytheatre.org>
    Subject: RE: [Tessitura Technical Forum] Mass price increase in v12

     

    Richard,

    Did you ever get this solved?  I would have responded earlier, but I was hoping another solution would occur to me, but alas none did.

    From: Richard Jackson <bounce-richardjackson6492@tessituranetwork.com>
    Sent: 10/30/2015 9:57:36 PM

    Hi John – I’ve tried this in the Season Maintenance view and end up getting the same error as when I tried updating the pricing.  Attached is an image of the error.  However, with the TASK system down, I can’t put a ticket in either.  I was kinda hoping to code my way around this, but that didn’t work either.  =(

     

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
    Sent: Friday, October 30, 2015 4:30 PM
    To: Richard Jackson <richardj@alleytheatre.org>
    Subject: Re: [Tessitura Technical Forum] Mass price increase in v12

     

    Could you use Season Manager - Season Maintenance to add a whole new price layer of your $1 fee to everything?  It might seem like a little much to add a whole new price layer to everything just for $1, but it seems like that would work better than updating existing prices as you could just add the layer with all the existing price types and calculate it all up $1 (excluding the comps).

    That is just off the top of my head; I am sure there are other solutions.

    From: Richard Jackson <bounce-richardjackson6492@tessituranetwork.com>
    Sent: 10/30/2015 5:08:52 PM

    Hello all - I'm faced with a situation where a new fee needs to be added post haste (the money train continues to roll on each day) to all tickets going forward.  We've established here that the easiest thing to do is to add $1 to an already exiting fee on all our tickets.

    I tested it via a sql update on one performance on one zone and things were promising.  However, expanding that to an entire production season seems to crash our database.  Once the update is done, I cannot access any performances.  I've also tried using the Season Manager - Season Maintenance way to update the prices - but that seems to throw an error when updating a goodly number of performances even across just one price type.  I've heard rumors of a bug in v12.1 regarding Season Maintenance, so I've dropped that avenue since we cannot upgrade to 12.5 anytime soon due to productions in progress and a relatively new website still undergoing revisions.

    This is all done in TEST, mind you - so it's not an emergency.

    However, we have 291 performances we need to update with 21 different zones using 30 different price types.  Is there a programmatic way to do this or should I just send the box office flowers and have them update the prices manually?

    Any ideas?  I have a script I've written for the test database - that seems to update the necessary table - which I'd be happy to send to anyone that might be able to help in case there is something in the script that is foul.  Any assistance or input is greatly appreciated, all.  Thanks!

    RJ




    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!




    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!




    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!

Children
No Data