Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
3 years ago

PowerBI Dataflows connector using a DirectQuery not working

Dear PBI Community,
we have a trouble with reports built upon a DirectQuery Datasets using PowerBI Dataflows as a source. We do not use any advanced transformations when the Dataflows in DirectQuery mode are used. Just simply 1:1 load. The report is working fine in PowerBI Desktop. However when I publish it into the PowerBI Service, it returns an Error: 


Unable to convert an M query in table 'Table_Name' into a native source query.

 

I figured out that the issue only appears when we are using connector PowerBI Dataflows. Once I use Dataflows it is working fine. However I guess that PowerBI Dataflows was working fine till the last week. Are there any news why the PowerBI Dataflows connector can not be used with the DirectQuery mode? Is it a bug or it is a standard behaviour? 

 

Thank you for your community support! 
Regards!

 

Dataflow
Need Help

6 Replies

  • leclercj's avatar
    leclercj
    New Member
    3 years ago

    Hello Anonymous 

    I faced exact same issue yesterday. After investigation today, I found that tables in trouble in my dataset were built several months ago using what is now named "Power BI dataflows (Legacy)" connector.
    I redefined them using the new Dataflows" connector, and it actually fixed the problem.

     

      • Anonymous's avatar
        Anonymous
        Not applicable
        3 years ago

        I am not sure there is a automatic way how to fix it. In your PowerQuery transformation you have to modify 1st step - Source. You have to change PowerBI.Dataflows for PowerPlatform.Dataflows. Then you have to navigate to the dataflow you would like to connect. And the steps for selecting the dataflow which are evaluated through PowerPlatform.Dataflows are not the same like in PowerBI.Dataflows connector.

    • Anonymous's avatar
      Anonymous
      Not applicable
      3 years ago

      Yes, exactly this is what I also figured out! I am glad that I am not the only one who had this exact issue. I know that Power BI dataflows connector is in Legacy, but there had to be change on PowerBI Service last week. Because all our solutions based upon this connector  with DirectQuery has started to fail since this week.

  • MAwwad's avatar
    MAwwad
    Solution Sage
    3 years ago

    The error message you are receiving suggests that there may be a problem converting an M query used in your report into a native source query when using PowerBI Dataflows as a source in DirectQuery mode. This could be caused by a variety of factors, such as an unsupported function or syntax in your M query, or an issue with the Dataflows connector itself.

    You can try to troubleshoot this issue by reviewing your M query code and checking for any errors or unsupported functions, as well as verifying that the Dataflows connector is up to date and properly configured. You may also want to reach out to the PowerBI community or support team for additional assistance or to report a potential bug.

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    Hello MAwwad ,
    thanks for answering. There are no transformations in my PowerQuery. There are just two PowerQuery steps - Source (PowerBI.Dataflows) and Navigation which are returned by default using the PowerBI Dataflow connector. The same Dataflow but with Dataflow Connector (PowerPlatform.Dataflows) is working fine using DirectQuery. 

    That is also the reason why I am thinking there has been released some change in PowerBI Dataflow connector. But It is only my guessing.