Hi friends,
I'm working on getting rollover sets built for our 23-24 season. We have two venues, and in years past, have allowed patrons to subscribe to shows in only one of the venues. We are sunsetting this, and would like to roll those subscribers into a full season package. When building the rollover sets, would it work to have the source list set to pull from the existing full-season subpackage as first priority, and then the single venue package as second priority, into the same target subpackage? This is what I'm thinking: For our purposes, SUBCP is the subpackage of our full-season super package, and the plain CP is the single venue package. I'm not concerned about overlapping seating issues because they are the same facility, and I believe the single venue folks should then also have unseated line items in the other facility. I'm on a bit of a time crunch to get our rollover done this year and would rather not have to wait for our live-to-test refresh to figure out if this will work as I think it should. Thanks for any insight.
We have done this kind of thing in the past and this should work, however, I strongly suggest that you do a few in your test environment first as it can be a pain to unroll sets.
Thanks, Amber. I will definitely be running everything in test, but I'm hoping to avoid multiple rounds of testing if at all possible.
An update, for anyone who comes across this that might be interested in the final product: it worked in our test environment. In order to create the unseated line items in the second facility, there must be a default price type set in your MOS, and any price types you use must be added at the package level (as well as the performance level), which can be done in season manager. If you don't do this, it will only create half of your super package, and then if you try to open the rollover order, it will give you several errors. Ultimately, the order still opens, but if you try to add seats in your second facility, you end up with extraneous subline items in the first facility and an out of balance order. The default price type element of this is discussed in the special rollover scenarios section of the knowledgebase, but it is out of date. It advises you to do this in a system table (which is not available in the client according to my SA), but you can do it in Ticketing Setup > MOS > MOS/Price Types. It does not mention adding the price types at the package level in season manager, I don't think I've ever had to do that before, but this is only my second rollover