I'm guessing the answer is no and I've looked in both v15 and v16, but is there anyway to pull the answers to custom forms on TNEW into Analytics? CSI reports aren't the most user friendly for looking a the responses from teacher workshop attendees as a group (even when saved as a CSV). I was hoping I could set up a pivot table with the info. Something like this:
But obviously the custom order fields I chose aren't giving me what I need. Is it possible to assign the custom fields to custom form questions?
Anne
My answer is "Yes, but" depending on if your firm field data is in CSIs or a local table. The problem for me is the CSI string. Though doable it would be easier to take the form data into a local table via a sproc and then use those fields columns to create your custom categories.
Just a though before bed
Cannot support this idea more. It would seem like there would have to be SOME way to set up a standard/out-of-the-box Tessitura way of standardizing the saving of custom form data in a way that can be reported on clearer than a giant CSI string output. I am not saying that things like Origin, Activity Type and such are not important, but the data itself is much MORE important, especially when most of this information is happening online in the first place. The data points entered, and the two key points: the customer and performance/package to which they are connected. Whether a simple yes/no as to whether someone needs a loaner instrument for lessons, or a complex form with things like dietary restrictions and accessibility needs, it seems like there would be a way to create a standard data table that can save this information and then return it to a patron tab.
I think the term "custom" here may have outlived its usefulness. Sure, this data is "custom" in that it is unique to the performance/package, but it is hardly "custom" in the way that my organization's pre-cart pages are "custom" as compared to the pre-cart pages of any other organization. We are ALL seemingly using these form fields. So, let us think of it not as "custom save data" but instead as "form data", and I think that will help us to formulate a better notion of saving and displaying that information.
In V16, with its web construction, it really seems like this should not be an overly taxing tab to create. Just spitballing here, similar to what I have done for our own organization, create a form data table that has columns for customer_no, perf_no, pkg_no, data_type, column_desc and then column_value. Then you just return that information in some general form of table based on which customer is selected on the tab (or performance/package in an SSRS report), and it would seem like it would not be too challenging to make that editable either for patron services associates to add/delete/update as needed either. While I am off in my own world creating Tessitura functionality here, I would also suggest moving this newly-titled "Form Data" section out of system tables and instead make it its own thing like Pricing Rules.
That got away from me a little there. But I support Heath Wilder here.
John A. Moskal II
And my axe! ... (Sorry I might be in the wrong film)
I do have a CTE report to split those strings but it's so much better with a local table. And stored procedure.
You could do it easy with WordFly surveys
I was literally just talking to a coworker 30 seconds ago about Lord of the Rings. Way to be!