Hi all,
I'm wondering if there are any best-practices or advice for our current situation. We have a custom integration between our CRM solution and Eloqua. When Contacts are updated in the CRM system, the changes are automatically pushed via the REST API to the corresponding record (found by a "CRM ID" field on the Eloqua contact) in Eloqua. This generally works well. If a contact's email address changes however (they get married and change their last name, the company is bought and the email domain changes etc. etc.), and they register on our site with the new address (thus creating a second Eloqua contact), we find it's later impossible to update their CRM record with the new email address. Our integration finds the Eloqua record with the old address (because that's the one linked by CRM ID) and attempts to update it with the new address. This, however, violates the uniqueness constraint on the email address field, and the operation fails.
Ideally we'd like to keep the same eloqua contact record with all of their history etc. and just update the email address.
Any thoughts? How is this handled or avoided in your integration?
Thanks,
Lorne