One of my users is attempting to use Lists and Output Set Builder to pull some ticketing information. The list works properly, and pulls only the customers that bought from the selected performances.
The problem comes in with Output Set Builder pulling all ticket history for those users. I realize I can probably set up TR_QUERY_ELEMENT and TR_QUERY_ELEMENT_PARAMETER (if I knew how) to filter to the correct performances, but that would require selecting the same performance data twice, once in the list, and once in Output Set Builder.
Is there a better way?
Nope. There is no relation between the list criteria and the data returned by the output set. The list criteria is used to generate the contents of your list but after that your list is just a bunch of constituent IDs. The output set elements control what data is output for that bunch of constituent IDs.
You can read up on adding output set element parameters in the System Tables document:
http://www.tessituranetwork.com/~/media/Documentation/System%20Administration/System_Tables.ashx
Look at the sections for both TR_QUERY_ELEMENT and TR_QUERY_ELEMENT_PARAMETER.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com
Heather Laidlaw Kraft SEATTLE REPERTORY THEATRE Please consider the environment before printing this e-mail
I asked a question about unwanted ticket lines in query output a while back and Sandra Ashby gave me a great tip; when you set up your composite query item use an unusual character as a break between each element, we use ~ and it means that when you save to Excel you can split the text to columns by this character. It works a treat and our member events co-ordinator was really pleased with the result.
It looks like this in practice (in case my explanation was rubbish)
Description: Ticket dt~Perf name~No seats
Data Select: cast(!.perf_dt as char (12)) + '~' + !.production + '~' + cast(!.tot_seats as char (3))