What causes DF-AdobeIntegration-KeyColumnMissed?

The sink transformation is configured for upsert or update mode but no key column is mapped in the sink settings. The key column name specified in the sink does not match any column name in the incoming stream (case sensitivity or rename mismatch). An upstream Select or Rename transformation removed or renamed the key column before it reached the sink

How do I fix DF-AdobeIntegration-KeyColumnMissed?

Open the failing data flow in ADF Studio and select the Adobe Analytics sink transformation.. Go to the Settings tab and locate the key column definition — verify at least one key column is specified for upsert or update operations.. Check that the key column name exactly matches a column in the incoming stream — use Debug preview on the sink input to see the available column names.. Trace back through any Select, Derived Column, or Rename transformations to confirm the key column is not being dropped or renamed before reaching the sink.. If insert-only (no upsert), switch the write method to Insert and remove the key column requirement.

Medium severitydata flow

Power BI Refresh Error:
DF-AdobeIntegration-KeyColumnMissed

What does this error mean?

The ADF Mapping Data Flow Adobe Analytics sink requires a key column for upsert or update operations, but no key column was specified or the specified column does not exist in the incoming data stream.

Common causes

1The sink transformation is configured for upsert or update mode but no key column is mapped in the sink settings
2The key column name specified in the sink does not match any column name in the incoming stream (case sensitivity or rename mismatch)
3An upstream Select or Rename transformation removed or renamed the key column before it reached the sink

How to fix it

1Open the failing data flow in ADF Studio and select the Adobe Analytics sink transformation.
2Go to the Settings tab and locate the key column definition — verify at least one key column is specified for upsert or update operations.
3Check that the key column name exactly matches a column in the incoming stream — use Debug preview on the sink input to see the available column names.
4Trace back through any Select, Derived Column, or Rename transformations to confirm the key column is not being dropped or renamed before reaching the sink.
5If insert-only (no upsert), switch the write method to Insert and remove the key column requirement.

Frequently asked questions

How do I identify which column should be the key column?

The key column is the unique identifier for upserted records — for Adobe Analytics data, typically a combination of date dimension and visitor or hit ID. Enable debug preview on the sink input to see available columns.

Does this error only happen with upsert or update operations?

Yes — Insert operations do not require a key column. If your use case is append-only, switch the sink write method to Insert and this error won't occur.

Can a column renaming upstream cause this error?

Yes — if a Select or Derived Column renames or drops the key column, the sink can no longer find it. Use debug data preview to check which columns arrive at the sink.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide