Merging into customer 0

Hi Sara,

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 

Hi Sara,

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.