For the ecommerce side of things? Nice. Sort of like flagging possible duplicates for backend
handling.
Jonathon
BJ Freeman wrote:
in the application I wrote for accepting real-time orders from a
website, I have a service that is run to check different parms in the IP
and address fields. It then sets the order to hold status if there are
matches to the parms.
this shows up in the order task list to be dealt with by a human.
Jonathon -- Improov sent the following on 9/11/2007 7:29 AM:
Hmm. My very next project absolutely requires that. The duplicates don't
come from eCommerce, BUT still... I'm not gonna prompt users about
possible duplicates when they enter data (want to accelerate initial
data entry effort).
I'll need a webtool for the admin (or other permitted parties) to
periodically reconcile duplicate Party(s). Will be doing it soon.
Let me know what criteria should be checked? So far, I'm just thinking
"name, postal code, birthdate, mobile phone number". Note that my
application mandates the entry of birthdate, not so for ecommerce apps.
Help me do something that is also usable by ecommerce side?
Thanks.
Jonathon
Jacques Le Roux wrote:
Yes this sounds interesting, to me at least. There is always plenty of
party duplicates coming from eCommerce.
An administrator webtool as suggested by Jonathon may be interesting
too...
Jacques
De : "Bilgin Ibryam" <[EMAIL PROTECTED]>
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.
--
View this message in context:
http://www.nabble.com/Link-Party-tf4418931.html#a12612663
Sent from the OFBiz - User mailing list archive at Nabble.com.
