Hi everyone!
I'm reposting this from the Ticketing forums, in case any of you Admin/ IT wizards have a work around!
We have two performances that went on sale earlier this year for single ticket sales. However, they are also part of a package for next season. Our typical business practice is to not seat subscription renewal requests or new subscriptions until after the renewal period is over. However, this one performance SHOULD be seated because it is technically on sale for single ticket buyers and we don't want all the seats to be sold from under renewing and new subscribers. Currently, if you try and seat one performance in a package, you can an error message asking if you want to remove the unseated line items (which we obviously don't).
Is there any way around this? We could probably exchange the performance out and then into itself, but i figured I'd ask if there was a more direct route. We are RAMP hosted, and I currently am learning SQL, so I wouldn't be able to access anything that way (without worrying about breaking the entire database )
Any advice is appreciated!
Just an update, if anyone is curious. If we go the exchange route, we need to seat the entire package in order to be able to return/ exchange the individual performance. However, once the performance is exchanged, I then cannot unseat the package so that the remaining performances are still unseated.
Super fun!