Version 12 Pricing

Hi there,

We are currently testing version 12.0.3 and I have 3 questions around pricing:

  • Is there a way to copy a price type (including all layers) for an existing performance? We have 6 layers to each price type and I'm copying each layer individually when adding a price.
  • When adding start and end times to a price type (or mode of sale for that matter) can you add a start time from the calendar and an end time from the relative settings all in one step? Usually we add a start time of 'yesterday' and end it 90 mins after the show
  • When adding a new price type to the performance, is there a way to specify what ticket design to use without changing it after adding the price?

That's a lot for one post! Help with any of these would be much appreciated! I may just be missing something in the documentation.

Craig

  • Craig,

     

    There is no way to copy a price type as it is configured across all layers.  In the case that you need to add the same price type to several layers as you describe, you will need to do it individually.  I should also point out that if this is a new setup (not currently on sale) I would strongly urge you to reconsider using events instead of layers.  Unless the different pieces really need to go to separate GLs.  All of the efficiency we added to pricing setup favors this approach.

     

    For start and end date editing take a look at the Bulk Edit feature on the properties view.  This lets you apply a relative start or end date to any or all price types at once.  Even better, if you are doing this in bulk take a look at the same feature, but in season maintenance on the composite view.  If you use relative dates in this view, Tessitura will do all of the calculations for you.

     

    As far as the ticket design, you can select a default ticket design in the price type setup screen. This is the one that will be applied by default whenever an instance of that price type is added to a grid. If it differs a lot from production to production, then you will have to change it as you add.  If this is the case you might consider changing the default to be the correct design for the items you are working on, so that at least it could save you a few steps.

     

    Hope this helps, and again if possible I would urge you to spend some time playing with events to see if you can replace some of those layers and make setup a little easier.    

     

    Dave

     

    From: Technology Roadmap Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Craig McDermott
    Sent: Thursday, March 13, 2014 11:20 AM
    To: Dave Aholt
    Subject: [Technology Roadmap Forum] Version 12 Pricing

     

    Hi there,

    We are currently testing version 12.0.3 and I have 3 questions around pricing:

    • Is there a way to copy a price type (including all layers) for an existing performance? We have 6 layers to each price type and I'm copying each layer individually when adding a price.
    • When adding start and end times to a price type (or mode of sale for that matter) can you add a start time from the calendar and an end time from the relative settings all in one step? Usually we add a start time of 'yesterday' and end it 90 mins after the show
    • When adding a new price type to the performance, is there a way to specify what ticket design to use without changing it after adding the price?

    That's a lot for one post! Help with any of these would be much appreciated! I may just be missing something in the documentation.

    Craig




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

  • Hi Dave,

    As of now, we do have all layers pointing to different GLs so I may have to copy each layer individually. We will certainly explore using pricing events for future setups though.

    For the start and end times, is there a way to combine the calendar and relative date setup in one step? ie. For a number of performances, I want all price types, for all shows, to start now but end 90 minutes after each performance.

    Thanks very much Dave for the help on all of this!

    Craig 

  • Craig,

     

    No, unfortunately you can only be in one date mode at a time.  So you would need to do your start dates using the calendar, apply, then use the relative mode for end dates.

     

    Dave

     

     

    From: Technology Roadmap Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Craig McDermott
    Sent: Friday, March 14, 2014 10:50 AM
    To: Dave Aholt
    Subject: RE: [Technology Roadmap Forum] Version 12 Pricing

     

    Hi Dave,

    As of now, we do have all layers pointing to different GLs so I may have to copy each layer individually. We will certainly explore using pricing events for future setups though.

    For the start and end times, is there a way to combine the calendar and relative date setup in one step? ie. For a number of performances, I want all price types, for all shows, to start now but end 90 minutes after each performance.

    Thanks very much Dave for the help on all of this!

    Craig 

    From: Dave Aholt <bounce-daveaholt2143@tessituranetwork.com>
    Sent: 3/14/2014 8:57:35 AM

    Craig,

     

    There is no way to copy a price type as it is configured across all layers.  In the case that you need to add the same price type to several layers as you describe, you will need to do it individually.  I should also point out that if this is a new setup (not currently on sale) I would strongly urge you to reconsider using events instead of layers.  Unless the different pieces really need to go to separate GLs.  All of the efficiency we added to pricing setup favors this approach.

     

    For start and end date editing take a look at the Bulk Edit feature on the properties view.  This lets you apply a relative start or end date to any or all price types at once.  Even better, if you are doing this in bulk take a look at the same feature, but in season maintenance on the composite view.  If you use relative dates in this view, Tessitura will do all of the calculations for you.

     

    As far as the ticket design, you can select a default ticket design in the price type setup screen. This is the one that will be applied by default whenever an instance of that price type is added to a grid. If it differs a lot from production to production, then you will have to change it as you add.  If this is the case you might consider changing the default to be the correct design for the items you are working on, so that at least it could save you a few steps.

     

    Hope this helps, and again if possible I would urge you to spend some time playing with events to see if you can replace some of those layers and make setup a little easier.    

     

    Dave

     

    From: Technology Roadmap Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Craig McDermott
    Sent: Thursday, March 13, 2014 11:20 AM
    To: Dave Aholt
    Subject: [Technology Roadmap Forum] Version 12 Pricing

     

    Hi there,

    We are currently testing version 12.0.3 and I have 3 questions around pricing:

    • Is there a way to copy a price type (including all layers) for an existing performance? We have 6 layers to each price type and I'm copying each layer individually when adding a price.
    • When adding start and end times to a price type (or mode of sale for that matter) can you add a start time from the calendar and an end time from the relative settings all in one step? Usually we add a start time of 'yesterday' and end it 90 mins after the show
    • When adding a new price type to the performance, is there a way to specify what ticket design to use without changing it after adding the price?

    That's a lot for one post! Help with any of these would be much appreciated! I may just be missing something in the documentation.

    Craig




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

  • Maybe a service interceptor pluggin could be used to fill the gaps.

  • That's what I thought but just wanted to make sure.

    Thanks again!

    Craig