Overview

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:

• If ID is NULL, Skyvia performs an Insert.
• 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 is not 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 directly.
• 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:

• If a matching record exists in the target, Skyvia performs an Update.
• 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