We've had a weird issue come up with our batch ticket printing sets: suddenly a large number of them have become inactive.
www.tessituranetwork.com/.../Batch Ticket Printing.htm
There is a "Active Only" checkbox at the bottom of the listing of sets (unmentioned or shown in the documentation), but otherwise I see no mechanism to inactivate a set or difference in any parameter between the active an inactive sets. Does anyone know what might be going on, and how to control if a printing set is active?
Thanks,
Gawain
I believe this relates to the status of the seasons selected for the set.
I'm not seeing a connection between the active and inactive sets and their seasons: many are set to current seasons and still inactive.
Okay, this actually came up with us a few weeks ago, and I didn't look into it more closely then, but I did just now. As best I can tell: the datawindow filters "current only" based on the 'season' column in T_AU_SET_MASTER. If the value is -1, or if it matches an active season, it will pass the filter. Anything else is not considered "current".
The problem with that is that I can't figure out what T_AU_SET_MASTER.season is supposed to mean -- any new batch print sets I create are always assigned -1. My hunch is that the column is at least partially obsolete, since now there's a season_str column in the same table. It's also only the older rows from the table that have a positive integer value.
Did we perhaps see that between 12.1 and 12.5, season went from being single-select to multi-select, but the datawindow filter wasn't updated to match? I think this is a bug; feel free to do the TASK honors.
P.S. I'd be comfortable updating the season value to -1 if I had existing sets I wanted to maintain as current.
I think we would have noticed if it was a 12.1 to 12.5 change. I also assume we would have noticed if it was a 12.5 to 14 change, since that happened over a month ago now, but maybe not.
Anyway, TASK ticket already filed: if nothing else it's missing some documentation.
Okay, this appears to be exactly the issue. I changed the season column and all the sets started behaving appropriately. A note: you make a change that would change the inactive/active status of a set, you have to close and re-open Batch Ticket Printing to see that change reflected in the selection pane.