Does anyone know of a report or counter in Tessitura that can be used to record the number of constituent merges done over a certain period? We are beginning to tackle our rather daunting merge list and thought it might be more bearable if we could track the amount of completed merges to indicate some sort of progress! Any insight would be appreciated.
Thanks in advance and I'm looking forward to DC!
Hi Mary -
There's a report called Duplicate Merge Report in the Data Management folder. You might need permission to get it. It allows you to see successful/failed merges for a date range. It will print a list of each merge, but if you go to the last page of the report it will show you the total.
Good luck!
HeatherSeattle Rep
This is exactly what I was looking for, thanks Heather!
Unknown said: Does anyone know of a report or counter in Tessitura that can be used to record the number of constituent merges done over a certain period?
Does anyone know of a report or counter in Tessitura that can be used to record the number of constituent merges done over a certain period?
If you'd like counts per day over a range of dates and are or have access to someone that's comfortable with SQL, you could run something like this, too:
select convert(varchar(8), merge_dt, 112) "short_merge_dt", count(*) "count" from t_merged where status = 'S' and merge_dt between '07/01/2010' and '07/16/2010' group by convert(varchar(8), merge_dt, 112) order by short_merge_dt
Yep. In Shared Reports. I think it’s called Constituent Merge Suite or something similar.
+Ryan Creps
+Tessitura Network
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Amanda FreemanSent: Wednesday, November 30, 2011 2:32 PMTo: Ryan CrepsSubject: Re: [Tessitura Ticketing Forum] Merging Constituents
I think her dupe scripts might even be in the shared reports...
From: Chris Jensen <bounce-chrisjensen8841@tessituranetwork.com>Sent: 11/30/2011 1:20:35 PM
Andrew Moreau:[...] Is there a way to flag the accounts that are not actually duplicates so that on the next scheduled duplicate search, they are not listed again?
Andrew Moreau:
[...] Is there a way to flag the accounts that are not actually duplicates so that on the next scheduled duplicate search, they are not listed again?
Community member Katie Lachance-Duffy has shared her own custom dupe scripts that include the ability to flag non-dupes and eliminate them from future potential dupes. I've incorporated this idea with our custom code here, and found it to be invaluable. I bet if you drop her an e-mail she'd share, as she did with me.
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
By default, the procedure that identifies duplicates does not relist a pair that was previously identified but not scheduled for merging, unless one of the pair has had activity since the last time the procedure ran. You can specify the activity date window with an optional parameter on the procedure. For full details see the Managing Duplicate Constituent Records document.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
No virus found in this message.Checked by AVG - www.avg.comVersion: 2012.0.1873 / Virus Database: 2102/4648 - Release Date: 11/30/11