UPSERT Runs Successfully but Doesn’t Insert or Update Data

​

Sometimes an integration run in Skyvia finishes with Success, but no new data is inserted or updated in the target table.

This situation most often occurs when using the UPSERT operation.

🔹Why this happens

UPSERT decides whether to Insert or Update a record based on the ID (primary key) field: 

1. If ID is NULL, Skyvia performs an Insert.
   
2. If ID is NOT NULL, Skyvia performs an Update.
   

If the source provides an ID value that does not exist in the target, Skyvia tries to update a record that isn’t there.
The run completes successfully, but no rows are changed — because there is nothing to update. This is expected behavior, not an error.

🔹When this typically occurs

• Source and target do not share the same IDs
• The source should not provide the target’s ID
• Records should match by another business identifier (e.g., email, external code, number, etc.)

🔹Solution: Use Lookup mapping for the ID field

Instead of mapping the target ID directly, configure it as a Lookup based on another unique field.

In the Lookup settings, enable the Set null when no record found option. Result:

1. If a matching record exists in the target, Skyvia performs an Update.
   
2. If no matching record exists, the ID becomes NULL, and Skyvia performs an Insert.
   

🔹Steps to configure

1. Open the integration task and go to Mapping.
2. Find the ID (primary key) field in the target.
3. Change its mapping type to Lookup.
4. Select the source field(s) that uniquely identify the record.
5. Enable Set null when no record found.
6. Save and run the task again.
   

🔹Behavior With and Without a Lookup

When a matching record exists, the integration updates it whether a lookup is used or not.

When no matching record exists:

      • Without a lookup: no action is performed, but the run finishes successfully.

      • With a lookup: Skyvia inserts a new record as expected.

• Related Articles

• Mapping the RowNo Column for UPDATE/UPSERT Operations for Google Sheets

  When implementing UPDATE/UPSERT operations in Google Sheets, you may need to set up mapping for the RowNo mandatory field. RowNo is a unique auto-generated row number in the Sheet. It is essential for performing UPSERT/UPDATE operations, as it ...

• Understanding Records in Skyvia Data Integration

  1.1 Understanding Records in Skyvia Data Integration A record in Data Integration represents a single row in a database table. Every integration process (Import, Replication, Export, Synchronization, etc.) handles individual records. Records also ...

• The specified lookup is ambiguous. Lookup must return at most one row for the specified lookup condition

  This error occurs when a Lookup operation returns multiple matching records for the specified condition. Lookups are designed to find and act on only one record. When that’s not possible, this error is triggered. Possible solutions are blow: 1. Use ...

• A Quick Guide to Importing and Updating Audience Members in Mailchimp

  If your integration involves importing data into Mailchimp Audiences, this information might be helpful. To start, let’s take a quick look at how the UPSERT operation works: If the Id is specified, the integration attempts an Update operation even if ...

• Integration Failure Types in Skyvia Data Integration

  When using Skyvia Data Integration product, you may encounter two distinct types of integration failures: 1. Record-Level Errors These occur when one or more individual records fail to process during an integration task. For example, in operations ...