I did a pre-check (via SECA) that also asks for confirmation when a possible
duplicate is detected.
But like I said, I just can't absolutely prevent users from entering duplicates!
Yes, the pre-check does help reduce instances of duplicates, since users are reminded about
already existing records.
At some point, we still need to reconcile duplicates caused by human error. I'm interested in this
particular process.
The case in discussion sounds like it has something to do with checkouts from ecommerce, where
anonymous shoppers create multiple userLogins. No way we can tell the anonymous shopper this: "Hi,
there's somebody else named Blah Bleh in our database. We'll show you all his details so you can
kindly confirm if that is really you?"
Jonathon
Bilgin Ibryam wrote:
I also have the same need and idea for preventing duplicate person/customer
entries but still no time for it. My idea was to write an event for checking
some key fields like Jonathon said and if they already exist in the DB to
require a confirmation before recording(duplicating) the new customer.
Is it a good idea to have such a mechanism for precheck in ofbiz ? May be
more generic one.
