Re-Numbering Seats In Facility

Hi Kevin,

Thanks again for your info! Just an update - I updated the numbering of this facility in our TEST environment, and it did update the seat map for existing performances. I did not run any facility updates to my knowledge, but did save the seat map changes. Do you know why this might have happened? 

Thanks again for your help.

Kim

Unknown said:

Thanks again for your info! Just an update - I updated the numbering of this facility in our TEST environment, and it did update the seat map for existing performances. I did not run any facility updates to my knowledge, but did save the seat map changes. Do you know why this might have happened? 

Just following on from this, as we are seeing the same behaviour in our TEST environment...

Have there been any updates as we would also like to re-number a facility that is currently in use without it impacting existing performances.

Thanks!

Tom

Working on the exact same project and will be starting the renumbering project in two weeks. 

We were under the impression that a couple of scripts would have to be run for the changes to take place as well.

If this isn't the case it would be good to know before this project gets underway.  

We ran into the same issue here in Santa Barbara.  We updated the seat numbers and rows on a facility in test, and before we noticed that the changes had been affected already we requested our Database Manager to run the SQL scripts against specific seasons.

When we noticed that all seasons and events using that facility had been affected we opened a support ticket.  It was suggested to be a one-time error at the time.  Thankfully we have two test sites (Test and DEV) and tried the updates once again, but before requesting the scripts to be executed we noticed that once again all seasons/events using the facility in question had been affected.

The last note on our support ticket (Issue=59723) indicated that support was unable to recreate the issue.  We made the change in live and sure enough, the changes were reflected immediately.

At this stage, it's likely a bug that needs to be reported.  I too would suggest opening a support ticket for those who have encountered the problem.

Logan, I would suggest making your changes in your test environment first to see if the same thing is going to happen to your facility.

As an update on our project, we were not able to get this to work properly on our end. It updated all the seats in our current productions (in our test environment), and we couldn't get around that. We worked with Tessitura support and could not come to a fix for this. 

We instead built a new facility with the intention of using a data export and import for our subscription roll. We had issues with that as well and had been communicating with Tessitura through support tickets the entire time. Unfortunately, we ran out of time to implement these changes for the next year, and instead will revisit it for the following year.

We worked in the test environment for the majority of this, so as to not effect any of our current productions. I would highly suggest working this through in your test environment before moving forward to implementing it in production. 

If anyone has successfully made this work, it would be great to know!

I took a look at the help tickets Kim and Christopher both opened and it looks like making changes to the seat row and number assignments are applied automatically to all performances using that facility without running the update scripts, at least in all the places that matter.  So it is not possible to make changes to the seat row and number assignments an only affect new performances. The current documentation is incorrect here and will be updated.

It's worth noting, though, that if you do make seat row or number changes to a facility, you should still run the update procedures as they will update some of those other, less important places that don't get updated automatically so they are in sync with the active facility data. 

-Kevin

I took a look at the help tickets Kim and Christopher both opened and it looks like making changes to the seat row and number assignments are applied automatically to all performances using that facility without running the update scripts, at least in all the places that matter.  So it is not possible to make changes to the seat row and number assignments an only affect new performances. The current documentation is incorrect here and will be updated.

It's worth noting, though, that if you do make seat row or number changes to a facility, you should still run the update procedures as they will update some of those other, less important places that don't get updated automatically so they are in sync with the active facility data. 

-Kevin

Thank you for following up, Kevin. 

It potentially saves me a big headache. 


Chris, I will definitely be going forward in Test. We have an overlap period between the 14/15 concerts and the 15/16 subscription seating process so more than likely we're going to have to change the Hall and have it affect the current season's seat maps. Unless a work around is found.