Hi All,
Has anyone customized a way to merge multiple 100% duplicate records, more often than one set at a time? We are on V15.2.31 and due to Guest checkout, customers are constantly creating new records. One customer has 46 records. We could merge them individually but it will take a long time. Hoping someone has found an answer and is willing to share. Any advice is greatly appreciated.
Tatiana
I have a related question that we've just recently seen. Perhaps I have something set incorrectly somewhere, but I don't know.
We have been getting this failed merge error message. It seems to not make sense. We want to merge the dups from Guest Checkout, but this is seemingly stopping it.
Am I missing something obvious in the setup somewhere?
It won't allow you to use the Guest Checkout record as the keep record.
Ahhhhh...thanks! We have our onsite Membership Team process the suggested dups & I didn't dig that far. I just keep seeing it in my daily report.
Amber Gale said:In our experience, that is not the case.
Our experience matches. Guest checkout dupes appear (and are merged) daily.
Upvoted. I have a low-tech method for this, but an official, supported process is long overdue.
Wow. We used Guest Checkout, briefly, a while ago. We'd had some other issues with it: no way to turn it off for things that should require an login, like memberships and digital content was the main thing. But we also have a (Consulting-built) auto-merge system, so I guess I didn't notice.
Other integrations we've worked with have simply looked for a login with the same email address as the one entered by the customer, and considered it a safe assumption that this was the same person and therefore there was no need to create a new account. It would be nice to have some kind of flag on the order itself (not the customer) that the order was executed using guest checkout.
if you're able to share I would love to just take a look at this procedure. thanks
In the v16 documentation is mentions the ability to have multiple merges again......anyone on V16 that can confirm?
We also use guest checkout - lots of duplicates created which is a pain but we have dev on staff that has added code to 'hide' guest login option when there are things in the cart - like membership were we don't want a buyer to use that check out option.
This is mind blowing - that is our dream to only have guest checkout available for free events. We find a lot of our internal teams will resist running events through Tessi because the full purchase path is offputting, but I can't offer a more streamlined path as we don't want it available for paid events. Would you mind if I reached out to you for more details on this?
Of course Tash. Happy to help if we can!