• Replies 4 replies
  • Subscribers 337 subscribers
  • Views 13 views
  • Users 0 members are here
Related

v12 Criteria missing

James Huynh
$organization

Hello Tessitura,

In our testing environment we've recently upgraded to v12.0.3 and have an ongoing issue with criterias missing (extractions, list manager, etc). We are going with the theory that the official name has been changed (eg. Ticket Package is now Ticket History Package), thus requiring it to be re-directed to resolve the issue.

If anyone has had a similar issue, help would be appreciated.


Thanks,
James

Parents
  • $organization

    James-

    Did you implement the v12 Standard Ticket History? If I remember correctly, there was an earlier version of this script that deleted "old" rows (referring to previous ticket history tables) in T_KEYWORD and TR_QUERY_ELEMENT, then it adds new rows for the new ticket history. The current version however does not delete - it just makes the "old" rows inactive. I think the script was updated in March sometime? We noticed the same when we upgraded our test environment in March, but have since done another live to test and used the new Ticket History scripts. Hope that helps you somewhat...

    Beth

  • $organization in reply to Beth Gilliland

    Hi Beth,

    I did go through the procedure of the v12 Standard Ticket History Implementation prior, and as you said in the post earlier, the old rows are inactive/not referenced. Do you know of a way to redirect or to have the criterion point to the newer entries?

  • $organization in reply to James Huynh

    James -

    We haven't gone live with v12 at UMS, so we haven't arrived at the point where we were worried about list building. Generally, we build new lists every year, so changing to the new criteria is not much of an issue here.

    Someone already on v12 might have more real-world experience with this, but I suppose you could use SQL to search in the criteria field for T_LIST to find lists using old tix/pkg history tables/views. You could then maybe update those criteria in T_LIST to point to the new tables/views, though you'd have to be aware of columns and whether they exist in both versions of the tables. But I would think that would only be a temporary fix until you could build new lists using new criteria, just to be safe. YRMV.

    Anyone else have this experience?

    Beth

  • $organization in reply to Beth Gilliland

    Hi Beth and James -

    I did two things:

    Pulled lists of people who had bad/old criteria in their lists (both ticket history and solicitation) and sent them notifications that they needed to fix/inactivate their lists.

    Changed the names of all the bad criteria (we put a 'Z ' in front of them) so people could easily see what not to use.

    I gave them a chance to fix it, and then, after a bit of time inactivated any lists that used the old criteria. Unfortunately, you can't do that with extractions (inactivate them) and I didn't want to delete them for historical purposes, so we had a couple of 'weird, we're not seeing as many people as we think we should' moments.

    - Heather

Reply
  • $organization in reply to Beth Gilliland

    Hi Beth and James -

    I did two things:

    Pulled lists of people who had bad/old criteria in their lists (both ticket history and solicitation) and sent them notifications that they needed to fix/inactivate their lists.

    Changed the names of all the bad criteria (we put a 'Z ' in front of them) so people could easily see what not to use.

    I gave them a chance to fix it, and then, after a bit of time inactivated any lists that used the old criteria. Unfortunately, you can't do that with extractions (inactivate them) and I didn't want to delete them for historical purposes, so we had a couple of 'weird, we're not seeing as many people as we think we should' moments.

    - Heather

Children
No Data