Unable to create new or edit existing dataflows with incremental refresh and query folding

[Anonymous]

I have been unable to create new and edit existing dataflows for several days. I could see that if I remove incremental refresh and query folding I can do it again, but this is not an option in my scenario. The datasource connector is ODBC. I'm current using Power BI Premium. The method used is that one explained by Adam Saxton in this video: https://www.youtube.com/watch?v=x7q1DHf8wE4 and it was working fine until this issue occurred.

[Anonymous]

Error message:

ID da atividade: 3cfa85d0-1549-4c39-9584-1413b48dd0f1
Solicitar ID: 283dddb7-df3f-424a-3585-58b9bcee1c79
ID de correlação: a857333b-1d8c-169c-2f2a-4789d0f8c18e
Código de status: 500
Hora: Tue Jul 26 2022 13:02:02 GMT-0300 (Horário Padrão de Brasília)
Versão do serviço: 13.0.18666.32
Versão do Cliente: 2207.2.12400-train
Cluster URI: https://wabi-us-north-central-f-primary-redirect.analysis.windows.net/

[Anonymous]

Hi @Anonymous ,

Incremental refresh is supported for Power BI Premium, Premium per user, Power BI Pro, and Power BI Embedded datasets.

Incremental refresh and real-time data works best for structured, relational data sources, like SQL Database and Azure Synapse, but can also work for other data sources. In any case, your data source must support the following:

The table must contain a date column of date/time or integer data type. 

Incremental refresh is designed for data sources that support query folding, which is Power Query's ability to generate a single query expression to retrieve and transform source data, especially if getting the latest data in real time with DirectQuery

Please check whether the above requirements are met.

Best Regards,
Community Support Team _ Caitlyn

[Anonymous]

Hi @Anonymous,

Thanks for the suggestions. In fact, my scenario met the requirements.

Luckly I could find the solution for this problems (although I don't quite understand the source of the problem).

In the video whose link I shared here, Adam Saxton suggests to change the last step of the power query transformation this way:

In fact, it was working well until some moment when I needed to change a little bit one of my dataflows and then start to facing this problem.

I was doing exactly the same thing that worked for a long time, but then it stopped.

Trying to find a workaround for that, I've decided to get rid of this last step and then... the dataflows could be saved and loaded properly again.

Just that: I removed the last step and everything worked again.

Obviously, when I save and load the dataflows, the last step is restored without errors.

I didn't understand what can be have changed that resulted in this behaviour, but the fact is that this action seems to be necessary now in order to edit existing or create new dataflows using the Saxton's method for query folding some types of datasources and apply incremental refresh on them.

Thanks a lot!

[Anonymous]

Kindly see the comments below, this issue has been solved.