Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I am attempting to connect using DirectQuery with the Power Platform Dataverse connector. I'm getting this error message in the Source step when I go to edit the query in Power Query Editor:
Is this a bug?
Solved! Go to Solution.
Hello @Anonymous,
After a bit more testing, I believe that the above error message appearing in Power Query Editor is a bug and the message should not be there. If I ignore the error message and load the query into Power BI Desktop, the table storage mode is shown as DirectQuery. And after publishing the report to PBI service the DirectQuery seems to be working as expected.
I hope MS will fix this bug as the error message caused a lot of wasted time spent trying to "debug" something that was working.
Hi @Susan_ ,
Thanks for reaching out to us with your problem. Base on your description, you got the error message when connect to Dataverse connector with Direct Query mode. And as checked your screenshot, there is only one connection setup step in Advanced Editor. Please review the following official documenation and check if it fulfill the rerequisites of connecting to Dataverse.
Power Query Dataverse connector - Power Query | Microsoft Learn
And the following links are the threads which has the similar problems as yours.
Solved: Error: "This step results in a query that is not s... - Microsoft Fabric Community
I was able to fix the following by firstly using Import mode instead of DirectQuery.
How to connect to Dataverse using Direct Query - Microsoft Fabric Community
In this instance, I opted to query the dataverse source using the Azure SQl connector option which gave me a setup I was used to.
Best Regards
Hello @Anonymous,
After a bit more testing, I believe that the above error message appearing in Power Query Editor is a bug and the message should not be there. If I ignore the error message and load the query into Power BI Desktop, the table storage mode is shown as DirectQuery. And after publishing the report to PBI service the DirectQuery seems to be working as expected.
I hope MS will fix this bug as the error message caused a lot of wasted time spent trying to "debug" something that was working.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 96 | |
| 70 | |
| 50 | |
| 42 | |
| 40 |