• Replies 4 replies
  • Subscribers 332 subscribers
  • Views 101 views
  • Users 0 members are here
Related

Extractions - Ticketing History

Rog Hildreth
$organization

Hi,

We have had a request for a data extraction to include constituents' ticketing histories. I've been unable to successfully include these, and having watched the 3 Introduction to Output Set Builder for v11 T-Casts, I take it that this may be impossible due to it being a multiple-line extraction. However, in Part 3 it does mention writing code to include strings of information. Has anyone successfully done this with ticketing histories, and if so do you have code to add to the TR_Query table? 

Many Thanks,

Rog



[edited by: Rog Hildreth at 9:34 AM (GMT -6) on 5 Aug 2013]
Parents
  • $organization

    Hi Rog

     

    It says there is an issue with the query generated. That element should work with all other elements, so there may be something about the custom elements that ‘upsetting’ it.

     

    Also you have not modified the Tickets-Number Of Unique Perfs element in anyway? Also have you tried running the Output Set with just that element? Just to make sure it is mapped properly for your Ticket History setup>

     

    If that doesn’t shed any light, then it might quicker to submit a help ticket.

     

    But great to hear that you have got some data out!

     

    Cheers

    S.

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Rog Hildreth
    Sent: Wednesday, 7 August 2013 12:57 AM
    To: Sandra Ashby
    Subject: RE: [Tessitura Marketing Forum] Extractions - Ticketing History

     

    Hi Sandra,

    Thanks very much for the information, I've now successfully extracted the ticketing data via the Execute An Output Set report, featuring Performance Name, Performance Date and Number Of Seats.

    I have found including certain elements in the Output Set returns an error message. If I include 'Tickets-Number Of Unique Perfs' or the report returns the error:

    SyntaxFromSQL caused these errors: SQL State = 42000
    Microsoft OLE DB Provider for SQL Server
    Incorrect syntax near the keyword 'From'.
    execute dbo.RP_RUN_QUERY;1 @query_no = 10, @list_no = 0

    Can I just ask if this is an error at my end or do certain elements not work for this type of report?

    Thanks again,
    Roger

    From: Sandra Ashby <bounce-sandraashby2064@tessituranetwork.com>
    Sent: 8/6/2013 1:16:45 AM

    Hi Rog

     

    If you are outputting all the ticket history for a customer the output set will return multiple rows and hence won’t work with extractions. You can save the Extraction to a List and then run ‘Execute and Output Set’ and multiple rows won’t be an issue.

     

    Depending upon how your ticketing history is formatted (each site customises this area), you may only have one row per performance. If the extraction you are wanting to do is only for one performance AND you have one row of data only per performance in Ticket history – then yes you can use extractions. However, the output set elements would need to have at least one parameter of perf_no or perf_code (depending upon whether or not it is for performances that have been sold in Tessitura or Legacy Ticket History)

     

    Outputting the string of data that is covered in part 3 of the T-Cast series is to avoid creating a Cartesian Product which is where erroneous multiple rows are returned. Different to your scenario.

     

    Cheers

    Sandra

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Rog Hildreth
    Sent: Tuesday, 6 August 2013 12:40 AM
    To: Sandra Ashby
    Subject: [Tessitura Marketing Forum] Extractions - Ticketing History

     

    Hi,

    We have had a request for a data extraction to include constituents' ticketing histories. I've been unable to successfully include these, and having watched the 3 Introduction to Output Set Builder for v11 T-Casts, I take it that this may be impossible due to it being a multiple-line extraction. However, in Part 3 it does mention writing code to include strings of information. Has anyone successfully done this with ticketing histories, and if so do you have code to add to the TR_Query table? 

    Many Thanks,

    Roger




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

    Hi Rog

     

    It says there is an issue with the query generated. That element should work with all other elements, so there may be something about the custom elements that ‘upsetting’ it.

     

    Also you have not modified the Tickets-Number Of Unique Perfs element in anyway? Also have you tried running the Output Set with just that element? Just to make sure it is mapped properly for your Ticket History setup>

     

    If that doesn’t shed any light, then it might quicker to submit a help ticket.

     

    But great to hear that you have got some data out!

     

    Cheers

    S.

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Rog Hildreth
    Sent: Wednesday, 7 August 2013 12:57 AM
    To: Sandra Ashby
    Subject: RE: [Tessitura Marketing Forum] Extractions - Ticketing History

     

    Hi Sandra,

    Thanks very much for the information, I've now successfully extracted the ticketing data via the Execute An Output Set report, featuring Performance Name, Performance Date and Number Of Seats.

    I have found including certain elements in the Output Set returns an error message. If I include 'Tickets-Number Of Unique Perfs' or the report returns the error:

    SyntaxFromSQL caused these errors: SQL State = 42000
    Microsoft OLE DB Provider for SQL Server
    Incorrect syntax near the keyword 'From'.
    execute dbo.RP_RUN_QUERY;1 @query_no = 10, @list_no = 0

    Can I just ask if this is an error at my end or do certain elements not work for this type of report?

    Thanks again,
    Roger

    From: Sandra Ashby <bounce-sandraashby2064@tessituranetwork.com>
    Sent: 8/6/2013 1:16:45 AM

    Hi Rog

     

    If you are outputting all the ticket history for a customer the output set will return multiple rows and hence won’t work with extractions. You can save the Extraction to a List and then run ‘Execute and Output Set’ and multiple rows won’t be an issue.

     

    Depending upon how your ticketing history is formatted (each site customises this area), you may only have one row per performance. If the extraction you are wanting to do is only for one performance AND you have one row of data only per performance in Ticket history – then yes you can use extractions. However, the output set elements would need to have at least one parameter of perf_no or perf_code (depending upon whether or not it is for performances that have been sold in Tessitura or Legacy Ticket History)

     

    Outputting the string of data that is covered in part 3 of the T-Cast series is to avoid creating a Cartesian Product which is where erroneous multiple rows are returned. Different to your scenario.

     

    Cheers

    Sandra

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Rog Hildreth
    Sent: Tuesday, 6 August 2013 12:40 AM
    To: Sandra Ashby
    Subject: [Tessitura Marketing Forum] Extractions - Ticketing History

     

    Hi,

    We have had a request for a data extraction to include constituents' ticketing histories. I've been unable to successfully include these, and having watched the 3 Introduction to Output Set Builder for v11 T-Casts, I take it that this may be impossible due to it being a multiple-line extraction. However, in Part 3 it does mention writing code to include strings of information. Has anyone successfully done this with ticketing histories, and if so do you have code to add to the TR_Query table? 

    Many Thanks,

    Roger




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing 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 Marketing Forum. You may reply to this message to post to the Marketing 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
  • $organization in reply to Sandra Ashby

    Hi. I've just tried running each of the Ticketing elements one-by-one as single entries in the Output Set. I'm still getting this error for the 'Number Of Unique Performances' and I also encounter error messages for 'Single Ticket Amount' and 'Tickets Total Amount' (all the others are working fine). I'm not aware of any changes having been made to these elements, so I'll submit a ticket as you suggest.

    Thanks again for your help.

    Rog