MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
ParquetUnsupportedInterpretation

What does this error mean?

The ADF Parquet connector cannot interpret a column using the logical type or physical type combination present in the file.

Common causes

  • 1The Parquet file uses a logical type annotation (e.g., UUID, INTERVAL) not supported by the ADF Parquet connector
  • 2A physical type + converted type combination in the Parquet file does not map to a known ADF type

How to fix it

  1. 1Identify the column with the unsupported interpretation from the error output.
  2. 2Cast the column to a simpler type (e.g., string or bytes) in the source system before writing the Parquet file.
  3. 3Exclude the column from the ADF copy if it is not required at the destination.
  4. 4Check the latest ADF Parquet connector documentation for newly supported types and upgrade the IR if needed.

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-parquet

Other data source errors