MetricSign
EN|NLRequest Access
Low severitydata source

Power BI Refresh Error:
ParquetUnsupportFileLevelCompressionOption

What does this error mean?

The file-level compression option specified for Parquet is not supported — Parquet uses column-level compression internally, and file-level options for other formats do not apply.

Common causes

  • 1A file-level compression type (e.g., ZipDeflate) was configured for a Parquet format dataset, which is not supported
  • 2A dataset previously used for a non-Parquet file type was switched to Parquet without removing the file compression setting

How to fix it

  1. 1Open the Parquet dataset settings and remove the file-level compression type setting.
  2. 2For Parquet, configure column-level compression (Snappy, GZip, None) in the copy activity codec settings instead.

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