MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
ParquetBridgeInvalidData

What does this error mean?

The ADF Parquet bridge (the internal component bridging Parquet reading to ADF data types) encountered invalid data it cannot process.

Common causes

  • 1A column value in the Parquet file contains data that violates the expected encoding for that data type
  • 2The Parquet file uses a compression codec or encoding not fully supported by the ADF bridge
  • 3Null byte sequences or binary data in text columns that cannot be decoded

How to fix it

  1. 1Identify the offending column from the error output and inspect its values in the Parquet file.
  2. 2Try reading the Parquet file with Spark/Databricks to see if the same error occurs outside of ADF.
  3. 3Re-generate the Parquet file with standard encodings (PLAIN, DICTIONARY).
  4. 4Upgrade the ADF self-hosted IR to the latest version for improved Parquet codec 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