My org has a custom object called Email_Address__c as a child to the Contact object. Each time the Email field is populated and/or updated with a new value, the old value gets saved to an Emal_Address record. A Contact can have multiple Email_Address records and we have an automation checking for duplicate entries. The initial Email_Address record that gets created has a Duplicate__c value of FALSE and if one is found, the checkbox turns to TRUE for the subsequent records, up to a maximum of 3 records (1 primary record and 2 duplicate records). The automation prevents any more duplicate records from being created and stops the Email field from being populated on the Contact record.
I'm trying to configure a connector so that when someone enters their email address on the form, it searches that value in Email_Address records so we can find the true Contact record. (I know this isn't the normal way to handle duplicates, but its what works for us based on our needs) If it finds a match where Email on the form = Email field on Email_Address object AND the Duplicate checkbox = FALSE, then update the parent Contact record. If it doesn't find it, then create a new contact record.
Having trouble doing this since the lookup in the connector only stores the Email_Address record ID and I can't figure out how to get to the parent Contact ID to be able to update the parent rather than create a new one. I set it up initially to lookup the Email_Address record, then update based on "a lookup field" but I believe it stores the Email_Address record ID and can't reference the Contact ID.
Any thoughts?
@Vikas Patidar Thank you for responding, but the email address solution is already implemented in my org and is working well. My question was specific to FormAssembly functionality and traversing the parent-child relationship to achieve a desired outcome.
