I'd like to merge a bunch of old constituent records from our old system that represent day of sales into the General Public/Null constituent record (customer #0). Unfortunately, when I tried to do this, I received an error message stating "Invalid Entry: Valid kept and deleted IDs must both be specific to schedule a merge." My Keep ID was 0 and the Delete ID was one of the records I wanted to merge into the General Public record.
Is there a setting I need to change? If this merge is truly NOT possible, what workarounds have you employed.
We have a ton of "bad" records I'd love to have all merged into General Public.
Thanks!Sara
Hi Sara,
I'm not 100%, but I think Tessitura may not be set up to really use customer 0 as an actual customer. I think there are numerous checks in the system to exclude it from various operations.
As to merging, I wonder if this is part of a custom check, perhaps in LP_VALIDATE_CUST_MERGE or LP_CONST_MERGE? I don't see any obvious reference to the error in any of the built-in merge procedures.
--Gawain
Gawain is correct - customer 0 isn't a real constituent and so you can't merge records into it.
You might want to create a new constituent for this - it can also be useful for when you get contacted with a "take me off your database" type call. But bear in mind that for the merge to work, you'll need to update the records so the names match.....
Martin
Martin Keen (Past Member) said:for the merge to work, you'll need to update the records so the names match.....
Martin, do you have some customizations in place for your merge procedure? We are able to merge accounts with mismatched names (and do so regularly in the case of nicknames, maiden names, mispellings, etc).
For your original quest, Sara, I have the same suggestions as above. I would create an account specifically for all of these accounts to merge into and go about it that way. I agree that I don't think customer 0 is a 'real' customer according to Tessitura and doesn't follow the same rules as others. Hope that helps!
Martin Keen (Past Member) said:But bear in mind that for the merge to work, you'll need to update the records so the names match.....
I agree with Beth, I don't believe there's anything in the standard code that prevents merging records with different names.
Martin Keen (Past Member) said:You might want to create a new constituent for this
Also agreed. If we did something like this we'd probably merge into our official Anonymous constituent.
Thanks everyone!