Data Analysis Expressions (DAX) is a formula language introduced by Microsoft in Power Pivot and Analysis Services Tabular to define calculations and queries.

DAX Formatter is a free tool that transform your raw DAX formulas into clean, beautiful and readable code.
The syntax rules used improves the readability of the expressions, if you want learn more read the article: Rules for DAX Code Formatting.


You can format any DAX query and expression in the form:


You can call the service via standard HTTP GET and POST requests. Learn more »


DAX Formatter is not working as expected?
Please fill out the form as completely as possible.

Note: the current formula will be automatically attached to the request.

DAX Patterns 2015 Book

Support Us

If you use DAX Formatter for your posts, please embed our badge:

DAX Formatter by SQLBI DAX Formatter by SQLBI
<a href=""><img src="" alt="DAX Formatter by SQLBI"></a>
<a href=""><img src="" alt="DAX Formatter by SQLBI"></a>

Latest Changes

March 20, 2015:

Implemented Description, Visible, and DisplayFolder calculation properties for DAX Editor

The new features implemented in DAX Editor (calculation properties Visible, Description, and DisplayFolder) are supported in DAX Formatter syntax. The extension of custom MDX Script is not yet supported.

February 6, 2015:

Fixed separators bug in HTML version

Choosing non-US separators in HTML-only version was not working and the behavior is now fixed.

January 18, 2015:

Improved detection of table names

Table names having function names where not detected by DAX Formatter unless included within single quotes. Now the behavior has improved and function names can be used in DAX Formatter as table names even without single quotes.

January 11, 2015:

Added raw HTML version

Added a raw HTML version of DAX Formatter. Certain corporate policies do not allow using the scripts we use for a better user experience. You can use the HTML-only version at this address:
Also fixed minor bugs in URL syntax (there was an error using single quotes in DAX syntax).

December 30, 2014:

Fixed missing space at the end of USERELATIONSHIP

There was a missing space before the close parenthesis of USERELATIONSHIP function when it was inline.

December 6, 2014:

Automatic removal of special character

When a formula was pasted from OneNote or Power Point, a few non standard characters were included (such as 0x0b and 0xa0). These characters are now replaced with spaces in the input before formatting, so the formula is correctly parsed and displayed.

November 29, 2014:

Support implicit conversion of table expression in scalar values

Certain table expressions that are converted in scalar values were not previously supported. An internal refactoring of the grammar supports now this type of conversion. As a side effect, certain syntax errors are no longer recognized by DAX Formatter, but this could be considered a benefit, because DAX Formatter now correctly format a certain number of invalid DAX syntaxes (that will generate errors once executed, anyway).

October 26, 2014:

Fixed parsing of floating point numbers

Floating point number starting or ending with “.” are now correctly recognized

August 16, 2014:

Added support to query parameters

The DAX query can have parameters with the prefix @

June 30, 2014:

Fixed issue with RELATED within EARLIER/EARLIEST

Using RELATED within EARLIER or EARLIEST was not recognized as a valid syntax.

June 3, 2014:

Added buttons before the formatted query

In case the formatted query does not display in the browser page, the buttons to copy/edit/create new query are visible also in the upper area of the screen.

May 18, 2014:

Fixed issue with ROLLUP function

Fixed a grammar bug that was not recognizing the usage of ROLLUP function in case it had columnlist before and after the ROLLUP function call.

March 25, 2014:

FIrst support to comments

You can include comments (single line with // and multiple lines with /* … */ ). Comments at the end of an expression are not recognized. Comment position might be moved according to formatting. Please submit any bug on comment Handling, thanks!

Fixed issue with FIND function

If the third argument in FIND function was missing, and the fourth was present, the formatting did not recognize a valid syntax.

March 5, 2014:

Fixed split of expressions in too many lines

Now it splits only two binary operators in the same expressions. To be improved, implementing different logic for logical, comparisons and arithmetical operators.