I don't think I see this in the Seats and Tickets Cube definitions, but is it possible to report on the date a performance was created in the database?I'm looking to create a widget that shows the number of performances that have been set up in the last two weeks, and was all set to use the time-based filters for that... But I don't see whether grabbing that data is immediately possible, unless anyone knows of a clever workaround?Happy Monday, folks!C.//X.
Hi Chris,
Performance Create Date is not a standard field in Tessitura Analytics. I'm curious to learn more about your need for it in the context of auditing that past 2 weeks of performance setup, and more generally other than this one time, is this a regular need? It's the first I've heard. It could certainly be added as a custom, performance level field in Analytics if this is a frequent need. Or if this is a one time thing, someone can probably help with a SQL query.
Not sure about Chris Campbell's needs, but we have sometimes tried to do internal reporting on how long it takes from the start of a build to the on-sale date. This helps not only evaluate our own efficiency but also can help us to inform rental clients the expected time from the receipt of their packet of materials to on-sale, and things like that.
Just throwing my own experience here.
Yes, we too have the annual question "how much lead time do we need for build?" Thankfully we have an excel doc that we work off of and initial as we build. So I was able to use the edit times of those fields to figure it out.
Good question! Well, our specific need for this is that the number of performances in a given financial year is now a key performance indicator for us. We're having a fortnightly meeting to review those KPIs, and I'd like to see the movement between meetings. It's not a biggie, I don't think, but when all other KPIs have a net movement widget (ticket sales, occupancy %) etc., I'd love to see that reflected here also.Additionally, I do support John A. Moskal II's observation that it's useful to understand the pipeline of work internally, especially as it relates to the pressure put on key members of staff! Handy to report that to Exec level, I think.I could surely do a SQL query, and I may do that on a fortnightly basis. Or I could just live without it. Hmmm; decisions, decisions. It's good to know my understanding of what was possible was correct, though!C.//X.