Power Query is an ETL tool created by Microsoft for data extraction, loading and transformation, and is used to retrieve data from sources, process it, and load them into one or more target systems. Power Query is available in several variations within the Microsoft Power Platform, and is used for business intelligence on fully or partially self-service platforms. It is found in software such as Excel, Power BI, Analysis Services, Dataverse,[1] Power Apps, Azure Data Factory, SSIS, Dynamics 365, and in cloud services such as Microsoft Dataflows,[2] including Power BI Dataflow used with the online Power BI Service or the somewhat more generic version of Microsoft Dataflow used with Power Automate.

The Power Query user interface, as shown in the Power Query Online experience.

ETL is closely related to data modeling,[3] and for transformation, Power Query can be used to develop a logical data model in those cases where the data does not already have one, or where there is a need to further develop the data model.

History

Power Query was firstly included as an optional additional import feature in Excel besides PowerPivot (used for providing a data model to the PivotTables pivot tables, and more) in Excel 2010 and 2013. In Excel 2016, the function was included in standard Excel and renamed Get & Transform for a short time, but has since been named Power Query again.

M Formula language

Power Query is built on what was then[when?] a new query language called M. It is a mashup language (hence the letter M) designed to create queries that mix together data. It is similar to the F Sharp programming language, and according to Microsoft it is a "mostly pure, higher-order, dynamically typed, partially lazy, functional language." The M language is case-sensitive.

Much of the user interaction with Power Query can be done via graphical user interfaces with wizards, and this can be used for many common or basic tasks. It is also possible to use the advanced editing mode where the developer can write in the M formula language; this gives greater expressive power, more possibilities, and can also be used to change the code generated by the graphical wizards.

Let expression

User queries are typically written with a top level let expression. The let expression contains a list of comma-separated named reference (variables) bindings and an in expression which is what the let expression evaluates to. The in expression can reference the variables and the variables can reference each other. Backwards and forward referencing is allowed, and self-referencing is allowed by prefixing the @ on the variable. Variables are recursively evaluated as needed to evaluate the in expression. No variable is evaluated more than once.

Examples

let
    a = "Hello",
    b = "World",
    result = a & " " & b
in
    result

Assertions and Datatypes

Variables are not typed in Power Query. Instead, an expression can have a type assertion which will evaluate to an error when the expression does not evaluate to a value compatible with the assertion. Assertions can be preceded by nullable to include null in the allowed values.

More information Name, Description ...
Datatypes/Assertions
NameDescriptionDatatypeAssertion
numberAssertion for integer and floating-point numbers No Yes
intSigned 32-bit integer Yes No
longSigned 64-bit integer Yes No
doubleIEEE 754 float Yes No
decimal128-bit float. Same as C#'s decimal Yes No
timeTime of day Yes Yes
dateA calendar date ranging from 1 CE to 9999 CE in the Georgian Calendar Yes Yes
datetimeA composite of the date and time datatypes Yes Yes
durationA measurement of elapsed time (can be negative) Yes Yes
logicalRepresents a Boolean true or false value Yes Yes
textA Unicode string Yes Yes
guidA Globally Unique Identifier (Converts to a text as needed automatically) Yes No
listAn ordered list of values Yes Yes
recordAn ordered map from text to any value Yes Yes
tableA 2D matrix where each column has a unique name and type (type not checked on table contents) Yes Yes
functionA power query function Yes Yes
typeRepresents a datatype and may contain assertion information Yes Yes
actionAn internally used datatype Yes Yes
nullThe null singleton Yes Yes
anyRepresents all values No Yes
anynonnullRepresents all values except null No Yes
noneRepresents no values and always fails as an assertion No Yes
errorA pseudo value representing an error No No
Close

Comments

Power Query supports the C block (/* ... */) and C line (// ...) comments.

DirectQuery

In Power BI, use of M-code is somewhat limited in DirectQuery, as opposed to Import which has all capabilities. This is due to the requirement that M-code in DirectQuery has to be translated into SQL at runtime.

Query Folding

Query Folding is the ability for the Power Query steps to be transpiled into a single query at the data source (for example in Transact SQL). As such, Query Folding works like a traditional ETL process, and enables working on the data before loading. Query Folding is not always supported. Steps like filtering, selecting columns and simple SQL arithmetic are supported. Steps like creating index and appending or merging non foldable sources with foldable sources are not. Folding indicators (such as folding, not folding, might fold, opaque, unknown) might indicate up to which step a query might fold. Non-folding queries will have to be performed on the client-side. The order of queries can determine how many of the steps which get folded.

See also

References

Wikiwand in your browser!

Seamless Wikipedia browsing. On steroids.

Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.

Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.