MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
ParquetNotSupportedType

What does this error mean?

A data type in the Parquet file is not supported by the ADF Parquet connector — certain complex or nested types may not be directly readable.

Common causes

  • 1The Parquet file contains a LIST, MAP, or deeply nested STRUCT type that ADF cannot flatten
  • 2A custom Parquet logical type annotation is not recognized by the ADF Parquet reader
  • 3The file was written with Parquet v2 features not yet supported by the ADF integration runtime version

How to fix it

  1. 1Identify the unsupported column from the error message and exclude it from the copy if it is not needed.
  2. 2Use Azure Databricks or Synapse Spark to read the Parquet file and write it in a simpler format that ADF can process.
  3. 3Upgrade the self-hosted integration runtime to the latest version for broader Parquet type support.

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