You need to sign in to do that
Don't have an account?
Milan
Best Design Practice : Checking for existing leads
Hello,
In our application, we need to verify if a lead already exists, before we insert (create) a new one. One of the ways we are going to check for existing leads is based on email. i.e If a Lead with a certain email id already exists, it means it need not be inserted (created) again.
Now, we may have to insert thousands of leads at a time. Which in turn means verifying all those thousands of leads before we insert them. What is the best possible approach, keeping time in mind, to do this ? Note : Time is critical !
One approach that immediately comes to my mind is using a Query in Partner WSDL and passing a batch of say n email Ids at a time. i.e:
qr = stub.query("select email, FirstName, LastName, Id from Contact where email IN ('abc@asd.com', 'werr@dfdf.com' ,'cxvcv@uoa.edu','dfdf.fd@wer.com', 'fd@abc.com' ,...........)");
- Would this be a good idea ?
- It is never a great idea to fire a 'like' query in existing production database... so do I have a better option ?
- Firing a single call for each lead certainly seems a slower option ... isnt it ?
Thus can anyone suggest what is the best practice for such a scenario ?
Thanks,
Milan
Any inputs for me ?All help appreciated!
Thanks,
Milan
~ sfdcfox ~
Hope i understood your problem and provided a gud solution ^_^