Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hi,
Pulling my hair out here. No matter how simple the underlying table is, I always get this warning when I click on Applied Steps->Source.
I've tried pointing to a local SQL Server. And an Azure SQL. Same thing. It's like Direct Query simply doesn't work anymore.
Anyone else getting this?
Nick
Hi there, I have SQL code in my advanced option. And I get the same warning 'results in a query ...' What's the connection between these two?
Hi,
found the same in very simple queries - even ones that just call a custon function to create a local date table.
Finally I found the problem and a solution 🙂
If some queries have been created while some preview feature where on, those queries seem to get stuck into this issue,
I have switched off "Composite Models", "Direct Qerry for... " and after restart created a new query with the same code - and that runs then without the warning: "This step results in a query that is not supportedin DirectQuery mode"
Hope this helps.
You should explain how to switch off Composite Models etc.
@Anonymous,
See limited data transformations mentioned here. Also check if you've specified SQL statement in advanced options.
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
116 | |
108 | |
108 | |
93 | |
69 |
User | Count |
---|---|
171 | |
135 | |
132 | |
96 | |
94 |