Identify existing records when importing records

This feature allows you to identify existing records when importing records. It analyzes data files and datasets to identify similar or existing records in the destination application and react accordingly. You can use this for imports from relational databases and HTTP APIs including:

• Amazon Redshift
• Google BigQuery
• HTTP
• Microsoft SQL
• MongoDB
• MySQL
• Oracle DB (SQL)
• PostgreSQL

Contents

• Step A: Import your records
  • Relational databases
  • HTTP APIs
    • Create new records & ignore existing records
    • Create new records & update existing records
    • Ignore new records & update existing records
• Step B: Identify existing records
  • Records have a specific field populated
  • Run a dynamic lookup

Step A: Import your records

Records are normally imported through create, insert, or update methods. The process of importing records varies from application to application, but you typically can insert or update a record in a database, and create or update records in HTTP or REST API-based applications.

Relational databases

As an example, you can select Insert to add new records to the database or update to revise 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. See Step B for information about how to identify an existing record.

Import records in a relational database

REST and HTTP APIs

As an example, you can select the Composite HTTP method, which gives you access to three relevant sub-methods:

• Create new records & ignore existing records
• Create new records & update existing records
• Ignore new records & update existing records

Composite method and types

Create new records & ignore existing records

When you choose this method, integrator.io searches for and compares records based on the settings you specify in the Identify existing records section. When it finds new, non-existent data, it creates new records. And, when it finds existing records in the destination application, it ignores the records.

Create new records & update existing records

When you choose this method, integrator.io searches for and compares records based on the settings you specify in the Identify existing records section. When it finds new, non-existent data, it creates new records. And, when it finds existing records in the destination application, it updates the records with the new data.

Ignore new records & update existing records

When you choose this method, integrator.io searches for and compares records based on the settings you specify in the Identify existing records section. When it finds new, non-existent data, it ignores the records. When it finds existing records in the destination application, it updates the records with the new data.

Step B: Identify existing 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

Options for identifying existing records

Records have a specific field populated

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.

Relational database with a specific field populated

HTTP or REST API with a specific field populated

Run a dynamic lookup

This method searches 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’.

Learn more about creating lookups.

Dynamic lookup in a relational database

Dynamic lookup in an HTTP or REST API