Merged Records Missing from Extractions

Rog

That just means, as Ken pointed out earlier, that your merge procedure is not including your ticket history table (and probably package history table) as part of the process.

Essentially the ticket history data is keeping the old customer number and is not being updated to reflect the new customer number.

You will need to have LP_CONST_MERGE updated to include these tables. But for those accounts that have already been merged they will need to be updated separately via the database to the new account number, then they will show in the ticket history under the customer’s account.

Cheers

Sandra

From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Rog Hildreth
Sent: Friday, 2 August 2013 10:14 PM
To: Sandra Ashby
Subject: Re: [Tessitura Marketing Forum] Merged Records Missing from Extractions

I'm having the same problem, but we don't currently have someone able to write this kind of code. 

I've also found that, having moved to Tessitura from ProVenue in November and transported old ticketing histories as "legacy data", extractions are finding the old ID numbers of merged constituents based on this legacy data, but mostly the legacy events no longer appear in the ticketing history of their new merged files. So the legacy stuff is in there somewhere, but does merging make it disappear?

Hi Andrea

If you've localised your Ticket History table (almost everyone does), you need to add some code into the localised merge script (LP_CONST_MERGE)  to make it merge your local ticket history details as well. Otherwise the ticket history won't move across to the Keep record, which sounds like what you've got here.

Same goes if you create any local tables to hold custom constituent data. You need to add them into the LP_CONST_MERGE script so they merge correctly.

That's an SQL task, obviously, so you need to get your friendly local SQL guru to do it - or a Tess consultant if you haven't got your very own.

You'll also need to get them to merge the records that were missed in your merges so far. That's not hard, but it's definitely a back-end task.

A couple of things that might help them - 

1   There is a script on my page here which returns the current customer_no for any constituent record, so you can identify which constituent to merge records into.

2    This is the section of our LP_CUST_MERGE script which does the task::

/*****************************************************/

/*********** AFTER-MERGE RULES *************/

/**********************************************/

/********** Handle Local tables   ********************/

/* Step A1 update subs history table */

If @merge_stage = 'A'

  Begin

UPDATEdbo.LT_SUB_HIST set customer_no = @kept_id where customer_no = @deleted_id

 If @@error <> 0 

  Begin

select @err_table = 'LT_SUB_HIST (post_merge)'

goto GiveErrMsg

  End

   End

/* Step A2 update ticket history table */

If @merge_stage = 'A'

  Begin

UPDATEdbo.LT_TKT_HIST set customer_no = @kept_id where customer_no = @deleted_id

 If @@error <> 0 

  Begin

select @err_table = 'LT_TKT_HIST (post_merge)'

goto GiveErrMsg

  End

   End

-----

Ken

We've recently begun a massive database cleaning, including merging duplicate accounts. However, when pulling a list based on ticket history, it appears that if I suppress Merged/Inactive records, my extraction no longer picks up patrons with the designated ticket history if they have been merged with another account. Their ticket history now appears in their merged record, but I can't seem to pull them into an extraction based on that history. If I don't suppress Inactive/Merged records, the extraction pulls their inactive account. Has anyone else seen this? Am I missing something in my extraction build? Any suggestions?

Thanks!
Andrea Akin

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing 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!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing 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!