With Tessitura V15.0.4 we are having problems with holds showing up as none in a pivot table.
We can use it as a filter type?
I've got to imagine that either this is the way these are set up in the eCubes
OR
I'm doing something wrong.
Any ideas?
Booked holds or unbooked? I use the latter for filters and columns in various tables where i need to know what's held but unbooked. The former (booked holds) is that age old Tessitura problem that I've only ever solved by downloading the Hold code report as Excel and pivoting the thing.
Non-Booked Holds. We have a practice of holding a few seats in the seat map that are not blacked out. Don't want to count them as inventory in some cases.
Hi Tom ... here's a dashboard with 3 widgets in a variety of complexities of Hold Code usage. I get results for all but you can have a look at these and see if they work for you with a modification.
.7612.forTomholds.dash
One thing I found out from RAMP Support was that hold codes normally only refresh with your full load and not with incremental loads since there isn't a history table for them. If you just added the holds and haven't had another full load of Analytics, that could be the problem too. In that case, I'd recommend putting in a Support ticket as there are workarounds that can be implemented.
What version of Tessitura are you using? I'm o n 15.0.4
Thanks, Heath Wilder,
Unfortunately, your dashboard produces no results what so ever. Even when I correct for hold codes. What version of Dashboards are you on?
I'm opening a Support Ticket. Anyone else having this problem? Anyone know when and under what version this problem might be fixed?
15.0.2
We're on 15.1.0
Heath Wilder if I remember correctly you are local hosted. But minimally you are on a different RAMP architecture in Australia. Was anything done to make your seats & tickets eCube loads any more reliable? If so what can you share?
Nothing in particular. We had an issue with Price Categories and not showing up (an occasionally being replaced by israeli towns) after incremental loads that the RAMP team did a bit of fiddling with. That issue still happens from time to time but nit with the regularity that it did. I'm pretty sure our hold code charts remained consistent throughout.