Medium severitydata source

Power BI Refresh Error:
AzurePostgreSqlNpgsqlPartitionColumnNameNotProvided

What does this error mean?

The ADF copy activity is configured for parallel copy from Azure PostgreSQL but the required partition column name was not specified.

Common causes

1Parallel copy mode was enabled for the PostgreSQL source but the partition column name field was left empty
2Dynamic range partitioning was selected without specifying which column to use for range partitioning

How to fix it

1In the copy activity source settings, specify a numeric or datetime column to use as the partition column for parallel copy.
2Set the partition upper bound and lower bound to match the data range in the selected column.
3If no suitable partition column exists, disable parallel copy and use sequential copy.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

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