Conditional Name in Ticket Design Elements

Hi all, 

I'm working to set up a conditional name in a ticket design so that orders with SLI recipients will print with recipient names and those without will print with owner names. So far I have a method that works when I execute LP_Ticket_Elements in SSMS, but maybe I'm not understanding what parameters are passed into LP_Ticket_Elements? 

Here's what I'm using so far:

If @ude_no = 1

Begin

If @sli_recipient_no is not null

 Select @ude_value = display_name

              From dbo.FT_CONSTITUENT_DISPLAY_NAME()

              Where customer_no = @sli_recipient_no

else

Select @ude_value = display_name

From dbo.FT_CONSTITUENT_DISPLAY_NAME()

Where customer_no = @customer_no

End

Any insight is greatly appreciated, Thank you!
Parents
  • Hi Roberta,

    You’re absolutely right, since you’re only getting one header per order printed, and you could theoretically have as many recipients as SLIs, there may not be a practical way to do Recipients on the header.

    I’ve set ours up to apply recipient names to the ticket mostly with our group sales and tourism department in mind. Group bookings by an agent on behalf of tour operators will print with the tour operators names on the tickets instead of the booking agent who might not ever put the ticket directly in the customer’s hands.

    It would though definitely be a time saver to get the print process to turn out one corresponding header per unique value in the recipient column. I’d love to hear about it if anyone has a good/any way to do this.

     

     

     

    Jeff Gallo
    Box Office Supervisor, Virginia Arts Festival
    jgallo@vafest.org
    P: 757.282.2825  //  F: 757.282.2787
    440 Bank Street, Norfolk, VA 23510
    www.vafest.org
    Get Social with Us! Facebook, Twitter, Instagram, and Tumblr. #VaArtsFest

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Roberta Harrill
    Sent: Tuesday, January 31, 2017 6:29 PM
    To: Jeffrey Gallo
    Subject: Re: [Tessitura Ticketing Forum] Conditional Name in Ticket Design Elements

     

    Plus we only need one header for each recipient - not a header for each ticket. This will require a think.......

    From: Roberta Harrill <bounce-robertaharrill9583@tessituranetwork.com>
    Sent: 1/31/2017 6:00:01 PM

    OK I think I got to the bottom of our issue with this. We don't put the customer name on the ticket. We have a header ticket with the customer's name address etc. LP_TICKET_ELEMENTS has the potential of 10+ parameters being passed to it from TP_GET_HEADER_ELEMENTS and from TP_GET_TICKET_ORD_ELEMENTS. Unfortunately the key parameter that is needed to make this script work on a Header ticket is not being passed to the LP_TICKET_ELEMENTS from TP_GET_HEADER_ELEMENTS




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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
  • Hi Roberta,

    You’re absolutely right, since you’re only getting one header per order printed, and you could theoretically have as many recipients as SLIs, there may not be a practical way to do Recipients on the header.

    I’ve set ours up to apply recipient names to the ticket mostly with our group sales and tourism department in mind. Group bookings by an agent on behalf of tour operators will print with the tour operators names on the tickets instead of the booking agent who might not ever put the ticket directly in the customer’s hands.

    It would though definitely be a time saver to get the print process to turn out one corresponding header per unique value in the recipient column. I’d love to hear about it if anyone has a good/any way to do this.

     

     

     

    Jeff Gallo
    Box Office Supervisor, Virginia Arts Festival
    jgallo@vafest.org
    P: 757.282.2825  //  F: 757.282.2787
    440 Bank Street, Norfolk, VA 23510
    www.vafest.org
    Get Social with Us! Facebook, Twitter, Instagram, and Tumblr. #VaArtsFest

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Roberta Harrill
    Sent: Tuesday, January 31, 2017 6:29 PM
    To: Jeffrey Gallo
    Subject: Re: [Tessitura Ticketing Forum] Conditional Name in Ticket Design Elements

     

    Plus we only need one header for each recipient - not a header for each ticket. This will require a think.......

    From: Roberta Harrill <bounce-robertaharrill9583@tessituranetwork.com>
    Sent: 1/31/2017 6:00:01 PM

    OK I think I got to the bottom of our issue with this. We don't put the customer name on the ticket. We have a header ticket with the customer's name address etc. LP_TICKET_ELEMENTS has the potential of 10+ parameters being passed to it from TP_GET_HEADER_ELEMENTS and from TP_GET_TICKET_ORD_ELEMENTS. Unfortunately the key parameter that is needed to make this script work on a Header ticket is not being passed to the LP_TICKET_ELEMENTS from TP_GET_HEADER_ELEMENTS




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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