Hi everyone,
We're looking for a place to store ticket count goals, similar to how you can use budget amount to track towards revenue goals, where it will then pull into Analytics.
I know this topic has come up before, and in fact, there's an idea for it on the Ideas board: https://community.tessituranetwork.com/ideas/i/ideas/additional-ticketing-goals-in-tessitura-in-analytics
Until that idea becomes a reality, have others found workarounds for pulling additional goal numbers into Analytics? In the past I've hard-coded the ticket count goal into a formula, but that's not ideal when wanting to switch between multiple productions or product lines.
Thanks!Christine
I've looked through the cubes multiple times and I can't think of anything. Best option for multiple Prod/Perfs is a rather labourious CASE statement that you can keep adding to.
Hello, We've really struggled with this too. We have landed on have specific ticket count tracking dashboards that are a little less interactive where each widget is filtered to a different PROD season so that we can use CASE statements to have the individual daily targets in for each. If you do decide to go down that road just a warning that each widget will tap out after a certain number of CASE statements. We had a support case open and Tess helped confirm that it will only take 100 in one widget. So for us this means we go in every 100 days or so and wipe of the past daily targets so we can update it to show the next ones which are upcoming. It works fairly well for us!
But yes please up vote the idea on the ideas board :) I recently chaired an EU Museums and Attractions event where there was a resounding consensus that everyone wanted a non-financial budget field at each level of the perf hierarchy so hopefully this will be coming soon.
This is really helpful to know there is a limitation with the CASE statements! Especially as that probably is going to have to be the workaround until other goals fields come about.