A new knowledge base article has been published on our support portal.
Overview
In this business scenario we have a custom entity which stores Application data that a User provides.
When a User submits this Application, we want to match the details given in the Application with any existing Contact. The match rules are as follows,
- Match on email address
- Match on phone number
- Match on firstname, lastname, date of birth
If there is no match to any of the above rules we will create a new Contact. Finally the lookup field of type contact will be set on the Application.
Note: In this KB article we use a custom entity called Application that has the custom fields Email address, Phone number, First name, Last name, Birthday and a lookup to the Contact entity. We also have a custom field called Birthday. on the Contact entity.
North52 BPA Solution
The North52 BPA solution works like this:
- A formula is created that will trigger whenever an Application record is created or whenever the following fields are updated:
- Email address, Phone number, First name, Last name and Birthday
- When triggered, the formula will perform 3 searches to find a corresponding Contact. It performs these in descending order, stopping the searches if one is found.
- First it will look for a Contact with an email address that matches the one in the Application
- If it finds one, it will associate that Contact with that Application
- Second, it will look for a Contact with a phone number that matches the one in the Application
- If it finds one, it will associate that Contact with that Application
- Third, it will look for a Contact with a First Name, Last Name and Birthday. that matches those in the Application
- If it finds one, it will associate that Contact with that Application
- First it will look for a Contact with an email address that matches the one in the Application
- If the formula finds no matching Contact, it will create a new Contact using the fields given in the Application and associate it with the Application