Is Power Query Lang. being actively developed?

Question

I ask because I'd love to see the language develop a bit (says the "new guy", sheesh). This is based on a simple column reorder, moving&nbsp;the&nbsp;column "localTime" from the right end of a list to the left end results in code like this!:&nbsp;    #"Reordered Columns" = Table.ReorderColumns(
        #"Filtered Rows",
            {
                "WEATHER STATION CODE", 
                "DATA DATE and HOUR", 
                "TIME ZONE", 
                "localTime", 
                "° LATITUDE of STATION", 
                "° LONGITUDE of STATION", 
                "ELEVATION of STATION (Feet)", 
                "TEMPERATURE °F", "HEAT INDEX °F", 
                "WIND CHILL °F", 
                """FEELS-LIKE"" TEMPERATURE °F", 
                "WIND CHILL ENERGY, W/M2", 
                "HIGHEST TEMPERATURE °F", 
                "LOWEST TEMPERATURE °F", 
                "DEW POINT TEMPERATURE °F", 
                "NORMAL DEW POINT TEMPERATURE °F", 
                "RELATIVE HUMIDITY (Percent; %)", 
                "NORMAL RELATIVE HUMIDITY (Percent; %)", 
                "WET BULB TEMPERATURE °F", 
                "NORMAL WET BULB TEMPERATURE °F", 
                "WIND DIRECTION  (Degrees, True)", 
                "WIND SPEED (M.P.H.)", 
                "MAXIMUM INTRA HOUR WIND SPEED (M.P.H.)", 
                "SPEED GUST (if any, M.P.H.) ", 
                "NORMAL WIND SPEED (M.P.H.)", 
                "CLOUD COVER (Percent; %)", 
                "NORMAL CLOUD COVER (Percent; %)", 
                "CLOUD CEILING (x 100-Feet)", 
                "CLOUD COVER (Type)", 
                "COVERAGE, LOW (Percent; %)", 
                "COVERAGE, MIDDLE (Percent; %)", 
                "COVERAGE, HIGH (Percent; %)", 
                "VISIBILITY (Miles)", 
                "MINIMUM INTRA HOUR VISIBILITY (Miles)", 
                "NORMAL VISIBILITY (Miles)", 
                "SOLAR IRRADIANCE (Beam Horizontal, W/M2)", 
                "SOLAR IRRADIANCE (Diffuse, W/M2)", 
                "SOLAR IRRADIANCE (Global Horizontal, W/M2)", 
                "SOLAR IRRADIANCE POSSIBLE (Beam Horizontal, on a Clear Hour, W/M2)", 
                "SOLAR IRRADIANCE POSSIBLE (Global Horizontal, on a Clear Hour, W/M2)", 
                "SOLAR IRRADIANCE (ET, W/M2)", "SOLAR IRRADIANCE, PERCENT of POSSIBLE (Direct)", 
                "SOLAR IRRADIANCE, PERCENT of POSSIBLE (Global)", 
                "MINUTES of SUNSHINE (WBI Calculated)", 
                "NORMAL MINUTES of SUNSHINE (WBI Calculated)", 
                "MINUTES of SUNSHINE (Total Possible)", 
                "SUN ANGLE, °ABOVE HORIZON", 
                "SUN ANGLE, °FROM ZENITH", 
                "SUNSHINE, PERCENT of POSSIBLE (Calculated / Total Possible)", 
                "NORMAL SUNSHINE, PERCENT of POSSIBLE (Calculated / Total Possible)", 
                "SOLAR IRRADIANCE (Beam Normal, W/M2)", 
                "SOLAR IRRADIANCE POSSIBLE (Beam Normal on a Clear Hour, W/M2)", 
                "NORMAL WATER EQUIVALENT (Inches)", 
                "WATER EQUIVALENT AWXCLIMO (Inches)", 
                "NORMAL SNOWFALL, WBI (calculated; Inches)", 
                "SNOWFALL, FINAL (AWXCLIMO, Inches)", 
                "PRESSURE (Inches)", 
                "PRESSURE (Millibars)", 
                "NORMAL PRESSURE (Inches)", 
                "NORMAL PRESSURE (Millibars)", 
                "WBI 2-DIGIT NUMERIC WEATHER CODE", 
                "WBI 2-4 ALPHA NUMERIC WEATHER CODE", 
                "WBI WEATHER TEXT"
            }
        )Now, I might be doing it wrong, i'm new here. But I feel like the equivalent in Python would be something like:move column "localTime" where I want it
    please
thanksSays the guy who knows 0 Python (but who does know clean code when he sees it :) )&nbsp;What are your thoughts on this?

imkef · Answer

Some thoughts in random order:

The M-language is actively developed by Microsoft, but the community that builds additional packages isn't big (yet, hopefully). This might have something to do with the fact that there is still no elegant solution to use package-like additions on an enterprise level (yet, hopefully...) You can check out my GitHub-Repo to get some ideas what could be added:&nbsp;https://github.com/ImkeF/M
The M-language that is autogenerated by the steps you take in the UI can be as clumsy as with the VBA-Assistant in Excel. You can use more elegant code if you know the language.
In Python, you can use just the same "clumsy" technique to reorder column like the M-code you've pasted above.
I you prefer Python to M, you can use it in Power BI instead of M. There is an option to run Python-scripts in the Query Editor and you can do all you imports and transformation via Python (or R) instead if you feel more comfortable with it.

With regards to your pseudocode: How would you expect the "where I want it" to be determined?:

Move my field x positions to the right (or left) ("Relative number")
Move my field x next to field y ("Relative before or after")
Move my field to the xth position of the table ("Absolute")

Of course it's possible to write an M-function for all of them that will just need the name of the x (and y) -column to be specified.
&nbsp;

ericonline · Answer

Nice, thank you for the thoughts, I do appreciate the engagement. The purpose of the OP was to "prod" the community a little to see what came of it.&nbsp;RE:&nbsp; Your Github library:What a treasure! Hopefully I can submit some PR's and pass the project I've been working on (API POST request - JSON - table)RE: Elegant M:Yes, the auto-generated M is tough to reproduce consistently. I&nbsp;do need to get to know the language.RE: Python:I have no preference for language (I don't truly know either one!). It is very cool to know Python is supported by Power BI. I was unaware of that.RE: Pseudocode:More of a joke on my part. I do feel like M is being quite literal and perhaps even missing a layer of abstraction that would simplify things (certainly in the M example above).&nbsp;There likely IS a layer of abstraction that can be implemented, I'm just not sure of how to learn/implement it.&nbsp;I look forward to continue the path of learning and sharing here in the community.&nbsp;&nbsp;Take care!&nbsp;

greg_deckler · Answer

Yes, I do believe that M is being actively developed. From a computer language theorists perspective, comparing Python with M is apples and oranges. Python is an object-oriented, imperative, functional, procedural, reflective language while M is a mostly pure, higher-order, dynamically typed, partially lazy functional language. I mean, come on, like how different can you get??
&nbsp;
All of that aside, M does tend to be tied to column names too much and can be rather verbose when working with them.&nbsp;ImkeF do you have any thoughts on this topic?

ericonline · Answer

Hi&nbsp;Greg_Deckler. I totally get what you're saying.&nbsp;&nbsp;From a "data visualization" perspective (output of effort), Python&nbsp;and its plugins&nbsp;are what&nbsp;Power BI is compared with. At least&nbsp;within&nbsp;my org. So when we go to code review and we're comparing lines of code (apples) with actual charts (apples) from both tools...&nbsp;the tools do have instances where they are comparable.&nbsp;Thank you for the insights and expertise!

Forum Discussion

Is Power Query Lang. being actively developed?

4 Replies

Related content

Develop Power Query outside Power BI or Excel

Power BI Development and Best Practices

Creating ICMs via Activator

Activity Statistics

Laptop Hardware Requirements for Power BI Desktop Developers