Hi all -
We just moved over into V15 - and we're working through some new features. We received this error for the first time "Constituents Can Only Be Scheduled Once for a Single Merge." We've never encountered this before in other versions. We've done our due diligence and read about merging in V15 - but can't figure out how to merge Account Numbers 2 and 3 into 1 during the same merge procedure. Any ideas where we are going wrong?
Also, is anyone using any jobs for merges overnight that they really like? We've been doing it manually for awhile now. I've worked for other organizations that had jobs that ran overnight that looked for potential duplicates, and I'm looking into possibilities of implementing this here.
Thank you!
Hey Rachael,
This is new functionality. I don't think anyone was aware that the merge process was going to be changed in this manner. Sadly, you can only schedule one merge at a time. You will have to do something like setup an Outlook reminder for the next day to do the next merge, and so on. I've already expressed my frustration with this new functionality as it is not at all user friendly. I would suggest submitting a support ticket requesting this be changed back to the way it was. Perhaps if enough of us submit tickets, they will revert this back to the old way that was much better (even if it did occasionally create orphan accounts).
- Chris
Rachael/Chris,
Maybe I am missing something here, but we have a nightly job that inserts all of our TNEW Guest Checkout accounts into the merge table; all merging to one standard account, and it merges them just fine, no errors.
Is there something special in play of which I am unaware if the accounts are not TNEW Guest Checkout accounts?
John
Got it. Something we stumble on today.
Is it a custom job? We typically merge manually.
Unknown said:We received this error for the first time "Constituents Can Only Be Scheduled Once for a Single Merge."
What version of Tessitura are you on? We are on 15.0.6 at the moment, and I can't find that text among impresario sprocs.
15.1.2
Unknown said:15.1.2
Cool. We'll be on that in Live soon enough. If I can track down where they're doing that check, I may comment it out.
Interesting, we am on 15.1.1, and I am definitely not experiencing that, so it must be a VERY recent change.
This happens when you go to the actual merge screen and try to merge more than one account that has dupes. I had submitted a support ticket about this. Here is the response:
> B into A and C into A
Why shouldn't we be able to do that? If I can't in the client, I'll add 'em to the table via SQL. We'll see...
Here is the error message you get. I had scheduled 166265 in a merge and tried to schedule another account into that same account:
Chris,
Are you 15.1.2 as well, or on a previous version?
We are on V15.1.0
Although that's great for those who have SQL access and know how to do this. It doesn't help the front end users who used to be able to schedule multiple merges at once.
Well, that at least helps me to know that it just should be a client side irritant and our procedural stuff can continue unabated. Still irksome, though...