Partial Refresh (Delete-by-Key) Export

Summary:
Add a new export option that deletes only destination-table rows matching a specified key, such as KI_CODE, before inserting the updated data for that key. This provides a targeted overwrite behavior without changing the existing full-table “Replace All” export option.

Problem Statement:
Integration Platform currently supports a “Replace All” export behavior that deletes and reloads the entire destination table. This is inefficient and potentially disruptive when only one resource set needs to be refreshed. For example, when re-exporting an existing NormResSet to Oracle, users need to remove and replace only that resource set’s rows while preserving all other data in the table. Changing the existing “Replace All” behavior would also risk altering workflows that depend on the current full-table replacement process.

Proposed Solution:
Introduce a new export option for key-based overwrite behavior.
Allow users to define the field or key used to identify the records being exported, such as KI_CODE.
Before inserting exported data, delete only rows in the destination table whose key matches the incoming dataset.
Preserve rows associated with all other keys in the destination table.
Retain the existing “Replace All” option and behavior unchanged for backward compatibility.
Provide validation and clear error messaging when the key is missing, invalid, or cannot be matched in the destination table.
Model the scoped-delete approach after the existing Proposal export behavior where appropriate.

Benefits:
Reduces unnecessary deletes and reloads for targeted data updates.
Preserves unrelated destination-table data during exports.
Avoids breaking existing integrations that rely on full-table replacement.
Improves efficiency for custom tools that overwrite individual resource sets.
Provides users with a safer, more flexible export workflow.