Duplicate Search Setting
When sending data to systems where the uniqueness of records is important, Albato can perform additional checks to remove duplicates.
For example, let's take a look at the “Create a new contact” action in the Bitrix24 CRM system if we receive a new order from our online store.
Orders are received frequently, which means that contacts of acquired users are regularly created in the CRM system. In order not to create multiple contacts that are completely identical, you can choose a rule to handle duplicates in 4 scenarios.
In this case, Albato will not try to verify that, in the destination service, there is a record equal to the one being sent. A request to add a new record will always be made. In this case, errors in creating a record can occur if the required uniqueness of the data is not guaranteed.
In this case, Albato will check the target system for a duplicate, and if it finds data with the same specified fields, the integration will stop working without creating a new record.
To implement this and other scenarios, it is necessary to specify the fields, whose correspondence will allow Albato to determine if it is a duplicate or not. Most of the time, the data used is phone and email, because they tend to be the same for customers and rarely change.
This script also looks for an existing record, and when it finds it, its fields are updated. By selecting this configuration option, you can configure a field update rule.
For example, if an order came from an online store and we found a duplicate contact, you can update the “Recipient address” field, as the customer can indicate a different address for receiving the goods.
To do this, the script will also need to directly specify the fields by which to search for the same information. If no duplicates are found, a new record will be created.
In this scenario, if a duplicate is found, the record will be updated. Otherwise, a new record will not be created. Such an alternative is recommended if you need to track contact changes and synchronize multiple systems with each other.
To do this, the script will also need to directly specify the fields by which to search for a match.
Did not work? Contact us via chat. We are on hand to help you!
For example, let's take a look at the “Create a new contact” action in the Bitrix24 CRM system if we receive a new order from our online store.
Orders are received frequently, which means that contacts of acquired users are regularly created in the CRM system. In order not to create multiple contacts that are completely identical, you can choose a rule to handle duplicates in 4 scenarios.
Don't check for duplicates, always create a new record
In this case, Albato will not try to verify that, in the destination service, there is a record equal to the one being sent. A request to add a new record will always be made. In this case, errors in creating a record can occur if the required uniqueness of the data is not guaranteed.
Do not create a new record if a duplicate is found
In this case, Albato will check the target system for a duplicate, and if it finds data with the same specified fields, the integration will stop working without creating a new record.
To implement this and other scenarios, it is necessary to specify the fields, whose correspondence will allow Albato to determine if it is a duplicate or not. Most of the time, the data used is phone and email, because they tend to be the same for customers and rarely change.
Update an existing record if a duplicate is found, otherwise create a new record
This script also looks for an existing record, and when it finds it, its fields are updated. By selecting this configuration option, you can configure a field update rule.
For example, if an order came from an online store and we found a duplicate contact, you can update the “Recipient address” field, as the customer can indicate a different address for receiving the goods.
To do this, the script will also need to directly specify the fields by which to search for the same information. If no duplicates are found, a new record will be created.
Only update an existing record if a duplicate is found
In this scenario, if a duplicate is found, the record will be updated. Otherwise, a new record will not be created. Such an alternative is recommended if you need to track contact changes and synchronize multiple systems with each other.
To do this, the script will also need to directly specify the fields by which to search for a match.
Did not work? Contact us via chat. We are on hand to help you!
Updated on: 01/12/2022
Thank you!