Hi all!
I built a few performances under the wrong Title in Production Elements. I really don't want to build them again under the correct one - they were kind of a pain the first time!
I noticed there is a prod_season_no value in T_PERF. Does anyone know if it will break things if I simply update that with the prod_season_no that I want? Or is there a better way to move perfs?
Thanks!
So, I'd like to open up a very old thread. We have a situation where we don't know what production season a performance will be some time in the future.
We just know that at 4:15pm every day, in the Planetarium we will have a show. We would like to add this performance to the system now. Even sell the performance to hundreds of students for 6 months from now. Then when we have the "show title" AND a production season for the show, move this performances and others into an appropriate production season later. This would not be an emergency fix. But a regular part of our business process.
I see the change that can be made in t_perf. (That looks easy enough.) I see the note about checking t_imp_perf_data. (OK)
Is anyone out there doing this on a regular basis?
If so are there other things I should be thinking about.
Hi, Tom!
We are not doing it on a regular basis, on the other hand, it has happened often enough that I wrote out a list of what things needed to be accomplished and in what order. Our Finance staff has also decided that the season into which things were placed sometimes needed to change after the fact, too, which led to more things being updated.
If the season can be decided upon beforehand, and, from what you say there, it sounds like it could, then that does make it at least a little easier. Either way, you are also going to have to consider the ticket history, too, if you have any desire to do reporting on these performances off of lists that are pulled (plus it is just generally good practice to have all the data be correct).
If you are interested I can send you the documents I put together. I always try to make things as universal as I can when I put them together since we are a presenting organization which is also the primary on a consortium with six resident companies, so this SHOULD translate pretty well (we use the standard ticket history procedures), but I would of course highly encourage you to look it over first to make sure that there is nothing unique to our organization in there. Just let me know.
John