point upgrade from 15.0.x to 15.1.x

Hi everyone,

We're going to be doing our upgrade from 15.0.3 to the latest version of 15.1 this month, and I was wondering if there are any 'gotchas' we should be on the lookout for?  I would assume there's minimal technical issues as it's not a major release, but, well, assumptions are bad!  

Thanks,
Kathleen

Parents
  • 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!

Reply
  • 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!

Children
No Data