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
We are implementing next month with some of our education data being entered into the Custom Data tab in the order. Unfortunately, I don't have access to SQL to show you exactly how that info is getting pulled into a report, but I know that we will be able to pull it. All of the education reports I'll be launching with are custom reports, but I'm sure there's got to be some established way to access the data in that tab. I've attached a snippet of our custom data screen in the hopes it might help in some way. I'll see if I can find out more for you!
Thanks, Justin! I was able to get that far (although I didn't get a dropdown list figured out because I wanted to see if I could get the data out first). It's the pulling the info out that I'm stuck on. If it is going to mean another custom report, then we'll probably just do it with a CSI since we don't expect many phone orders for these. The documentation says that the data can be printed on tickets and acknowledgements, so there's somewhere in the system that can access the info. Unfortunately, these fields aren't available as elements in output sets, because that would be an easy solution.
Maybe look at Analytics. I see all the Custom fields are available on the orders object.
We use the Custom Data tab alot in Contributions. All of our gift memberships and Sponsor an Animal orders and Annual Appeals orders are taken in Contributions and use those fields for additional information. We pull the information using reports from List Manager. Some of the fields had to added to be used in the output.
I finally figured out how to make the custom fields show up in List Manager. But they are there as criteria. Really I just need to search for orders for specific performances and then pull out the data in the custom fields. I won't have something to search on. Now if I can just figure out how to get these fields into output set manager.
That and to figure out the dropdown lists...that one has me stumped.
Try the output set cookbook.
https://www.tessituranetwork.com/en/Files/Docs/Customizations/Output-Set-Manager-Cookbook
And this video that goes with it.
https://www.tessituranetwork.com/en/Items/Videos/Training/Extending_Output_Sets
--Tom
P.S. I think when I learned this I looked at the previous version
https://www.tessituranetwork.com/en/Items/Videos/Training/Output_set_custom_element_groups
Thanks, Tom! I knew you were a wealth of information on Analytics, I should have known you'd be a true Tessitura Renaissance man!
Hi Anne,
Those are great resources that Tom pointed you to for learning how to set up custom output elements. I just wanted to note that the custom order elements aren't examples that are explicitly included in the cookbook. For a custom order field output element, here are the key pieces you'll need:
Add a new group to TR_QUERY_ELEMENT group that points to T_ORDER (Data From column).
Add a row for each custom order field to TR_QUERY_ELEMENT that are assigned to the output element group you added, and with the Data Select column set to the column that corresponds to each custom order field (e.g. !.custom_1 for custom field 1).
-Kevin
Thanks, Kevin! I had noticed that the cookbook didn't have them (maybe they should be in there! hint! hint! :-) ). Those extra pieces of info are very helpful. I'm waiting on a Live to Test copy over night and then I'm going to get started tomorrow.
Anne
Just to clarify, Kevin Sheehan -- I first need to add a group to TR_QUERY_ELEMENT_GROUP, right? (not TR_QUERY_ELEMENT)
Yes, TR_QUERY_ELEMENT_GROUP. Sorry about that mistake in my original post!