Incremental Refresh in Fabric Dataflow with MySQL ODBC

Thankyou, tayloramy and lbendlin for your responses.

Hi martinacahya,

We appreciate your inquiry submitted via the Microsoft Fabric Community Forum.

Based on my understanding, the issue arises because Fabric Dataflow (Gen2) incremental refresh validation requires full query folding to the data source. Although the Power Query Editor displays a green folding indicator, ODBC based MySQL connectors do not guarantee complete pushdown of the incremental filter to the backend. Consequently, the service blocks the Dataflow publish and displays the “query with incremental refresh is not folding” error.

Please follow the steps below, which may help resolve the issue:

1. In your Dataflow Gen2 → Incremental Refresh settings → Advanced options, uncheck “Require incremental refresh query to fully fold.” This relaxes the validation check and allows publishing, although refresh performance may be slower.
2. Replace the ODBC connection with the native MySQL connector, if your environment supports it. Native connectors provide better folding support and are fully compatible with incremental refresh.
3. Load your MySQL data (via ODBC) into a Fabric Lakehouse or SQL endpoint first. Then configure incremental refresh on a secondary dataflow that reads from this Fabric native source, ensuring full folding and partition support.

Additionally, please refer to the links provided below:
Incremental refresh in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Power Query MySQL database connector - Power Query | Microsoft Learn
Understand and optimize dataflows refresh - Power BI | Microsoft Learn

If the issue persists after performing the above steps, and since you have already raised a support ticket, we request that you monitor updates from the support team regarding this matter.

Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.