• Replies 19 replies
  • Subscribers 337 subscribers
  • Views 168 views
  • Users 0 members are here
Related

Merge Procedure Advice?

Beth Hawryluk
$organization

Hi all,

We've always had a good number of failed merges each week due to the good ole "activity happened on the kept account" error. Sometimes I can see that something physically happened and so the error is legitimate (not that I always agree with it failing the merge because of that... but that's a different story). I also noticed a while ago that the LP_CUSTOMER_RANK was causing a lot of unwanted activity. Since we don't currently use ranking I disabled it which kind of helped.

But I find myself looking into this issue again as we've still been having a crazy number of merges failing each week and most of them are consistently the same people. This is what I've found and I'm looking for some advice on what other people have done.

The majority of the failures seem to be happening because of our nightly Manage Constituency updates. It's funny because most of these people have had the constituency for several months and the last_update_dt in TX_CONST_CUST is from several months ago. But their last_update_dt in T_CUSTOMER is for the exact time of the last constituency update run. How have other people gotten around this? Should I stop using the Manage Constituencies report and write up LPs to apply constituencies that don't modify the account unnecessarily?

This also leads me to wonder how I'll handle the ranking procedure and merges when we start using ranking in the future...

Thanks for any advice!

Parents
  • $organization

    Hi Beth,

     

    I looked at the code behind the Manage Constituency job, and you are correct – it is updating t_customer.last_activity_dt for all constituents in the specified list, even if it didn’t actually change anything. I would suggest opening a ticket with Tessitura on that, as that date really shouldn’t be updated when no activity actually occurred (in my opinion).

     

    You may also be able to refine your list criteria. I’m not sure what your Manage Constituency job(s) are doing, but I assume some are an action of Add to List. I think you could filter out constituents that already have the constituency you are trying to add, thus preventing the procedure from touching the last_activity_dt unnecessarily.

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Thursday, October 23, 2014 11:57 AM
    To: David Frederick
    Subject: Re: [Tessitura Technical Forum] Merge Procedure Advice?

     

    Hi David,

    Yes, the Manage Constituencies utility seems to be updating t_customer.last_activity_dt even if no changes were made to that particular account. I'm assuming simply because it needed to access the constituent record? I'm not really sure.

    Thanks! Beth

    From: David Frederick <bounce-davidfrederick9045@tessituranetwork.com>
    Sent: 10/23/2014 2:22:50 PM

    Hi Beth,

    The merge process looks at t_customer.last_activity_dt to determine if there has been activity since the last merge. It compares that against t_potential_dups.last_update_dt.

    Is there anything you are doing in your nightly jobs that is updating t_customer.last_activity_dt?

    Thanks,
    David




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • $organization

    Hi Beth,

     

    I looked at the code behind the Manage Constituency job, and you are correct – it is updating t_customer.last_activity_dt for all constituents in the specified list, even if it didn’t actually change anything. I would suggest opening a ticket with Tessitura on that, as that date really shouldn’t be updated when no activity actually occurred (in my opinion).

     

    You may also be able to refine your list criteria. I’m not sure what your Manage Constituency job(s) are doing, but I assume some are an action of Add to List. I think you could filter out constituents that already have the constituency you are trying to add, thus preventing the procedure from touching the last_activity_dt unnecessarily.

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Thursday, October 23, 2014 11:57 AM
    To: David Frederick
    Subject: Re: [Tessitura Technical Forum] Merge Procedure Advice?

     

    Hi David,

    Yes, the Manage Constituencies utility seems to be updating t_customer.last_activity_dt even if no changes were made to that particular account. I'm assuming simply because it needed to access the constituent record? I'm not really sure.

    Thanks! Beth

    From: David Frederick <bounce-davidfrederick9045@tessituranetwork.com>
    Sent: 10/23/2014 2:22:50 PM

    Hi Beth,

    The merge process looks at t_customer.last_activity_dt to determine if there has been activity since the last merge. It compares that against t_potential_dups.last_update_dt.

    Is there anything you are doing in your nightly jobs that is updating t_customer.last_activity_dt?

    Thanks,
    David




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
No Data