point upgrade from 15.0.x to 15.1.x

We went from 15.0.4 to 15.1.4.  We are on RAMP.  It went surprisingly smoothly.  The majority of our problems turned out to be the fact we were testing on our development environment and there were still some things that were not up to date and setup in our DEV environment. 

• There are some changes in the way that Merges are working that have caused problems with Web Guest Login Merges.
• There is a Change in Tessitura Analytics where the unit of analysis went from the Seat/Ticket to the Pricing Layer.  Depending on how you set up some of your ticketing analytic boards you may have to go back and rework your analysis boards.

Agreement from us. Just to add i had a few hold code and sales dashboards in Analytics that required rework now that sold holds are counted (incremental and full loads). 

We just completed this upgrade last month, and from the database perspective I found it to be pretty involved. It obviously depends on how many customizations you have, but the change from FS_USER() to FS_USERNAME() meant that I had to update almost every custom table and related update trigger, as well as any procs that also relied on that function.

Other changes, like introducing TR_GENDER & TR_BATCH_PERIOD's org column, and other features that our Consortium has found our own workarounds for over the last 13 years, were definitely nice features but also required some changes and thorough testing. 

From the end user's standpoint, though, I don't believe there were enough major shifts for them to appreciate how much prep work I was doing on the backend, but such is the life. ;)

Happy upgrading!

Also, I think Intrepid is on TNEW (correct me if I am wrong), so this should not be a big worry for you, but if you have your own cart and processing at some point outside of TNEW (like we do for donations), there is at least one change to a cart datatype that might snag you (like it did for us when we installed the 15.1.5 service pack).  But if you are 100% TNEW, then never mind.

John A. Moskal II we are not on TNEW and have a custom website - could you elaborate? We are set to start our upgrade project next week.

I will be honest, I do not do the the primary web coding for our website (though I do some of it).  So in this particular instance, since it was one of the more complex things involving transactional data, I do not have all the details, as our web developers took care of this change.  Here is what they told me at the time:  "Tessitura changed a datatype in the shopping cart which broke the contract between our code and their API. We’ve updated our code to comply with this and [it is working again]".

We were going from 15.1.1 to 15.1.5 at the time.  I will see if I can find out more from them.  Sorry if that is not extremely helpful.

How about that, I got a quick response.

Okay, so here is what I got back when asking about what calls/datatypes were affected in this change:  "Any call related to getting cart details (GetCart, GetCartBrief, GetOrderDetails) failed due to the Contribution table of the returned dataset changing its ‘db_status’ property from a 16bit to a 32bit integer (‘short’ to ‘int’)."

Looks like this is SOAP API stuff only, and our developers promised that these issues would lessen once we were fully on REST, so depending upon where you are in that transition might tell the tale of how this does or does not impact you.  But it does sound like it is an easy enough fix if you know to look for it.

Thanks so much, John. I've passed this along to our developers!