Output Set v Lists

Hi

I have created a list in List Manager.

I have created an output set with the following criteria

Ticketing Performance Name*

Ticket Order Date*

And a few other lines that have * at the end

Can someone please explain what the * means. I know it returns multiple values.

Why does it over ride the criteria in the list that we have pulled it against.

the list has an order date and MOS.

But when i pull the above list against the output set builder it gives me shows outside the order date and outside the MOS.

At the end of the day, i want to know

During DATE, by ticket method X, tell me everyone who purchased a ticket.

Then using output set builder (if correct method), Show me from teh above list

name, suburb, postcode (know how to pull on Output set builder)

Ticketing performance name (of ONLY the shows, within the list date and MOS)

how many tickets they purchased, how often they purchased (i.e via MOS more than once during that time frame)

Thanks Amanda

 

  • Former Member
    Former Member $organization
    Literally try sketching that out on a sheet of paper, or better, in a spreadsheet--I'm not sure it works.  Imagine more than one performance attended during the time period.  Should the data columns expand in number?  That probably indicates the need for a pivot table.  Show where  the summary information (how many, how often, and MOS) should fit onto your worksheet and submit your design.

    On Mar 2, 2010, at 9:47 PM, "Amanda Fairbairn" <bounce-amandafairbairn1420@tessituranetwork.com> wrote:

    Hi

    I have created a list in List Manager.

    I have created an output set with the following criteria

    Ticketing Performance Name*

    Ticket Order Date*

    And a few other lines that have * at the end

    Can someone please explain what the * means. I know it returns multiple values.

    Why does it over ride the criteria in the list that we have pulled it against.

    the list has an order date and MOS.

    But when i pull the above list against the output set builder it gives me shows outside the order date and outside the MOS.

    At the end of the day, i want to know

    During DATE, by ticket method X, tell me everyone who purchased a ticket.

    Then using output set builder (if correct method), Show me from teh above list

    name, suburb, postcode (know how to pull on Output set builder)

    Ticketing performance name (of ONLY the shows, within the list date and MOS)

    how many tickets they purchased, how often they purchased (i.e via MOS more than once during that time frame)

    Thanks Amanda

     




    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!
  • I think Warren's suggestion of a pivot table is right on the money.  A somewhat more detailed explanation of the infamous "*" in output sets:

    Your list contains only customer numbers no matter what criteria you have used to contruct it.  When you use an output set item that can return multiple rows, it is connecting all of those customer numbers to all of the data on the output side (performances for instance). This potentially creates multiple rows. When you have multiple "*" items in your output set the effect is multiplied.  So if a patron attended 3 events you will get three rows for performance name. If they purchased tickets using 3 different price types it takes those 3 event rows and each one then gets 3 price types for 9 rows.

    This isn't a perfect example, but it illustrates how fast the data gets out of hand.  The key to remember is that your list criteria don't affect the output set at all since all the list is providing is customer numbers.

    At least that is what I've come to understand about output sets. Its certainly not one of my strong areas.

    Another option you might consider is using your list as a parameter on one of the box office reports.  Although I can't think of one off the top of my head that might have the fields you are looking for, perhaps some of the box office folks have some ideas?

  • Former Member
    Former Member $organization in reply to Levi Sauerbrei
    Nicely explained!  It's worth noting that multiple rows aren't necessarily a bad thing.  An output set is exactly the way, for instance, to get a listing to use for mailing all known active email addresses on your patron accounts (we relied on this frequently during our recent snow emergencies).
      

    On Mar 3, 2010, at 6:16 AM, "Levi Sauerbrei" <bounce-levisauerbrei8271@tessituranetwork.com> wrote:

    I think Warren's suggestion of a pivot table is right on the money.  A somewhat more detailed explanation of the infamous "*" in output sets:

    Your list contains only customer numbers no matter what criteria you have used to contruct it.  When you use an output set item that can return multiple rows, it is connecting all of those customer numbers to all of the data on the output side (performances for instance). This potentially creates multiple rows. When you have multiple "*" items in your output set the effect is multiplied.  So if a patron attended 3 events you will get three rows for performance name. If they purchased tickets using 3 different price types it takes those 3 event rows and each one then gets 3 price types for 9 rows.

    This isn't a perfect example, but it illustrates how fast the data gets out of hand.  The key to remember is that your list criteria don't affect the output set at all since all the list is providing is customer numbers.

    At least that is what I've come to understand about output sets. Its certainly not one of my strong areas.

    Another option you might consider is using your list as a parameter on one of the box office reports.  Although I can't think of one off the top of my head that might have the fields you are looking for, perhaps some of the box office folks have some ideas?

    From: Warren Evans <bounce-warrenevans4782@tessituranetwork.com>
    Sent: 3/3/2010 12:10:05 AM

    Literally try sketching that out on a sheet of paper, or better, in a spreadsheet--I'm not sure it works.  Imagine more than one performance attended during the time period.  Should the data columns expand in number?  That probably indicates the need for a pivot table.  Show where  the summary information (how many, how often, and MOS) should fit onto your worksheet and submit your design.

    On Mar 2, 2010, at 9:47 PM, "Amanda Fairbairn" <bounce-amandafairbairn1420@tessituranetwork.com> wrote:

    Hi

    I have created a list in List Manager.

    I have created an output set with the following criteria

    Ticketing Performance Name*

    Ticket Order Date*

    And a few other lines that have * at the end

    Can someone please explain what the * means. I know it returns multiple values.

    Why does it over ride the criteria in the list that we have pulled it against.

    the list has an order date and MOS.

    But when i pull the above list against the output set builder it gives me shows outside the order date and outside the MOS.

    At the end of the day, i want to know

    During DATE, by ticket method X, tell me everyone who purchased a ticket.

    Then using output set builder (if correct method), Show me from teh above list

    name, suburb, postcode (know how to pull on Output set builder)

    Ticketing performance name (of ONLY the shows, within the list date and MOS)

    how many tickets they purchased, how often they purchased (i.e via MOS more than once during that time frame)

    Thanks Amanda

     




    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!
  • Something that I said to someone who have asked me this very question:

     

    List Manager is WHO

    Output Set Builder is WHAT

     

    -Ryan

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Warren Evans
    Sent: Wednesday, March 03, 2010 8:47 AM
    To: Ryan Creps
    Subject: Re: [Tessitura Marketing Forum] Output Set v Lists

     

    Nicely explained!  It's worth noting that multiple rows aren't necessarily a bad thing.  An output set is exactly the way, for instance, to get a listing to use for mailing all known active email addresses on your patron accounts (we relied on this frequently during our recent snow emergencies).

      


    On Mar 3, 2010, at 6:16 AM, "Levi Sauerbrei" <bounce-levisauerbrei8271@tessituranetwork.com> wrote:

    I think Warren's suggestion of a pivot table is right on the money.  A somewhat more detailed explanation of the infamous "*" in output sets:

    Your list contains only customer numbers no matter what criteria you have used to contruct it.  When you use an output set item that can return multiple rows, it is connecting all of those customer numbers to all of the data on the output side (performances for instance). This potentially creates multiple rows. When you have multiple "*" items in your output set the effect is multiplied.  So if a patron attended 3 events you will get three rows for performance name. If they purchased tickets using 3 different price types it takes those 3 event rows and each one then gets 3 price types for 9 rows.

    This isn't a perfect example, but it illustrates how fast the data gets out of hand.  The key to remember is that your list criteria don't affect the output set at all since all the list is providing is customer numbers.

    At least that is what I've come to understand about output sets. Its certainly not one of my strong areas.

    Another option you might consider is using your list as a parameter on one of the box office reports.  Although I can't think of one off the top of my head that might have the fields you are looking for, perhaps some of the box office folks have some ideas?

    From: Warren Evans <bounce-warrenevans4782@tessituranetwork.com>
    Sent: 3/3/2010 12:10:05 AM

    Literally try sketching that out on a sheet of paper, or better, in a spreadsheet--I'm not sure it works.  Imagine more than one performance attended during the time period.  Should the data columns expand in number?  That probably indicates the need for a pivot table.  Show where  the summary information (how many, how often, and MOS) should fit onto your worksheet and submit your design.


    On Mar 2, 2010, at 9:47 PM, "Amanda Fairbairn" <bounce-amandafairbairn1420@tessituranetwork.com> wrote:

    Hi

    I have created a list in List Manager.

    I have created an output set with the following criteria

    Ticketing Performance Name*

    Ticket Order Date*

    And a few other lines that have * at the end

    Can someone please explain what the * means. I know it returns multiple values.

    Why does it over ride the criteria in the list that we have pulled it against.

    the list has an order date and MOS.

    But when i pull the above list against the output set builder it gives me shows outside the order date and outside the MOS.

    At the end of the day, i want to know

    During DATE, by ticket method X, tell me everyone who purchased a ticket.

    Then using output set builder (if correct method), Show me from teh above list

    name, suburb, postcode (know how to pull on Output set builder)

    Ticketing performance name (of ONLY the shows, within the list date and MOS)

    how many tickets they purchased, how often they purchased (i.e via MOS more than once during that time frame)

    Thanks Amanda

     




    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!




    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 Amanda,

    It is possible to create combined output set items with parameter functions. 

    We have a couple that are used by our fundraising team. One gives the production name, performance date and the number of tickets purchased all in one go. It gets rid of the mix-and-match problem you've identified with info being duplicated or muddled across rows when there are multiples.

    In tr_query_element;

    Ticket dt~Perf name~No seats / Ticketing / cast(!.perf_dt as char (12)) + '~' + !.perf_name + '~' + cast(!.num_seats as char (3)) / LVS_TCK_HIST / !.perf_dt between <<p1>> and <<p2>>

    In tr_query_element_parameter;

    Date from / Datetime

    Date to / Datetime (with end of day ticked)

    The ~ means you can split the text if you export to Excel.

    Hopefully you can modify this to get what you're after, Suzanne.

  • Just one thing …

     

    You should use | instead of ~ as the delimiter.  ~ is used in PowerBuilder for commands and can result in unexpected results – ie a blank page for example when there shouldn’t be.

     

    Just thought I’d mention it as a point of interest.

     

    Cheers

    Sandra

     

    From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Suzanne Bridger
    Sent: Thursday, 4 March 2010 3:22 AM
    To: Sandra Ashby
    Subject: Re: [Tessitura Marketing Forum] Output Set v Lists

     

    Hi Amanda,

    It is possible to create combined output set items with parameter functions. 

    We have a couple that are used by our fundraising team. One gives the production name, performance date and the number of tickets purchased all in one go. It gets rid of the mix-and-match problem you've identified with info being duplicated or muddled across rows when there are multiples.

    In tr_query_element;

    Ticket dt~Perf name~No seats / Ticketing / cast(!.perf_dt as char (12)) + '~' + !.perf_name + '~' + cast(!.num_seats as char (3)) / LVS_TCK_HIST / !.perf_dt between <<p1>> and <<p2>>

    In tr_query_element_parameter;

    Date from / Datetime

    Date to / Datetime (with end of day ticked)

    The ~ means you can split the text if you export to Excel.

    Hopefully you can modify this to get what you're after, Suzanne.

    From: Amanda Fairbairn <bounce-amandafairbairn1420@tessituranetwork.com>
    Sent: 3/2/2010 11:45:00 PM

    Hi

    I have created a list in List Manager.

    I have created an output set with the following criteria

    Ticketing Performance Name*

    Ticket Order Date*

    And a few other lines that have * at the end

    Can someone please explain what the * means. I know it returns multiple values.

    Why does it over ride the criteria in the list that we have pulled it against.

    the list has an order date and MOS.

    But when i pull the above list against the output set builder it gives me shows outside the order date and outside the MOS.

    At the end of the day, i want to know

    During DATE, by ticket method X, tell me everyone who purchased a ticket.

    Then using output set builder (if correct method), Show me from teh above list

    name, suburb, postcode (know how to pull on Output set builder)

    Ticketing performance name (of ONLY the shows, within the list date and MOS)

    how many tickets they purchased, how often they purchased (i.e via MOS more than once during that time frame)

    Thanks Amanda

     




    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!

  • Thanks everyone for the help. I really appreciate it.

    Understand so much better now how output set builder works.

    Amanda