Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register 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.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
104 | |
69 | |
49 | |
41 | |
34 |
User | Count |
---|---|
164 | |
111 | |
61 | |
53 | |
38 |