Extractions - Ticketing History

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!

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!