Hi, all-
Does merging Tessitura accounts impact existing membership cards and the ability to scan them?
I've been told that someone's card was unsuccessfully scanned and the error message stated that the card was merged with another account.
I didn't see the message, and was wondering if anyone had insight before having to try to duplicate the issue.
Thanks!
Rachel
Hi Rachel,
Whilst we don't use this functionality, I can't be sure if my thoughts are relevant - but here goes...
I suspect that the bar code printed on the membership card has the customer_no value included and that the constituent record was delete ID involved in a merge. To prevent this, you could get your DBA to include code in the database procedure LP_VALIDATE_CUST_MERGE so that if the constituent has a membership, it cannot be the delete ID in a merge.
Martin
Martin,
Thank you for your response! Your thoughts are certainly relevant and we do include the customer ID in the bar code.
I was under the impression we already had this set to not delete accounts with active memberships, but I don't know how else we could get the error message we are, so we must not.
We'll have to review the procedure to confirm. Thanks much for your advice!
Best,
Thank you, John. Glad to know it happens to other organizations as well.