Improve the Advanced Query Editor
Add better static analysis, IntelliSense, and general formatting abilities (like allowing tabs) in the "Advanced" editor
We’re glad to let you know that this feature is now Generally Available. Please refer to the Power BI Desktop April release announcement for more details: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-april-2019-feature-summary/
Thanks for your feedback!
Maiquel Sampaio de Melo commented
I second this! Miguel, do you have any update to share with us? Thanks
Any news on this improvement?
Doug Robertson commented
I second every comment above and want to add a request for better highlighting and selection with a mouse.
Who designed that feature. It feels like it is designed to specificly frustrate me when I am attempting to copy and paste any code. How did you make it so good at preventing me from selecting what I actually want???
Otherwise it is hard to read and write there.
Jay Stevens commented
OMG. This is the best!!
Javier Recasens commented
Thank you Miguel!
And give the user the ability to change the font size!
Mike Roycroft commented
I can but join the clamour asking for an improved editor. Given that languages such as Python have managed to be integrated with Visual Studio, bringing all the benefits such as support for intellisense, could that not be the fist step?
We would then use this "advanced" editor [which it isn't] merely as the means of pasting code developed elsewhere, which we all do now but using VS rather than Notepad++ which seems to be the frontrunner at present.
The long-term aim has to be intellisense etc native to the product but VS integration would be a good first step along that road
Ted Eichinger commented
Best idea ever, Intellisense for Excel Power Query and Power BI Desktop
Colin Banfield commented
In the beginning, I was quite puzzled that: 1) The "Advanced Editor" is not even a basic editor for M scripting (e.g. far less capable than Notepad V1.0)
2) M has about double the functions of Excel, yet there's no Intellisense
3) In recent times, proper case for default steps names was replaced with spaced names that end up with ugly and error prone characters in the resulting script.
Finally, it occurred to me that the "advanced" editor was designed as a way of viewing recorded steps and making light modifications. It was never designed to do anything substantial, like creating scripts from scratch, or making substantial modifications to recorded scripts.
I made my peace with the editor a long time ago when it became clear that it was not going to get better anytime soon (that was about two years ago, and it turned out to be true).
I get the syntax highlighting, function intellisense and all of the editing functionality that I need in NotePad++. The advanced editor is merely used to paste scripts created in NotePad++
Do this ASAP. eagerly waiting
Is this still under review or are you already working on this?
Arthur Nicholson commented
This would be a massive help for productivity.
It obviously wouldn't be a v1.0 but Visual Studio integration would make out job so much easier (imagine intellisence, load to pbix and TFS integration). Baby steps ;)
Mourad Louha commented
+3 - would make things much easier. Thanks.
For the love of God please do this.
I also rely on Notepad ++ and love it for how helpful it is (Thank you Don Ho & team!). But I'd much rather have the suggested improvements right in the various Power BI Editors.
Alex Jankowski commented
And how about automatically managing those pesky commas?
This would increase the number of users
Ken Puls commented
Not just the Advanced Editor please. Add Intellisense to the Add Custom Column dialog as well (and make sure it gets to Excel, not just Power BI Desktop)
Dan Ahlvin commented
Writing code in Notepad ++ and then copying and pasting into the advanced editor is not very convenient