• Replies 13 replies
  • Subscribers 338 subscribers
  • Views 541 views
  • Users 0 members are here
Related

Couple of things about V14.1 I have discovered

Peter Smurlick (Past Member)
$organization

1. Constituencies:

If you have constituencies which never expire then check the end date is either NULL or 01/01/2999.  There is a bug in V12 or maybe earlier when using constituencies as part of the criteria in List Manager and Extractions.  This has been fixed in V14.  We went from 14,000 accounts with a given constituency to 3,000 because of the end date being 01/01/1900.  Once the end date was re-set all was well.  The SQL for this is easy enough.

2. The Performance Base Price and Availability Report

This report has been changed from Infomaker to SSRS.  The result users will not initially see the report.  You need to head into security and provide access to the report.

3. TR_QUERY_ELEMENT

Basically the issue is that with v14, the data_where column can't have keyword_no = at the beginning of the statement.  Items in the where need to be swaped around.  This is a sample of what had to be done:

select * from tr_query_element
where data_where like '%keyword%'

update tr_query_element
set data_where = 'key_value = ''Do Not Trade'' and keyword_no = 408'
where id = 407

I'm sure more surprises await.

Peter

Parents
  • Former Member
    Former Member $organization
    The biggest challenge I am having is output element and parameter migration.  I have gotten a couple of emails from Tessitura support didn’t make it any easier.  I spent hours on this problem.  Finally I sent the emails and the report off to my consultant and he scratched his head for a while.  He finally figured it out and will be documenting the corrections he had to make in TEST so it will be easier in LIVE.
     
    Jason Song
    Scottsdale Arts
    IT Manager
     
    T: 480-425-5340   C: 480-529-4653
     
Reply
  • Former Member
    Former Member $organization
    The biggest challenge I am having is output element and parameter migration.  I have gotten a couple of emails from Tessitura support didn’t make it any easier.  I spent hours on this problem.  Finally I sent the emails and the report off to my consultant and he scratched his head for a while.  He finally figured it out and will be documenting the corrections he had to make in TEST so it will be easier in LIVE.
     
    Jason Song
    Scottsdale Arts
    IT Manager
     
    T: 480-425-5340   C: 480-529-4653
     
Children
  • $organization in reply to Former Member

    It was a very difficult decision for us about how to migrate list elements and output set elements.  We knew that we needed to change a lot of the way we were storing data particularly for output set elements, due to the new functionality that we wanted to provide--namely the runtime output set filters.  We knew up front that we were not going to be able to successfully convert everyone's output set elements because of the wide open flexibility that they provided.  We debated whether to not migrate any of them at all, script an entire new set of standard output set elements, and then have everyone re-enter their own custom ones.  Ultimately we decided that we could programmatically convert a large percentage of all output set elements and leave the rest for people to fix or re-enter.  Somewhat understandably this has created some question about which could be easily migrated and which couldn't and why we changed the format at all.  In the end I think the new functionality is well worth the effort involved in upgrading, but I think it's important for members to know that we never take these decisions lightly.