We have a couple of events coming up that our education department is putting on and for which they need some additional information from attendees. I have these set up as custom forms on TNEW tied into CSIs with an automated report sending daily. But I'm trying to figure out the best way to collect this info from anyone who calls to register. I figured out how to build out the custom data tab in the orders window, but I can't figure out how to get that info out, short of having to open each order. Has anyone used this tab to collect info in this way? Is there an easy way to pull a report with the results? Or should I instruct my phone team to create a CSI for any orders taken with the appropriate info?
Thanks!Anne
Yes, TR_QUERY_ELEMENT_GROUP. Sorry about that mistake in my original post!
Thanks, again! I got those set up, but now I have another question. I'm trying to use an output set to pull the custom fields out of an Attendance by Performance report that was saved as a list. Here's what my output set looks like:
I have a filter on the Ticket Performance Name to try to limit it to just the two events that these custom fields are going to be used on. But my results are giving me a line for every performance on the record (my own so there are quite a few from testing!) and nothing is showing up in the Tickets - Performance Name column. I know the red ! means that it can pull more than one row for each constituent, but is there anyway to filter it to just these two perfs and then make the perf names show? (I also realized that I should rename my custom output set elements to match what the actual fields say in the order window so the answers make more sense).
Now I'm off to see if I can figure out dropdown lists in the custom fields...wish me luck!
Here's what happened (and what I didn't think about at first when telling you how to set up the output elements for the custom order fields):
The Performance Name element is referencing a different table (or in this case, a view) than the table referenced by the custom fields elements your created. More specifically, the performance name element references a view of the ticket history table while the custom elements are referencing the T_ORDER table directly. More simply, they are in different output element groups, which means that the filter you applied to the performance name element doesn't apply to the custom order field elements. So you are going to get rows for all orders belonging to the constituents on your list for the custom order field elements, mixed with the ticket history rows that meet the performance name filter for the performance name element, resulting in undesired exponential inflation of your results. For of a more detailed explanation of how that works, go to the 2:40 mark of the Lesson 9 video on the Lists and Output course.
To accomplish your goal, you are going to need a new view of the ticket history data that includes performance name, custom order fields, and any other order data you might want to combine with those fields in your output and filtering. You would then create a new output element group that references that view, new output elements you put in that group for the different pieces of data you want to return from the view, and filters assigned to that group to limit the data you get returned. Code for how to create that view is a little outside of my area of expertise, and probably more appropriate for a consulting request (you could always open a help ticket and if its definitely a consulting issue the support staff will get you in contact with the right people). The Output Set Cookbook has some examples of creating views to use with custom output elements, so that might help you figure it out on your own. You could also take a look at the view used by the ticket history output elements (VS_ELEMENTS_TICKET_HISTORY) and use a copy of that as a basis of your own custom view that includes the custom order fields. One other place to consider seeking some advice is the Administration and IT forum, which has a broader viewership than this user group, and has many smart people who often swap code for things like this.
I hope that's somewhat helpful pointing you in the right direction.
Hi Kevin, That makes total sense. Thank you! I've been taking some SQL courses, so I can understand the issue and the need for a new view. I might try it on my own and if I can't figure it out I'll ask the Admin and IT group. That's a great idea. I didn't realize my request was going to be so involved and technical, but I'm always happy to learn more.