March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi All,
Once i import data through Get data> SQL Server > providing the query in the SQL statement window, is it possible to modify that SQL...? (a SQL with complex calculations for our requirement).
cuz i built few viz's and dont wanna create another query item so that i use the same dataset(Query) to be modified which i see in my data fields for ease..!!
any help will be appriciated.
Thanks in advance.
Solved! Go to Solution.
You can modify it by clicking on the wheel on the source Step in the query settings
or modify the Query parameter in the Advanced editor
/erik
The method that @aahmed showed returns the correct explanation. If you just try to go through the edit queries section at the top you will recieve the greyed out box.
The method that @aahmed showed returns the correct explanation. If you just try to go through the edit queries section at the top you will recieve the greyed out box.
@aahmed - what if the Source "wheel" is non-existent (and when I right click, the "Edit Settings" is greyed out) - I can see this feature on some tables in my pbix file but not others. It seems as though the wheel/edit feature shows up if the query is ONLY referencing one table, but if the query has a JOIN then the wheel/edit feature is not available. Have you experienced this? Any suggestions for a workaround here? Editing the queries with the JOINs are the most cumbersome (I copy/paste into Notepad++ then "replace all" of the #(lf) and then reverse those steps after I've edited my query in SSMS.
I know this is an older thread but I am also looking for an answer to this exact question currently, anyone have any documentation would be much appreciated 👍
Click on Advanced Editor. I think it's available by right clicking the query pane on the left. If not, certainly in the menu
Power Query has a "split query" option to break a query into 2 pieces. hence you can break your query into a "source" and then transformation this way. Then you can point to the new source and create a new query from that.
In my experience, I tend to write my queries in SSMS first, then paste them into the Query window when creating a new query. I find it easier and more flexible. The only exception is if you want to use Query Folding with a table from within Power BI, then it is better to use a native query.
Hi, @MattAllington I don't know u got me wrong or i did...!!
I too follow the same SSMS way. But what um asking is, once um done with
1. writing SQL in SSMS and then Copying that SQL statement in
2. Get Data> SQL Server > SQL Statement Window,
3. Importing the data / Loading the data in the report (PBI Desktop)
can i modify the query which i wrote at the get data in 2nd step...??
Hi,
You can do that via the Applied Steps in your Query editor or using the advanced editor via the View tab and then modify your M/Power Query script
Or even better create a parameter and use that parameter in your query
/Erik
hi @donsvensen um not aware of M/Power Query Script and i got a few modfications in my query through updating the previous SQL statement in SSMS. i want to use the updated SQL instead of the SQL i provided to the report before.
should i create another data connection and add another query to the report with the updated SQL is this the only choice do i have..??
or
is there anyway to update the old SQL of the Existing Query..?
You can modify it by clicking on the wheel on the source Step in the query settings
or modify the Query parameter in the Advanced editor
/erik
Hi,
I tried changing an SQL statement changing the source; but the SQL statement area is greyed out (impossible to change the text).
Thanks for your help
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
93 | |
87 | |
84 | |
77 | |
49 |
User | Count |
---|---|
160 | |
144 | |
103 | |
74 | |
57 |