This feature allows you to identify existing records when importing records. It analyzes data files and datasets to identify similar, existing records in the destination application and react accordingly. It currently applies to imports from relational databases, and HTTP or REST APIs including:
- Amazon Redshift
- Google BigQuery
- Microsoft SQL
- Oracle DB (SQL)
- REST API
- Step A: Import your records
- Step B: Identify existing records
Records are normally imported through create, insert, or update methods. Importing records varies from application to application, but generally, you can insert or update a record in a database, and create and update records in HTTP or REST API-based applications.
As an example, you can select Insert or Update to add new records to the database (insert) or update existing records in the same import. After you import records integrator.io checks each record (based on your specified parameters) and determines if the records are new or existing. You configure how to identify an existing record in Step B.
As an example, you can select Composite, which gives you access to two relevant sub-methods: Create new data & ignore existing data or Update existing data & ignore new data.
When you choose this method, integrator.io searches for and compares existing data. When it finds new data, it creates new records. When it finds existing data in the destination application, it ignores the new data and does not update the records.
When you choose this method integrator.io searches for, compares, and updates existing data. If integrator.io finds new, non-existent data it ignores the data instead of creating new records.
After you select an import method, you can choose how you would like to identify the existing records. Regardless of the application or import method, you have two options to identify the records.
- Records have a specific field populated
– or –
- Run a dynamic lookup
This method searches existing records using a field you specify. It determines if the field in your source record already has a value; if so, the source record is considered an existing record.
This is a direct comparison between existing and new fields in your records. After you input a field from your new record, integrator.io searches for existing, matching records. You can then insert, create, update, or otherwise modify the data accordingly.
This method runs a search in the destination application to find a record quickly. If a record matches the search criteria, the source record will be considered an existing record. These dynamic searches are called ‘lookups’.