It would appear that a lot of merges that fail to be scheduled are kicked out by the system for being previously merged IDs. But obviously, there's a chance that a record, merged or not, could be created for a customer needlessly. How do we get the system to accept these merged records - provided, of course, that the current ID to be kept is the one kept from a previous merge.
Thanks, Tessiturians.
BONUS NON-MERGED TRIVIA: Friggatriskaidekaphobia is the irrational fear of the most ominous day of the year, Friday the thirteenth.
Matt
If the ID has been previously merged it really doesn’t exist anymore (it is a ghost). If you type the ID # in the search screen you will be given the new primary or Kept ID number. If this ID still needs to be merged with yet another record if can be merged.
When setting up merges if an ID has already been merged then the system will return an error message that the ID no longer exists. So the error is often avoided this way.
I’ve also found that a check that duplicate requests for the same merge are not made. If this happens the system bounces both/all the requests.
At least this what I’ve found to happen with the program
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matt Gonzales Sent: Monday, October 26, 2009 5:37 PM To: McKinley, Leslie Subject: [Tessitura Technical Forum] Merging Previously Merged IDs
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!
One other part of the process – the other trick is pick the Keep ID and merge ALL the items into it. I think the message you are getting happens when the user tries to “build” a merge within the same program run. Merging A into B into C into the keep ID of D. All of the items should just be merged into D.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Leslie McKinley Sent: Monday, October 26, 2009 5:47 PM To: McKinley, Leslie Subject: RE: [Tessitura Technical Forum] Merging Previously Merged IDs
In this case, as in most cases. This is an ID ("A") that was merged into another ID ("B"). Subsequently, a new ID ("C") was inadvertently created and needs to be merged into B from the previous merge. One would assume, I think, that the process would treat B as if this were the first time it was ever merged for the purposes of merging two distinct records (B and C). I recognize that A, having been previously merged into B, is inactive and unalterable. But I'm talking about merging a new extraneous ID (C) into the original kept ID, B. Seems like it should work just fine.
It should work, unless there is some criteria in your validate merge procedure that causes B to be bumped from merge in general, or if changes were made to B after being scheduled for merge with C, or if at the same time B is scheduled to merge with C it is also scheduled to merge with D. Any of those scenarios would make it bump. Based on the message you reported seeing, I would guess that you may be experiencing the third situation.
Matt GonzalesDatabase Administrator | Houston Grand Operamgonzales@houstongrandopera.org
From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>Sent: 10/26/2009 5:44:31 PM