Professional Documents
Culture Documents
DAX Refernce Microsoft
DAX Refernce Microsoft
Data Analysis Expressions (DAX) is a formula expression language used in Analysis Services, Power BI, and
Power Pivot in Excel. DAX formulas include functions, operators, and values to perform advanced calculations
and queries on data in related tables and columns in tabular data models.
This article provides only a basic introduction to the most important concepts in DAX. It describes DAX as it
applies to all the products that use it. Some functionality may not apply to certain products or use cases. Refer to
your product's documentation describing its particular implementation of DAX.
Calculations
DAX formulas are used in measures, calculated columns, calculated tables, and row-level security.
Measures
Measures are dynamic calculation formulas where the results change depending on context. Measures are used
in reporting that support combining and filtering model data by using multiple attributes such as a Power BI
report or Excel PivotTable or PivotChart. Measures are created by using the DAX formula bar in the model
designer.
A formula in a measure can use standard aggregation functions automatically created by using the Autosum
feature, such as COUNT or SUM, or you can define your own formula by using the DAX formula bar. Named
measures can be passed as an argument to other measures.
When you define a formula for a measure in the formula bar, a Tooltip feature shows a preview of what the
results would be for the total in the current context, but otherwise the results are not immediately output
anywhere. The reason you cannot see the (filtered) results of the calculation immediately is because the result of
a measure cannot be determined without context. To evaluate a measure requires a reporting client application
that can provide the context needed to retrieve the data relevant to each cell and then evaluate the expression
for each cell. That client might be an Excel PivotTable or PivotChart, a Power BI report, or a table expression in a
DAX query in SQL Server Management Studio (SSMS).
Regardless of the client, a separate query is run for each cell in the results. That is to say, each combination of
row and column headers in a PivotTable, or each selection of slicers and filters in a Power BI report, generates a
different subset of data over which the measure is calculated. For example, using this very simple measure
formula:
When a user places the TotalSales measure in a report, and then places the Product Category column from a
Product table into Filters, the sum of Sales Amount is calculated and displayed for each product category.
Unlike calculated columns, the syntax for a measure includes the measure's name preceding the formula. In the
example just provided, the name Total Sales appears preceding the formula. After you've created a measure,
the name and its definition appear in the reporting client application Fields list, and depending on perspectives
and roles is available to all users of the model.
To learn more, see:
Measures in Power BI Desktop
Measures in Analysis Services
Measures in Power Pivot
Calculated columns
A calculated column is a column that you add to an existing table (in the model designer) and then create a DAX
formula that defines the column's values. When a calculated column contains a valid DAX formula, values are
calculated for each row as soon as the formula is entered. Values are then stored in the in-memory data model.
For example, in a Date table, when the formula is entered into the formula bar:
A value for each row in the table is calculated by taking values from the Calendar Year column (in the same Date
table), adding a space and the capital letter Q, and then adding the values from the Calendar Quarter column (in
the same Date table). The result for each row in the calculated column is calculated immediately and appears, for
example, as 2017 Q1 . Column values are only recalculated if the table or any related table is processed
(refresh) or the model is unloaded from memory and then reloaded, like when closing and reopening a Power BI
Desktop file.
To learn more, see:
Calculated columns in Power BI Desktop
Calculated columns in Analysis Services
Calculated Columns in Power Pivot.
Calculated tables
A calculated table is a computed object, based on a formula expression, derived from all or part of other tables
in the same model. Instead of querying and loading values into your new table's columns from a data source, a
DAX formula defines the table's values.
Calculated tables can be helpful in a role-playing dimension. An example is the Date table, as OrderDate,
ShipDate, or DueDate, depending on the foreign key relationship. By creating a calculated table for ShipDate
explicitly, you get a standalone table that is available for queries, as fully operable as any other table. Calculated
tables are also useful when configuring a filtered rowset, or a subset or superset of columns from other existing
tables. This allows you to keep the original table intact while creating variations of that table to support specific
scenarios.
Calculated tables support relationships with other tables. The columns in your calculated table have data types,
formatting, and can belong to a data category. Calculated tables can be named, and surfaced or hidden just like
any other table. Calculated tables are re-calculated if any of the tables it pulls data from are refreshed or
updated.
To learn more, see:
Calculated tables in Power BI Desktop
Calculated tables in Analysis Services.
Row-level security
With row-level security, a DAX formula must evaluate to a Boolean TRUE/FALSE condition, defining which rows
can be returned by the results of a query by members of a particular role. For example, for members of the
Sales role, the Customers table with the following DAX formula:
= Customers[Country] = "USA"
Members of the Sales role will only be able to view data for customers in the USA, and aggregates, such as SUM
are returned only for customers in the USA. Row-level security is not available in Power Pivot in Excel.
When defining row-level secuirty by using DAX formula, you are creating an allowed row set. This does not
deny access to other rows; rather, they are simply not returned as part of the allowed row set. Other roles can
allow access to the rows excluded by the DAX formula. If a user is a member of another role, and that role's row-
level security allows access to that particular row set, the user can view data for that row.
Row-level security formulas apply to the specified rows as well as related rows. When a table has multiple
relationships, filters apply security for the relationship that is active. Row-level security formulas will be
intersected with other formulas defined for related tables.
To learn more, see:
Row-level security (RLS) with Power BI
Roles in Analysis Services
Queries
DAX queries can be created and run in SQL Server Management Studio (SSMS) and open-source tools like DAX
Studio (daxstudio.org). Unlike DAX calculation formulas, which can only be created in tabular data models, DAX
queries can also be run against Analysis Services Multidimensional models. DAX queries are often easier to
write and more efficient than Multidimensional Data Expressions (MDX) queries.
A DAX query is a statement, similar to a SELECT statement in T-SQL. The most basic type of DAX query is an
evaluate statement. For example,
EVALUATE
( FILTER ( 'DimProduct', [SafetyStockLevel] < 200 ) )
ORDER BY [EnglishProductName] ASC
Returns in Results a table listing only those products with a SafetyStockLevel less than 200, in ascending order
by EnglishProductName.
You can create measures as part of the query. Measures exist only for the duration of the query. To learn more,
see DAX queries.
Formulas
DAX formulas are essential for creating calculations in calculated columns and measures, and securing your data
by using row-level security. To create formulas for calculated columns and measures, use the formula bar along
the top of the model designer window or the DAX Editor. To create formulas for row-level security, use the Role
Manager or Manage roles dialog box. Information in this section is meant to get you started with understanding
the basics of DAX formulas.
Formula basics
DAX formulas can be very simple or quite complex. The following table shows some examples of simple
formulas that could be used in a calculated column.
F O RM UL A DEF IN IT IO N
= [Column1] + [Column2] Adds the values in the same row of [Column1] and
[Column2] and puts the results in the calculated column of
the same row.
Whether the formula you create is simple or complex, you can use the following steps when building a formula:
1. Each formula must begin with an equal sign (=).
2. You can either type or select a function name, or type an expression.
3. Begin to type the first few letters of the function or name you want, and AutoComplete displays a list of
available functions, tables, and columns. Press TAB to add an item from the AutoComplete list to the
formula.
You can also click the Fx button to display a list of available functions. To select a function from the
dropdown list, use the arrow keys to highlight the item, and click OK to add the function to the formula.
4. Supply the arguments to the function by selecting them from a dropdown list of possible tables and
columns, or by typing in values.
5. Check for syntax errors: ensure that all parentheses are closed and columns, tables and values are
referenced correctly.
6. Press ENTER to accept the formula.
NOTE
In a calculated column, as soon as you enter the formula and the formula is validated, the column is populated with
values. In a measure, pressing ENTER saves the measure definition with the table. If a formula is invalid, an error is
displayed.
In this example, let's look at a formula in a measure named Days in Current Quar ter :
This measure is used to create a comparison ratio between an incomplete period and the previous period. The
formula must take into account the proportion of the period that has elapsed, and compare it to the same
proportion in the previous period. In this case, [Days Current Quarter to Date]/[Days in Current Quarter] gives
the proportion elapsed in the current period.
This formula contains the following elements:
F O RM UL A EL EM EN T DESC RIP T IO N
[Date] Specifies the Date column in the Date table. Columns are in
brackets.
F O RM UL A EL EM EN T DESC RIP T IO N
LASTDATE The LASTDATE function returns the last date of the quarter.
Functions
A function is a named formula within an expression. Most functions have required and optional arguments, also
known as parameters, as input. When the function is executed, a value is returned. DAX includes functions you
can use to perform calculations using dates and times, create conditional values, work with strings, perform
lookups based on relationships, and the ability to iterate over a table to perform recursive calculations. If you are
familiar with Excel formulas, many of these functions will appear very similar; however, DAX formulas are
different in the following important ways:
A DAX function always references a complete column or a table. If you want to use only particular values
from a table or column, you can add filters to the formula.
If you need to customize calculations on a row-by-row basis, DAX provides functions that let you use the
current row value or a related value as a kind of parameter, to perform calculations that vary by context.
To understand how these functions work, see Context in this article.
DAX includes many functions that return a table, rather than a value. The table is not displayed in a
reporting client, but is used to provide input to other functions. For example, you can retrieve a table and
then count the distinct values in it, or calculate dynamic sums across filtered tables or columns.
DAX functions include a variety of time intelligence functions. These functions let you define or select date
ranges, and perform dynamic calculations based on these dates or range. For example, you can compare
sums across parallel periods.
Aggregation functions
Aggregation functions calculate a (scalar) value such as count, sum, average, minimum, or maximum for all rows
in a column or table as defined by the expression. To learn more, see Aggregation functions.
Date and time functions
The date and time functions in DAX are similar to date and time functions in Microsoft Excel. However, DAX
functions are based on a datetime data type starting March 1, 1900. To learn more, see Date and time
functions.
Filter functions
The filter functions in DAX return specific data types, look up values in related tales, and filter by related values.
The lookup functions work by using tables and relationships, like a database. The filtering functions let you
manipulate data context to create dynamic calculations. To learn more, see Filter functions.
Financial functions
The financial functions in DAX are used in formulas that perform financial calculations, such as net present value
and rate of return. These functions are similar to financial functions used in Microsoft Excel. To learn more, see
Financial functions.
Information functions
An information function looks at the cell or row that is provided as an argument and tells you whether the value
matches the expected type. For example, the ISERROR function returns TRUE if the value that you reference
contains an error. To learn more, see Information functions.
Logical functions
Logical functions act upon an expression to return information about the values in the expression. For example,
the TRUE function lets you know whether an expression that you are evaluating returns a TRUE value. To learn
more, see Logical functions.
Mathematical and trigonometric functions
The mathematical functions in DAX are very similar to the Excel mathematical and trigonometric functions.
Some minor differences exist in the numeric data types used by DAX functions. To learn more, see Math and trig
functions.
Other functions
These functions perform unique actions that cannot be defined by any of the categories most other functions
belong to. To learn more, see Other functions.
Relationship functions
Relationship functions in DAX allow you to return values from another related table, specify a particular
relationship to use in an expression, and specify cross filtering direction. To learn more, see Relationship
functions.
Statistical functions
Statistical functions calculate values related to statistical distributions and probability, such as standard deviation
and number of permutations. To learn more, see Statistical functions.
Text functions
Text functions in DAX are very similar to their counterparts in Excel. You can return part of a string, search for
text within a string, or concatenate string values. DAX also provides functions for controlling the formats for
dates, times, and numbers. To learn more, see Text functions.
Time intelligence functions
The time intelligence functions provided in DAX let you create calculations that use built-in knowledge about
calendars and dates. By using time and date ranges in combination with aggregations or calculations, you can
build meaningful comparisons across comparable time periods for sales, inventory, and so on. To learn more,
see Time intelligence functions (DAX).
Table manipulation functions
These functions return a table or manipulate existing tables. For example, by using ADDCOLUMNS you can add
calculated columns to a specified table, or you can return a summary table over a set of groups with the
SUMMARIZECOLUMNS function. To learn more, see Table manipulation functions.
Variables
You can create variables within an expression by using VAR. VAR is technically not a function, it's a keyword to
store the result of an expression as a named variable. That variable can then be passed as an argument to other
measure expressions. For example:
VAR
TotalQty = SUM ( Sales[Quantity] )
Return
IF (
TotalQty > 1000,
TotalQty * 0.95,
TotalQty * 1.25
)
In this example, TotalQty can be passed as a named variable to other expressions. Variables can be of any scalar
data type, including tables. Using variables in your DAX formulas can be incredibly powerful.
Data types
You can import data into a model from many different data sources that might support different data types.
When you import data into a model, the data is converted to one of the tabular model data types. When the
model data is used in a calculation, the data is then converted to a DAX data type for the duration and output of
the calculation. When you create a DAX formula, the terms used in the formula will automatically determine the
value data type returned.
DAX supports the following data types:
Whole Number A 64 bit (eight-bytes) integer value 1, 2 Numbers that have no decimal places.
Integers can be positive or negative
numbers, but must be whole numbers
between -9,223,372,036,854,775,808
(-2^63) and
9,223,372,036,854,775,807 (2^63-1).
DATA T Y P E IN M O DEL DATA T Y P E IN DA X DESC RIP T IO N
Decimal Number A 64 bit (eight-bytes) real number 1, 2 Real numbers are numbers that can
have decimal places. Real numbers
cover a wide range of values:
Zero
Tabular data models also include the Table data type as the input or output to many DAX functions. For example,
the FILTER function takes a table as input and outputs another table that contains only the rows that meet the
filter conditions. By combining table functions with aggregation functions, you can perform complex calculations
over dynamically defined data sets.
While data types are typically automatically set, it is important to understand data types and how they apply, in-
particular, to DAX formulas. Errors in formulas or unexpected results, for example, are often caused by using a
particular operator that cannot be used with a data type specified in an argument. For example, the formula,
= 1 & 2 , returns a string result of 12. The formula, = "1" + "2" , however, returns an integer result of 3.
Context
Context is an important concept to understand when creating DAX formulas. Context is what enables you to
perform dynamic analysis, as the results of a formula change to reflect the current row or cell selection and also
any related data. Understanding context and using context effectively are critical for building high-performing,
dynamic analyses, and for troubleshooting problems in formulas.
Formulas in tabular models can be evaluated in a different context, depending on other design elements:
Filters applied in a PivotTable or report
Filters defined within a formula
Relationships specified by using special functions within a formula
There are different types of context: row context, query context, and filter context.
Row context
Row context can be thought of as "the current row". If you create a formula in a calculated column, the row
context for that formula includes the values from all columns in the current row. If the table is related to another
table, the content also includes all the values from the other table that are related to the current row.
For example, suppose you create a calculated column, = [Freight] + [Tax] , that adds together values from two
columns, Freight and Tax, from the same table. This formula automatically gets only the values from the current
row in the specified columns.
Row context also follows any relationships that have been defined between tables, including relationships
defined within a calculated column by using DAX formulas, to determine which rows in related tables are
associated with the current row.
For example, the following formula uses the RELATED function to fetch a tax value from a related table, based on
the region that the order was shipped to. The tax value is determined by using the value for region in the current
table, looking up the region in the related table, and then getting the tax rate for that region from the related
table.
= [Freight] + RELATED('Region'[TaxRate])
This formula gets the tax rate for the current region from the Region table and adds it to the value of the Freight
column. In DAX formulas, you do not need to know or specify the specific relationship that connects the tables.
Multiple row context
DAX includes functions that iterate calculations over a table. These functions can have multiple current rows,
each with its own row context. In essence, these functions let you create formulas that perform operations
recursively over an inner and outer loop.
For example, suppose your model contains a Products table and a Sales table. Users might want to go through
the entire sales table, which is full of transactions involving multiple products, and find the largest quantity
ordered for each product in any one transaction.
With DAX you can build a single formula that returns the correct value, and the results are automatically
updated any time a user adds data to the tables.
= MAXX(FILTER(Sales,[ProdKey] = EARLIER([ProdKey])),Sales[OrderQty])
When a formula is evaluated, the model designer first checks for general syntax, and then checks the names of
columns and tables that you provide against possible columns and tables in the current context. If the name is
ambiguous or if the column or table cannot be found, you will get an error on your formula (an #ERROR string
instead of a data value in cells where the error occurs). To learn more about naming requirements for tables,
columns, and other objects, see Naming Requirements in DAX syntax.
Table relationships
By creating relationships between tables, you gain the ability for related values in other tables to be used in
calculations. For example, you can use a calculated column to determine all the shipping records related to the
current reseller, and then sum the shipping costs for each. In many cases, however, a relationship might not be
necessary. You can use the LOOKUPVALUE function in a formula to return the value in result_columnName for
the row that meets criteria specified in the search_column and search_value arguments.
Many DAX functions require that a relationship exist between the tables, or among multiple tables, in order to
locate the columns that you have referenced and return results that make sense. Other functions will attempt to
identify the relationship; however, for best results you should always create a relationship where possible.
Tabular data models support multiple relationships among tables. To avoid confusion or incorrect results, only
one relationship at a time is designated as the active relationship, but you can change the active relationship as
necessary to traverse different connections in the data in calculations. USERELATIONSHIP function can be used
to specify one or more relationships to be used in a specific calculation.
It's important to observe these formula design rules when using relationships:
When tables are connected by a relationship, you must ensure the two columns used as keys have values
that match. Referential integrity is not enforced, therefore it is possible to have non-matching values in a
key column and still create a relationship. If this happens, you should be aware that blank values or non-
matching values might affect the results of formulas.
When you link tables in your model by using relationships, you enlarge the scope, or context, in which
your formulas are evaluated. Changes in context resulting from the addition of new tables, new
relationships, or from changes in the active relationship can cause your results to change in ways that
you might not anticipate. To learn more, see Context in this article.
Updates
DAX is constantly being improved. New and updated functions are released with the next available update,
which is usually monthly. Services are updated first, followed by installed applications like Power BI Desktop,
Excel, SQL Server Management Studio (SSMS), and Analysis Services project extension for Visual Studio (SSDT).
SQL Server Analysis Services is updated with the next cumulative update. New functions are first announced
and described in the DAX function reference coinciding with Power BI Desktop updates.
Not all functions are supported in earlier versions of SQL Server Analysis Services and Excel.
Troubleshooting
If you get an error when defining a formula, the formula might contain either a syntactic error, semantic error,
or calculation error.
Syntactic errors are the easiest to resolve. They typically involve a missing parenthesis or comma.
The other type of error occurs when the syntax is correct, but the value or a column referenced does not make
sense in the context of the formula. Such semantic and calculation errors might be caused by any of the
following problems:
The formula refers to a non-existing column, table, or function.
The formula appears to be correct, but when the data engine fetches the data, it finds a type mismatch and
raises an error.
The formula passes an incorrect number or type of arguments to a function.
The formula refers to a different column that has an error, and therefore its values are invalid.
The formula refers to a column that has not been processed, meaning it has metadata but no actual data to
use for calculations.
In the first four cases, DAX flags the entire column that contains the invalid formula. In the last case, DAX grays
out the column to indicate that the column is in an unprocessed state.
Power BI Desktop is a free data modeling and reporting application. The model designer includes a DAX editor
for creating DAX calculation formulas.
Power Pivot in Excel
The Power Pivot in Excel models designer includes a DAX editor for creating DAX calculation formulas.
Visual Studio
Visual Studio with Analysis Services projects extension (VSIX) is used to create Analysis Services model projects.
Tabular model designer, installed with the projects extension includes a DAX editor.
SQL Server Management Studio
SQL Server Management Studio (SSMS) is an essential tool for working with Analysis Services. SSMS includes a
DAX query editor for querying both tabular and multidimensional models.
DAX Studio
DAX Studio is an open-source client tool for creating and running DAX queries against Analysis Services, Power
BI Desktop, and Power Pivot in Excel models.
Tabular Editor
Tabular Editor is an open-source tool that provides an intuitive, hierarchical view of every object in tabular
model metadata. Tabular Editor includes a DAX Editor with syntax highlighting, which provides an easy way to
edit measures, calculated column, and calculated table expressions.
Learning resources
When learning DAX, it's best to use the application you'll be using to create your data models. Analysis Services,
Power BI Desktop, and Power Pivot in Excel all have articles and tutorials that include lessons on creating
measures, calculated columns, and row-filters by using DAX. Here are some additional resources:
Videos
Use DAX in Power BI Desktop path in Microsoft Learn.
The Definitive Guide to DAX by Alberto Ferrari and Marco Russo (Microsoft Press). Now in its second edition,
this extensive guide provides basics to innovative high-performance techniques for beginning data modelers
and BI professionals.
Community
DAX has a vibrant community always willing to share their expertise. Microsoft Power BI Community has a
special discussion forum just for DAX, DAX Commands and Tips.
Videos
8/25/2021 • 2 minutes to read
Whether you're using Power BI Desktop, Power Pivot in Excel, or Analysis Services, learning Data Analysis
Expressions (DAX) is essential to creating effective data models. Here are some videos to help you get started
using this powerful expression language.
DAX 101
In this DAX 101 video, Microsoft Partner, Alberto Ferrari introduces essential concepts in DAX. With practical and
clear examples, you will learn about measures, calculated columns, and basic data modeling expressions with
DAX.
Advanced DAX
In this advanced DAX video, Microsoft Partner, Alberto Ferrari describes DAX theory, filter and row context, and
other essential concepts in DAX.
DAX sample model
8/25/2021 • 2 minutes to read
The Adventure Works DW 2020 Power BI Desktop sample model is designed to support your DAX learning.
The model is based on the Adventure Works data warehouse sample for AdventureWorksDW2017—however,
the data has been modified to suit the objectives of the sample model.
The sample model does not contain any DAX formulas. It does however support hundreds or even thousands of
potential calculation formulas and queries. Some function examples, like those in CALCULATE, DATESBETWEEN,
DATESIN PERIOD, IF, and LOOKUPVALUE can be added to the sample model without modification. We're working
on including more examples in other function reference articles that work with the sample model.
Scenario
The Adventure Works company represents a bicycle manufacturer that sells bicycles and accessories to global
markets. The company has their data warehouse data stored in an Azure SQL Database.
Model structure
The model has seven tables:
TA B L E DESC RIP T IO N
Date There are three relationships between the Date and Sales
tables, for order date, ship date, and due date. The order
date relationship is active. The company's reports sales using
a fiscal year that commences on July 1 of each year. The
table is marked as a date table using the Date column.
Sales Stores rows at sales order line grain. All financial values are in
US dollars (USD). The earliest order date is July 1, 2017, and
the latest order date is June 15, 2020.
Sales Order Describes sales order and order line numbers, and also the
sales channel, which is either Reseller or Internet . This
table has a one-to-one relationship with the Sales table.
TA B L E DESC RIP T IO N
Sales Territor y Sales territories are organized into groups (North America,
Europe, and Pacific), countries, and regions. Only the United
States sells products at the region level.
Download sample
Download the Power BI Desktop sample model file here.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Appropriate use of error functions
8/25/2021 • 2 minutes to read
As a data modeler, when you write a DAX expression that might raise an evaluation-time error, you can consider
using two helpful DAX functions.
The ISERROR function, which takes a single expression and returns TRUE if that expression results in error.
The IFERROR function, which takes two expressions. Should the first expression result in error, the value for
the second expression is returned. It is in fact a more optimized implementation of nesting the ISERROR
function inside an IF function.
However, while these functions can be helpful and can contribute to writing easy-to-understand expressions,
they can also significantly degrade the performance of calculations. It can happen because these functions
increase the number of storage engine scans required.
Most evaluation-time errors are due to unexpected BLANKs or zero values, or invalid data type conversion.
Recommendations
It's better to avoid using the ISERROR and IFERROR functions. Instead, apply defensive strategies when
developing the model and writing expressions. Strategies can include:
Ensuring quality data is loaded into the model: Use Power Query transformations to remove or
substitute invalid or missing values, and to set correct data types. A Power Query transformation can also
be used to filter rows when errors, like invalid data conversion, occur.
Data quality can also be controlled by setting the model column Is Nullable property to Off, which will
fail the data refresh should BLANKs be encountered. If this failure occurs, data loaded as a result of a
successful refresh will remain in the tables.
Using the IF function: The IF function logical test expression can determine whether an error result
would occur. Note, like the ISERROR and IFERROR functions, this function can result in additional storage
engine scans, but will likely perform better than them as no error needs to be raised.
Using error-tolerant functions: Some DAX functions will test and compensate for error conditions.
These functions allow you to enter an alternate result that would be returned instead. The DIVIDE function
is one such example. For additional guidance about this function, read the DAX: DIVIDE function vs divide
operator (/) article.
Example
The following measure expression tests whether an error would be raised. It returns BLANK in this instance
(which is the case when you do not provide the IF function with a value-if-false expression).
Profit Margin
= IF(ISERROR([Profit] / [Sales]))
This next version of the measure expression has been improved by using the IFERROR function in place of the IF
and ISERROR functions.
Profit Margin
= IFERROR([Profit] / [Sales], BLANK())
However, this final version of the measure expression achieves the same outcome, yet more efficiently and
elegantly.
Profit Margin
= DIVIDE([Profit], [Sales])
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Avoid converting BLANKs to values
8/25/2021 • 2 minutes to read
As a data modeler, when writing measure expressions you might come across cases where a meaningful value
can't be returned. In these instances, you may be tempted to return a value—like zero—instead. It's suggested
you carefully determine whether this design is efficient and practical.
Consider the following measure definition that explicitly converts BLANK results to zero.
Consider another measure definition that also converts BLANK results to zero.
Profit Margin =
DIVIDE([Profit], [Sales], 0)
The DIVIDE function divides the Profit measure by the Sales measure. Should the result be zero or BLANK, the
third argument—the alternate result (which is optional)—is returned. In this example, because zero is passed as
the alternate result, the measure is guaranteed to always return a value.
These measure designs are inefficient and lead to poor report designs.
When they're added to a report visual, Power BI attempts to retrieve all groupings within the filter context. The
evaluation and retrieval of large query results often leads to slow report rendering. Each example measure
effectively turns a sparse calculation into a dense one, forcing Power BI to use more memory than necessary.
Also, too many groupings often overwhelm your report users.
Let's see what happens when the Profit Margin measure is added to a table visual, grouping by customer.
The table visual displays an overwhelming number of rows. (There are in fact 18,484 customers in the model,
and so the table attempts to display all of them.) Notice that the customers in view haven't achieved any sales.
Yet, because the Profit Margin measure always returns a value, they are displayed.
NOTE
When there are too many data points to display in a visual, Power BI may use data reduction strategies to remove or
summarize large query results. For more information, see Data point limits and strategies by visual type.
Let's see what happens when the Profit Margin measure definition is improved. It now returns a value only
when the Sales measure isn't BLANK (or zero).
Profit Margin =
DIVIDE([Profit], [Sales])
The table visual now displays only customers who have made sales within the current filter context. The
improved measure results in a more efficient and practical experience for your report users.
TIP
When necessary, you can configure a visual to display all groupings (that return values or BLANK) within the filter context
by enabling the Show Items With No Data option.
Recommendation
It's recommended that your measures return BLANK when a meaningful value cannot be returned.
This design approach is efficient, allowing Power BI to render reports faster. Also, returning BLANK is better
because report visuals—by default—eliminate groupings when summarizations are BLANK.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Avoid using FILTER as a filter argument
8/25/2021 • 2 minutes to read
As a data modeler, it's common you'll write DAX expressions that need to be evaluated in a modified filter
context. For example, you can write a measure definition to calculate sales for "high margin products". We'll
describe this calculation later in this article.
NOTE
This article is especially relevant for model calculations that apply filters to Import tables.
The CALCULATE and CALCULATETABLE DAX functions are important and useful functions. They let you write
calculations that remove or add filters, or modify relationship paths. It's done by passing in filter arguments,
which are either Boolean expressions, table expressions, or special filter functions. We'll only discuss Boolean
and table expressions in this article.
Consider the following measure definition, which calculates red product sales by using a table expression. It will
replace any filters that might be applied to the Product table.
Red Sales =
CALCULATE(
[Sales],
FILTER('Product', 'Product'[Color] = "Red")
)
The CALCULATE function accepts a table expression returned by the FILTER DAX function, which evaluates its
filter expression for each row of the Product table. It achieves the correct result—the sales result for red
products. However, it could be achieved much more efficiently by using a Boolean expression.
Here's an improved measure definition, which uses a Boolean expression instead of the table expression. The
KEEPFILTERS DAX function ensures any existing filters applied to the Color column are preserved, and not
overwritten.
Red Sales =
CALCULATE(
[Sales],
KEEPFILTERS('Product'[Color] = "Red")
)
It's recommended you pass filter arguments as Boolean expressions, whenever possible. It's because Import
model tables are in-memory column stores. They are explicitly optimized to efficiently filter columns in this way.
There are, however, restrictions that apply to Boolean expressions when they're used as filter arguments. They:
Cannot compare columns to other columns
Cannot reference a measure
Cannot use nested CALCULATE functions
Cannot use functions that scan or return a table
It means that you'll need to use table expressions for more complex filter requirements.
Consider now a different measure definition.
High Margin Product Sales =
CALCULATE(
[Sales],
FILTER(
'Product',
'Product'[ListPrice] > 'Product'[StandardCost] * 2
)
)
The definition of a high margin product is one that has a list price exceeding double its standard cost. In this
example, the FILTER function must be used. It's because the filter expression is too complex for a Boolean
expression.
Here's one more example. The requirement this time is to calculate sales, but only for months that have achieved
a profit.
In this example, the FILTER function must also be used. It's because it requires evaluating the Profit measure to
eliminate those months that didn't achieve a profit. It's not possible to use a measure in a Boolean expression
when it's used as a filter argument.
Recommendations
For best performance, it's recommended you use Boolean expressions as filter arguments, whenever possible.
Therefore, the FILTER function should only be used when necessary. You can use it to perform filter complex
column comparisons. These column comparisons can involve:
Measures
Other columns
Using the OR DAX function, or the OR logical operator (||)
See also
Filter functions (DAX)
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Column and measure references
8/25/2021 • 2 minutes to read
As a data modeler, your DAX expressions will refer to model columns and measures. Columns and measures are
always associated with model tables, but these associations are different, so we have different recommendations
on how you'll reference them in your expressions.
Columns
A column is a table-level object, and column names must be unique within a table. So it's possible that the same
column name is used multiple times in your model—providing they belong to different tables. There's one more
rule: a column name cannot have the same name as a measure name or hierarchy name that exists in the same
table.
In general, DAX will not force using a fully qualified reference to a column. A fully qualified reference means that
the table name precedes the column name.
Here's an example of a calculated column definition using only column name references. The Sales and Cost
columns both belong to a table named Orders .
The same definition can be rewritten with fully qualified column references.
Sometimes, however, you'll be required to use fully qualified column references when Power BI detects
ambiguity. When entering a formula, a red squiggly and error message will alert you. Also, some DAX functions
like the LOOKUPVALUE DAX function, require the use of fully qualified columns.
It's recommended you always fully qualify your column references. The reasons are provided in the
Recommendations section.
Measures
A measure is a model-level object. For this reason, measure names must be unique within the model. However,
in the Fields pane, report authors will see each measure associated with a single model table. This association is
set for cosmetic reasons, and you can configure it by setting the Home Table property for the measure. For
more information, see Measures in Power BI Desktop (Organizing your measures).
It's possible to use a fully qualified measure in your expressions. DAX intellisense will even offer the suggestion.
However, it isn't necessary, and it's not a recommended practice. If you change the home table for a measure,
any expression that uses a fully qualified measure reference to it will break. You'll then need to edit each broken
formula to remove (or update) the measure reference.
It's recommended you never qualify your measure references. The reasons are provided in the
Recommendations section.
Recommendations
Our recommendations are simple and easy to remember:
Always use fully qualified column references
Never use fully qualified measure references
Here's why:
Formula entr y : Expressions will be accepted, as there won't be any ambiguous references to resolve. Also,
you'll meet the requirement for those DAX functions that require fully qualified column references.
Robustness : Expressions will continue to work, even when you change a measure home table property.
Readability : Expressions will be quick and easy to understand—you'll quickly determine that it's a column or
measure, based on whether it's fully qualified or not.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
DIVIDE function vs. divide operator (/)
8/25/2021 • 2 minutes to read
As a data modeler, when you write a DAX expression to divide a numerator by a denominator, you can choose to
use the DIVIDE function or the divide operator (/ - forward slash).
When using the DIVIDE function, you must pass in numerator and denominator expressions. Optionally, you can
pass in a value that represents an alternate result.
The DIVIDE function was designed to automatically handle division by zero cases. If an alternate result is not
passed in, and the denominator is zero or BLANK, the function returns BLANK. When an alternate result is
passed in, it's returned instead of BLANK.
The DIVIDE function is convenient because it saves your expression from having to first test the denominator
value. The function is also better optimized for testing the denominator value than the IF function. The
performance gain is significant since checking for division by zero is expensive. Further using DIVIDE results in a
more concise and elegant expression.
Example
The following measure expression produces a safe division, but it involves using four DAX functions.
Profit Margin =
IF(
OR(
ISBLANK([Sales]),
[Sales] == 0
),
BLANK(),
[Profit] / [Sales]
)
This measure expression achieves the same outcome, yet more efficiently and elegantly.
Profit Margin =
DIVIDE([Profit], [Sales])
Recommendations
It's recommended that you use the DIVIDE function whenever the denominator is an expression that could
return zero or BLANK.
In the case that the denominator is a constant value, we recommend that you use the divide operator. In this
case, the division is guaranteed to succeed, and your expression will perform better because it will avoid
unnecessary testing.
Carefully consider whether the DIVIDE function should return an alternate value. For measures, it's usually a
better design that they return BLANK. Returning BLANK is better because report visuals—by default—eliminate
groupings when summarizations are BLANK. It allows the visual to focus attention on groups where data exists.
When necessary, in Power BI, you can configure the visual to display all groups (that return values or BLANK)
within the filter context by enabling the Show items with no data option.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Use SELECTEDVALUE instead of VALUES
8/25/2021 • 2 minutes to read
As a data modeler, sometimes you might need to write a DAX expression that tests whether a column is filtered
by a specific value.
In earlier versions of DAX, this requirement was safely achieved by using a pattern involving three DAX
functions; IF, HASONEVALUE and VALUES. The following measure definition presents an example. It calculates
the sales tax amount, but only for sales made to Australian customers.
In the example, the HASONEVALUE function returns TRUE only when a single value of the Countr y-Region
column is visible in the current filter context. When it's TRUE, the VALUES function is compared to the literal text
"Australia". When the VALUES function returns TRUE, the Sales measure is multiplied by 0.10 (representing
10%). If the HASONEVALUE function returns FALSE—because more than one value filters the column—the first
IF function returns BLANK.
The use of the HASONEVALUE is a defensive technique. It's required because it's possible that multiple values
filter the Countr y-Region column. In this case, the VALUES function returns a table of multiple rows.
Comparing a table of multiple rows to a scalar value results in an error.
Recommendation
It's recommended that you use the SELECTEDVALUE function. It achieves the same outcome as the pattern
described in this article, yet more efficiently and elegantly.
Using the SELECTEDVALUE function, the example measure definition is now rewritten.
TIP
It's possible to pass an alternate result value into the SELECTEDVALUE function. The alternate result value is returned
when either no filters—or multiple filters—are applied to the column.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Use COUNTROWS instead of COUNT
8/25/2021 • 2 minutes to read
As a data modeler, sometimes you might need to write a DAX expression that counts table rows. The table could
be a model table or an expression that returns a table.
Your requirement can be achieved in two ways. You can use the COUNT function to count column values, or you
can use the COUNTROWS function to count table rows. Both functions will achieve the same result, providing
that the counted column contains no BLANKs.
The following measure definition presents an example. It calculates the number of OrderDate column values.
Sales Orders =
COUNT(Sales[OrderDate])
Providing that the granularity of the Sales table is one row per sales order, and the OrderDate column does
not contain BLANKs, then the measure will return a correct result.
However, the following measure definition is a better solution.
Sales Orders =
COUNTROWS(Sales)
There are three reasons why the second measure definition is better:
It's more efficient, and so it will perform better.
It doesn't consider BLANKs contained in any column of the table.
The intention of formula is clearer, to the point of being self-describing.
Recommendation
When it's your intention to count table rows, it's recommended you always use the COUNTROWS function.
See also
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
Suggestions? Contribute ideas to improve Power BI
Use variables to improve your DAX formulas
8/25/2021 • 3 minutes to read
As a data modeler, writing and debugging some DAX calculations can be challenging. It's common that complex
calculation requirements often involve writing compound or complex expressions. Compound expressions can
involve the use of many nested functions, and possibly the reuse of expression logic.
Using variables in your DAX formulas can help you write more complex and efficient calculations. Variables can
improve performance and reliability, and readability, and reduce complexity.
In this article, we'll demonstrate the first three benefits by using an example measure for year-over-year (YoY)
sales growth. (The formula for YoY sales growth is: period sales fewer sales for the same period last year, divided
by sales for the same period last year.)
Let's start with the following measure definition.
The measure produces the correct result, yet let's now see how it can be improved.
Improve performance
Notice that the formula repeats the expression that calculates "same period last year". This formula is inefficient,
as it requires Power BI to evaluate the same expression twice. The measure definition can be made more
efficient by using a variable, VAR.
The following measure definition represents an improvement. It uses an expression to assign the "same period
last year" result to a variable named SalesPriorYear . The variable is then used twice in the RETURN expression.
The measure continues to produce the correct result, and does so in about half the query time.
Improve readability
In the previous measure definition, notice how the choice of variable name makes the RETURN expression
simpler to understand. The expression is short and self-describing.
Simplify debugging
Variables can also help you debug a formula. To test an expression assigned to a variable, you temporarily
rewrite the RETURN expression to output the variable.
The following measure definition returns only the SalesPriorYear variable. Notice how it comments-out the
intended RETURN expression. This technique allows you to easily revert it back once your debugging is
complete.
Reduce complexity
In earlier versions of DAX, variables were not yet supported. Complex expressions that introduced new filter
contexts were required to use the EARLIER or EARLIEST DAX functions to reference outer filter contexts.
Unfortunately, data modelers found these functions difficult to understand and use.
Variables are always evaluated outside the filters your RETURN expression applies. For this reason, when you
use a variable within a modified filter context, it achieves the same result as the EARLIEST function. The use of
the EARLIER or EARLIEST functions can therefore be avoided. It means you can now write formulas that are less
complex, and that are easier to understand.
Consider the following calculated column definition added to the Subcategor y table. It evaluates a rank for
each product subcategory based on the Subcategor y Sales column values.
The EARLIER function is used to refer to the Subcategor y Sales column value in the current row context.
The calculated column definition can be improved by using a variable instead of the EARLIER function. The
CurrentSubcategor ySales variable stores the Subcategor y Sales column value in the current row context,
and the RETURN expression uses it within a modified filter context.
See also
VAR DAX article
Learning path: Use DAX in Power BI Desktop
Questions? Try asking the Power BI Community
DAX function reference
8/25/2021 • 2 minutes to read
The DAX function reference provides detailed information including syntax, parameters, return values, and
examples for each of the over 250 functions used in Data Analysis Expression (DAX) formulas.
IMPORTANT
Not all DAX functions are supported or included in earlier versions of Power BI Desktop, Analysis Services, and Power
Pivot in Excel.
In this section
New DAX functions - These functions are new or are existing functions that have been significantly updated.
Aggregation functions - These functions calculate a (scalar) value such as count, sum, average, minimum, or
maximum for all rows in a column or table as defined by the expression.
Date and time functions - These functions in DAX are similar to date and time functions in Microsoft Excel.
However, DAX functions are based on the datetime data types used by Microsoft SQL Server.
Filter functions - These functions help you return specific data types, look up values in related tables, and filter
by related values. Lookup functions work by using tables and relationships between them. Filtering functions let
you manipulate data context to create dynamic calculations.
Financial functions - These functions are used in formulas that perform financial calculations, such as net
present value and rate of return.
Information functions - These functions look at a table or column provided as an argument to another function
and returns whether the value matches the expected type. For example, the ISERROR function returns TRUE if
the value you reference contains an error.
Logical functions - These functions return information about values in an expression. For example, the TRUE
function lets you know whether an expression that you are evaluating returns a TRUE value.
Math and Trig functions - Mathematical functions in DAX are similar to Excel's mathematical and trigonometric
functions. However, there are some differences in the numeric data types used by DAX functions.
Other functions - These functions perform unique actions that cannot be defined by any of the categories most
other functions belong to.
Parent and Child functions - These functions help users manage data that is presented as a parent/child
hierarchy in their data models.
Relationship functions - These functions are for managing and utilizing relationships between tables. For
example, you can specify a particular relationship to be used in a calculation.
Statistical functions - These functions calculate values related to statistical distributions and probability, such as
standard deviation and number of permutations.
Table manipulation functions - These functions return a table or manipulate existing tables.
Text functions - With these functions, you can return part of a string, search for text within a string, or
concatenate string values. Additional functions are for controlling the formats for dates, times, and numbers.
Time intelligence functions - These functions help you create calculations that use built-in knowledge about
calendars and dates. By using time and date ranges in combination with aggregations or calculations, you can
build meaningful comparisons across comparable time periods for sales, inventory, and so on.
See also
DAX Syntax Reference
DAX Operator Reference
DAX Parameter-Naming Conventions
New DAX functions
9/15/2021 • 2 minutes to read
DAX is continuously being improved with new functions and functionality to support new features. New
functions and updates are included in service, application, and tool updates which in most cases are monthly.
While functions and functionality are being updated all the time, only those updates that have a visible and
functional change exposed to users are described in documentation. New functions and updates to existing
functions within the past year are shown here.
IMPORTANT
Not all functions are supported in all versions of Power BI Desktop, Analysis Services, and Power Pivot in Excel. New and
updated functions are typically first introduced in Power BI Desktop, and then later in Analysis Services, Power Pivot in
Excel, and tools.
New functions
F UN C T IO N MONT H
Updated functions
F UN C T IO N MONT H DESC RIP T IO N
Aggregation functions calculate a (scalar) value such as count, sum, average, minimum, or maximum for all rows
in a column or table as defined by the expression.
In this category
F UN C T IO N DESC RIP T IO N
COUNTA Counts the number of cells in a column that are not empty.
Returns the approximate number of rows that contain distinct values in a column. This function can query large
amounts of data with potentially better performance than DISTINCTCOUNT, with slight deviation from the exact
result.
Syntax
APPROXIMATEDISTINCTCOUNT(<columnName>)
Parameters
T ERM DESC RIP T IO N
Return value
The approximate number of distinct values in column.
Remarks
The only argument to this function is a column. You can use columns containing any type of data. When the
function finds no rows to count, it returns a BLANK, otherwise it returns the count of distinct values.
AVERAGE
8/25/2021 • 2 minutes to read
Syntax
AVERAGE(<column>)
Parameters
T ERM DEF IN IT IO N
column The column that contains the numbers for which you want
the average.
Return value
Returns a decimal number that represents the arithmetic mean of the numbers in the column.
Remarks
This function takes the specified column as an argument and finds the average of the values in that
column. If you want to find the average of an expression that evaluates to a set of numbers, use the
AVERAGEX function instead.
Nonnumeric values in the column are handled as follows:
If the column contains text, no aggregation can be performed, and the functions returns blanks.
If the column contains logical values or empty cells, those values are ignored.
Cells with the value zero are included.
When you average cells, you must keep in mind the difference between an empty cell and a cell that
contains the value 0 (zero). When a cell contains 0, it is added to the sum of numbers and the row is
counted among the number of rows used as the divisor. However, when a cell contains a blank, the row is
not counted.
Whenever there are no rows to aggregate, the function returns a blank. However, if there are rows, but
none of them meet the specified criteria, the function returns 0. Excel also returns a zero if no rows are
found that meet the conditions.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following formula returns the average of the values in the column, ExtendedSalesAmount, in the table,
InternetSales.
= AVERAGE(InternetSales[ExtendedSalesAmount])
Related functions
The AVERAGEX function can take as its argument an expression that is evaluated for each row in a table. This
enables you to perform calculations and then take the average of the calculated values.
The AVERAGEA function takes a column as its argument, but otherwise is like the Excel function of the same
name. By using the AVERAGEA function, you can calculate a mean on a column that contains empty values.
AVERAGEA
8/25/2021 • 2 minutes to read
Returns the average (arithmetic mean) of the values in a column. Handles text and non-numeric values.
Syntax
AVERAGEA(<column>)
Parameters
T ERM DEF IN IT IO N
column A column that contains the values for which you want the
average.
Return value
A decimal number.
Remarks
The AVERAGEA function takes a column and averages the numbers in it, but also handles non-numeric
data types according to the following rules:
Values that evaluates to TRUE count as 1.
Values that evaluate to FALSE count as 0 (zero).
Values that contain non-numeric text count as 0 (zero).
Empty text ("") counts as 0 (zero).
If you do not want to include logical values and text representations of numbers in a reference as part of
the calculation, use the AVERAGE function.
Whenever there are no rows to aggregate, the function returns a blank. However, if there are rows, but
none of them meet the specified criteria, the function returns 0. Microsoft Excel also returns a zero if no
rows are found that meet the conditions.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns the average of non-blank cells in the referenced column, given the following
table. If you used the AVERAGE function, the mean would be 21/2; with the AVERAGEA function, the result is
22/5.
T RA N SA C T IO N ID A M O UN T RESULT
0000123 1 Counts as 1
T RA N SA C T IO N ID A M O UN T RESULT
0000124 20 Counts as 20
0000126 Counts as 0
= AVERAGEA([Amount])
See also
AVERAGE function
AVERAGEX function
Statistical functions
AVERAGEX
8/25/2021 • 2 minutes to read
Calculates the average (arithmetic mean) of a set of expressions evaluated over a table.
Syntax
AVERAGEX(<table>,<expression>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
The AVERAGEX function enables you to evaluate expressions for each row of a table, and then take the
resulting set of values and calculate its arithmetic mean. Therefore, the function takes a table as its first
argument, and an expression as the second argument.
In all other respects, AVERAGEX follows the same rules as AVERAGE. You cannot include non-numeric or
null cells. Both the table and expression arguments are required.
When there are no rows to aggregate, the function returns a blank. When there are rows, but none of
them meet the specified criteria, then the function returns 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example calculates the average freight and tax on each order in the InternetSales table, by first
summing Freight plus TaxAmt in each row, and then averaging those sums.
If you use multiple operations in the expression used as the second argument, you must use parentheses to
control the order of calculations. For more information, see DAX Syntax Reference.
See also
AVERAGE function
AVERAGEA function
Statistical functions
COUNT
8/25/2021 • 2 minutes to read
The COUNT function counts the number of cells in a column that contain non-blank values.
Syntax
COUNT(<column>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
The only argument allowed to this function is a column. The COUNT function counts rows that contain
the following kinds of values:
Numbers
Dates
Strings
When the function finds no rows to count, it returns a blank.
Blank values are skipped. TRUE/FALSE values are not supported.
If you want to evaluate a column of TRUE/FALSE values, use the COUNTA function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
For best practices when using COUNT, see Use COUNTROWS instead of COUNT.
Example
The following example shows how to count the number of values in the column, ShipDate.
= COUNT([ShipDate])
See also
COUNTA function
COUNTAX function
COUNTX function
Statistical functions
COUNTA
8/25/2021 • 2 minutes to read
The COUNTA function counts the number of cells in a column that are not empty.
Syntax
COUNTA(<column>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
When the function does not find any rows to count, the function returns a blank.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns all rows in the Reseller table that have any kind of value in the column that
stores phone numbers. Because the table name does not contain any spaces, the quotation marks are optional.
= COUNTA('Reseller'[Phone])
See also
COUNT function
COUNTAX function
COUNTX function
Statistical functions
COUNTAX
8/25/2021 • 2 minutes to read
The COUNTAX function counts nonblank results when evaluating the result of an expression over a table. That is,
it works just like the COUNTA function, but is used to iterate through the rows in a table and count rows where
the specified expressions results in a non-blank result.
Syntax
COUNTAX(<table>,<expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A whole number.
Remarks
Like the COUNTA function, the COUNTAX function counts cells containing any type of information,
including other expressions. For example, if the column contains an expression that evaluates to an empty
string, the COUNTAX function treats that result as non-blank. Usually the COUNTAX function does not
count empty cells but in this case the cell contains a formula, so it is counted.
Whenever the function finds no rows to aggregate, the function returns a blank.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example counts the number of nonblank rows in the column, Phone, using the table that results
from filtering the Reseller table on [Status] = Active .
= COUNTAX(FILTER('Reseller',[Status]="Active"),[Phone])
See also
COUNT function
COUNTA function
COUNTX function
Statistical functions
COUNTBLANK
8/25/2021 • 2 minutes to read
Syntax
COUNTBLANK(<column>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number. If no rows are found that meet the condition, blanks are returned.
Remarks
The only argument allowed to this function is a column. You can use columns containing any type of data,
but only blank cells are counted. Cells that have the value zero (0) are not counted, as zero is considered a
numeric value and not a blank.
Whenever there are no rows to aggregate, the function returns a blank. However, if there are rows, but
none of them meet the specified criteria, the function returns 0. Microsoft Excel also returns a zero if no
rows are found that meet the conditions.
In other words, if the COUNTBLANK function finds no blanks, the result will be zero, but if there are no
rows to check, the result will be blank.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows how to count the number of rows in the table Reseller that have blank values for
BankName.
= COUNTBLANK(Reseller[BankName])
See also
COUNT function
COUNTA function
COUNTAX function
COUNTX function
Statistical functions
COUNTROWS
8/25/2021 • 2 minutes to read
The COUNTROWS function counts the number of rows in the specified table, or in a table defined by an
expression.
Syntax
COUNTROWS([<table>])
Parameters
T ERM DEF IN IT IO N
table (Optional) The name of the table that contains the rows to
be counted, or an expression that returns a table. When not
provided, the default value is the home table of the current
expression.
Return value
A whole number.
Remarks
This function can be used to count the number of rows in a base table, but more often is used to count
the number of rows that result from filtering a table, or applying context to a table.
Whenever there are no rows to aggregate, the function returns a blank. However, if there are rows, but
none of them meet the specified criteria, the function returns 0. Microsoft Excel also returns a zero if no
rows are found that meet the conditions.
To learn more about best practices when using COUNT and COUNTROWS, see Use COUNTROWS instead
of COUNT in DAX.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following example shows how to count the number of rows in the table Orders. The expected result is
52761.
= COUNTROWS('Orders')
Example 2
The following example demonstrates how to use COUNTROWS with a row context. In this scenario, there are
two sets of data that are related by order number. The table Reseller contains one row for each reseller; the table
ResellerSales contains multiple rows for each order, each row containing one order for a particular reseller. The
tables are connected by a relationship on the column, ResellerKey.
The formula gets the value of ResellerKey and then counts the number of rows in the related table that have the
same reseller ID. The result is output in the column, CalculatedColumn1 .
= COUNTROWS(RELATEDTABLE(ResellerSales))
1 73
2 70
3 394
See also
COUNT function
COUNTA function
COUNTAX function
COUNTX function
Statistical functions
COUNTX
8/25/2021 • 2 minutes to read
Counts the number of rows that contain a non-blank value or an expression that evaluates to a non-blank value,
when evaluating an expression over a table.
Syntax
COUNTX(<table>,<expression>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer.
Remarks
The COUNTX function takes two arguments. The first argument must always be a table, or any expression
that returns a table. The second argument is the column or expression that is searched by COUNTX.
The COUNTX function counts only values, dates, or strings. If the function finds no rows to count, it
returns a blank.
If you want to count logical values, use the COUNTAX function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following formula returns a count of all rows in the Product table that have a list price.
= COUNTX(Product,[ListPrice])
Example 2
The following formula illustrates how to pass a filtered table to COUNTX for the first argument. The formula
uses a filter expression to get only the rows in the Product table that meet the condition, ProductSubCategory =
"Caps", and then counts the rows in the resulting table that have a list price. The FILTER expression applies to the
table Products but uses a value that you look up in the related table, ProductSubCategory.
= COUNTX(FILTER(Product,RELATED(ProductSubcategory[EnglishProductSubcategoryName])="Caps"),
Product[ListPrice])
See also
COUNT function
COUNTA function
COUNTAX function
Statistical functions
DISTINCTCOUNT
8/25/2021 • 2 minutes to read
Syntax
DISTINCTCOUNT(<column>)
Parameters
T ERM DESC RIP T IO N
Return value
The number of distinct values in column.
Remarks
The only argument allowed to this function is a column. You can use columns containing any type of data.
When the function finds no rows to count, it returns a BLANK, otherwise it returns the count of distinct
values.
DISTINCTCOUNT function includes the BLANK value. To skip the BLANK value, use the
DISTINCTCOUNTNOBLANK function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows how to count the number of distinct sales orders in the column
ResellerSales_USD[SalesOrderNumber].
= DISTINCTCOUNT(ResellerSales_USD[SalesOrderNumber])
Using the above measure in a table with calendar year in the side and product category on top returns the
following results:
C O M P O N EN T GRA N D
RO W L A B EL S A C C ESSO RIES B IK ES C LOT H IN G S - TOTA L
1 1
In the above example, note that the rows Grand Total numbers do not add up, this happens because the same
order might contain line items, in the same order, from different product categories.
See also
COUNT function
COUNTA function
COUNTAX function
COUNTX function
Statistical functions
DISTINCTCOUNTNOBLANK
8/25/2021 • 2 minutes to read
Syntax
DISTINCTCOUNTNOBLANK (<column>)
Parameters
T ERM DESC RIP T IO N
Return value
The number of distinct values in column.
Remarks
Unlike DISTINCTCOUNT function, DISTINCTCOUNTNOBLANK does not include the BLANK value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows how to count the number of distinct sales orders in the column
ResellerSales_USD[SalesOrderNumber].
= DISTINCTCOUNT(ResellerSales_USD[SalesOrderNumber])
DAX query
EVALUATE
ROW(
"DistinctCountNoBlank", DISTINCTCOUNTNOBLANK(DimProduct[EndDate]),
"DistinctCount", DISTINCTCOUNT(DimProduct[EndDate])
)
[ DIST IN C TC O UN T N O B L A N K ] [ DIST IN C TC O UN T ]
2 3
See also
DISTINCTCOUNT
MAX
8/25/2021 • 2 minutes to read
Syntax
MAX(<column>)
MAX(<expression1>, <expression2>)
Parameters
T ERM DEF IN IT IO N
column The column in which you want to find the largest value.
Return value
The largest value.
Remarks
When comparing two expressions, blank is treated as 0 when comparing. That is, Max(1, Blank() ) returns
1, and Max( -1, Blank() ) returns 0. If both arguments are blank, MAX returns a blank. If either expression
returns a value which is not allowed, MAX returns an error.
TRUE/FALSE values are not supported. If you want to evaluate a column of TRUE/FALSE values, use the
MAXA function.
Example 1
The following example returns the largest value found in the ExtendedAmount column of the InternetSales table.
= MAX(InternetSales[ExtendedAmount])
Example 2
The following example returns the largest value between the result of two expressions.
= Max([TotalSales], [TotalPurchases])
See also
MAXA function
MAXX function
Statistical functions
MAXA
8/25/2021 • 2 minutes to read
Syntax
MAXA(<column>)
Parameters
T ERM DEF IN IT IO N
column The column in which you want to find the largest value.
Return value
The largest value.
Remarks
The MAXA function takes as argument a column, and looks for the largest value among the following
types of values:
Numbers
Dates
Logical values, such as TRUE and FALSE. Rows that evaluate to TRUE count as 1; rows that evaluate to
FALSE count as 0 (zero).
Empty cells are ignored. If the column contains no values that can be used, MAXA returns 0 (zero).
If you want to compare text values, use the MAX function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following example returns the greatest value from a calculated column, named ResellerMargin , that
computes the difference between list price and reseller price.
= MAXA([ResellerMargin])
Example 2
The following example returns the largest value from a column that contains dates and times. Therefore, this
formula gets the most recent transaction date.
= MAXA([TransactionDate])
See also
MAX function
MAXX function
Statistical functions
MAXX
8/25/2021 • 2 minutes to read
Evaluates an expression for each row of a table and returns the largest value.
Syntax
MAXX(<table>,<expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
The largest value.
Remarks
The table argument to the MAXX function can be a table name, or an expression that evaluates to a table.
The second argument indicates the expression to be evaluated for each row of the table.
Of the values to evaluate, only the following are counted:
Numbers
Texts
Dates
Blank values are skipped. TRUE/FALSE values are not supported.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following formula uses an expression as the second argument to calculate the total amount of taxes and
shipping for each order in the table, InternetSales. The expected result is 375.7184.
Example 2
The following formula first filters the table InternetSales, by using a FILTER expression, to return a subset of
orders for a specific sales region, defined as [SalesTerritory] = 5. The MAXX function then evaluates the
expression used as the second argument for each row of the filtered table, and returns the highest amount for
taxes and shipping for just those orders. The expected result is 250.3724.
See also
MAX function
MAXA function
Statistical functions
MIN
8/25/2021 • 2 minutes to read
Syntax
MIN(<column>)
MIN(<expression1>, <expression2>)
Parameters
T ERM DEF IN IT IO N
column The column in which you want to find the smallest value.
Return value
The smallest value.
Remarks
The MIN function takes a column or two expressions as an argument, and returns the smallest value. The
following types of values in the columns are counted:
Numbers
Texts
Dates
Blanks
When comparing expressions, blank is treated as 0 when comparing. That is, Min(1,Blank() ) returns 0,
and Min( -1, Blank() ) returns -1. If both arguments are blank, MIN returns a blank. If either expression
returns a value which is not allowed, MIN returns an error.
TRUE/FALSE values are not supported. If you want to evaluate a column of TRUE/FALSE values, use the
MINA function.
Example 1
The following example returns the smallest value from the calculated column, ResellerMargin.
= MIN([ResellerMargin])
Example 2
The following example returns the smallest value from a column that contains dates and times, TransactionDate.
This formula therefore returns the date that is earliest.
= MIN([TransactionDate])
Example 3
The following example returns the smallest value from the result of two scalar expressions.
= Min([TotalSales], [TotalPurchases])
See also
MINA function
MINX function
Statistical functions
MINA
8/25/2021 • 2 minutes to read
Syntax
MINA(<column>)
Parameters
T ERM DEF IN IT IO N
column The column for which you want to find the minimum value.
Return value
The smallest value.
Remarks
The MINA function takes as argument a column that contains numbers, and determines the smallest
value as follows:
If the column contains no values, MINA returns 0 (zero).
Rows in the column that evaluates to logical values, such as TRUE and FALSE are treated as 1 if TRUE
and 0 (zero) if FALSE.
Empty cells are ignored.
If you want to compare text values, use the MIN function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following expression returns the minimum freight charge from the table, InternetSales.
= MINA(InternetSales[Freight])
Example 2
The following expression returns the minimum value in the column, PostalCode. Because the data type of the
column is text, the function does not find any values, and the formula returns zero (0).
= MINA([PostalCode])
See also
MIN function
MINX function
Statistical functions
MINX
8/25/2021 • 2 minutes to read
Returns the smallest value that results from evaluating an expression for each row of a table.
Syntax
MINX(<table>, < expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A smallest value.
Remarks
The MINX function takes as its first argument a table, or an expression that returns a table. The second
argument contains the expression that is evaluated for each row of the table.
Blank values are skipped. TRUE/FALSE values are not supported.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following example filters the table, InternetSales, and returns only rows for a specific sales territory. The
formula then finds the minimum value in the column, Freight.
Example 2
The following example uses the same filtered table as in the previous example, but instead of merely looking up
values in the column for each row of the filtered table, the function calculates the sum of two columns, Freight
and TaxAmt, and returns the smallest value resulting from that calculation.
See also
MIN function
MINA function
Statistical functions
PRODUCT
8/25/2021 • 2 minutes to read
Syntax
PRODUCT(<column>)
Parameters
T ERM DEF IN IT IO N
column The column that contains the numbers for which the
product is to be computed.
Return value
A decimal number.
Remarks
To return the product of an expression evaluated for each row in a table, use PRODUCTX function.
Only the numbers in the column are counted. Blanks, logical values, and text are ignored. For example,
PRODUCT( Table[Column] ) is equivalent to PRODUCTX( Table, Table[Column] ) .
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the product of the AdjustedRates column in an Annuity table:
= PRODUCT( Annuity[AdjustedRates] )
See also
PRODUCTX
PRODUCTX
8/25/2021 • 2 minutes to read
Syntax
PRODUCTX(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A decimal number.
Remarks
To return the product of the numbers in a column, use PRODUCT.
The PRODUCTX function takes as its first argument a table, or an expression that returns a table. The
second argument is a column that contains the numbers for which you want to compute the product, or
an expression that evaluates to a column.
Only the numbers in the column are counted. Blanks, logical values, and text are ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the future value of an investment:
See also
PRODUCT
SUM
8/25/2021 • 2 minutes to read
Syntax
SUM(<column>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If you want to filter the values that you are summing, you can use the SUMX function and specify an expression
to sum over.
Example
The following example adds all the numbers that are contained in the column, Amt, from the table, Sales.
= SUM(Sales[Amt])
See also
SUMX
SUMX
8/25/2021 • 2 minutes to read
Syntax
SUMX(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A decimal number.
Remarks
The SUMX function takes as its first argument a table, or an expression that returns a table. The second
argument is a column that contains the numbers you want to sum, or an expression that evaluates to a
column.
Only the numbers in the column are counted. Blanks, logical values, and text are ignored.
For more complex examples of SUMX in formulas, see ALL and CALCULATETABLE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example first filters the table, InternetSales, on the expression, ShippingTerritoryID = 5 , and then
returns the sum of all values in the column, Freight. In other words, the expression returns the sum of freight
charges for only the specified sales area.
= SUMX(FILTER(InternetSales, InternetSales[SalesTerritoryID]=5),[Freight])
If you do not need to filter the column, use the SUM function. The SUM function is similar to the Excel function
of the same name, except that it takes a column as a reference.
See also
SUM
Statistical functions
Date and time functions
8/25/2021 • 2 minutes to read
These functions help you create calculations based on dates and time. Many of the functions in DAX are similar
to the Excel date and time functions. However, DAX functions use a datetime data type, and can take values
from a column as an argument.
In this category
F UN C T IO N DESC RIP T IO N
EOMONTH Returns the date in datetime format of the last day of the
month, before or after a specified number of months.
WEEKNUM Returns the week number for the given date and year
according to the return_type value.
YEAR Returns the year of a date as a four digit integer in the range
1900-9999.
Returns a table with a single column named "Date" that contains a contiguous set of dates. The range of dates is
from the specified start date to the specified end date, inclusive of those two dates.
Syntax
CALENDAR(<start_date>, <end_date>)
Parameters
T ERM DEF IN IT IO N
Return value
Returns a table with a single column named "Date" containing a contiguous set of dates. The range of dates is
from the specified start date to the specified end date, inclusive of those two dates.
Remarks
An error is returned if start_date is greater than end_date.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
The following formula returns a table with dates between January 1st, 2005 and December 31st, 2015.
For a data model which includes actual sales data and future sales forecasts. The following expression returns
the date table covering the range of dates in these two tables.
Returns a table with a single column named "Date" that contains a contiguous set of dates. The range of dates is
calculated automatically based on data in the model.
Syntax
CALENDARAUTO([fiscal_year_end_month])
Parameters
T ERM DEF IN IT IO N
Return value
Returns a table with a single column named "Date" that contains a contiguous set of dates. The range of dates is
calculated automatically based on data in the model.
Remarks
The date range is calculated as follows:
The earliest date in the model which is not in a calculated column or calculated table is taken as the
MinDate.
The latest date in the model which is not in a calculated column or calculated table is taken as the
MaxDate.
The date range returned is dates between the beginning of the fiscal year associated with MinDate and
the end of the fiscal year associated with MaxDate.
An error is returned if the model does not contain any datetime values which are not in calculated
columns or calculated tables.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In this example, the MinDate and MaxDate in the data model are July 1, 2010 and June 30, 2011.
CALENDARAUTO() will return all dates between January 1, 2010 and December 31, 2011.
CALENDARAUTO(3) will return all dates between March 1, 2010 and March 31, 2012.
DATE
8/25/2021 • 3 minutes to read
Syntax
DATE(<year>, <month>, <day>)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the specified date (datetime) .
Remarks
The DATE function takes the integers that are input as arguments, and generates the corresponding date.
The DATE function is most useful in situations where the year, month, and day are supplied by formulas.
For example, the underlying data might contain dates in a format that is not recognized as a date, such as
YYYYMMDD. You can use the DATE function in conjunction with other functions to convert the dates to a
number that can be recognized as a date.
In contrast to Microsoft Excel, which stores dates as a serial number, DAX date functions always return a
datetime data type. However, you can use formatting to display dates as serial numbers if you want.
Date and datetime can also be specified as a literal in the format dt"YYYY-MM-DD" ,
dt"YYYY-MM-DDThh:mm:ss" , or dt"YYYY-MM-DD hh:mm:ss" . When specified as a literal, using the DATE
function in the expression is not necessary. To learn more, see DAX Syntax | Date and time.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
Simple Date
The following formula returns the date July 8, 2009:
= DATE(2009,7,8)
= DATE(2008,1,2)
Months
If month is greater than 12, month adds that number of months to the first month in the year specified. The
following formula returns the date February 2, 2009:
= DATE(2008,14,2)
Days
If day is greater than the number of days in the month specified, day adds that number of days to the first day
in the month. The following formula returns the date February 4, 2008:
= DATE(2008,1,35)
See also
Date and time functions
DAY function
TODAY function
DATEDIFF
8/25/2021 • 2 minutes to read
Syntax
DATEDIFF(<start_date>, <end_date>, <interval>)
Parameters
T ERM DEF IN IT IO N
interval The interval to use when comparing dates. The value can be
one of the following:
- SECOND
- MINUTE
- HOUR
- DAY
- WEEK
- MONTH
- QUARTER
- YEAR
Return value
The count of interval boundaries crossed between two dates.
Remarks
An error is returned if start_date is larger than end_date.
Example
DAT E
2012-12-31 23:59:59
2013-01-01 00:00:00
Syntax
DATEVALUE(date_text)
Parameters
T ERM DEF IN IT IO N
Remarks
When converting, DATEVALUE uses the locale and date/time settings of the model to determine a date
value. If the model date/time settings represent dates in the format of Month/Day/Year, then the string,
"1/8/2009", is converted to a datetime value equivalent to January 8th of 2009. However, if the model
date/time settings represent dates in the format of Day/Month/Year, the same string is converted as a
datetime value equivalent to August 1st of 2009.
If conversion using the locale and date/time settings of the model fails, DATEVALUE will attempt to use
other date formats. In this case, some rows may be converted using one format and other rows are
converted using a different format. For example, "5/4/2018" may convert to May 4th of 2018, and
"20/4/2018" may convert to April 20th.
If the year portion of the date_text argument is omitted, the DATEVALUE function uses the current year
from your computer's built-in clock. Time information in the date_text argument is ignored.
Model locale and data/time settings are initially determined by the application and computer when the
model is created.
Date and datetime can also be specified as a literal in the format dt"YYYY-MM-DD" ,
dt"YYYY-MM-DDThh:mm:ss" , or dt"YYYY-MM-DD hh:mm:ss" . When specified as a literal, using the DATEVALUE
function in the expression is not necessary. To learn more, see DAX Syntax | Date and time.
Example
The following example returns a different datetime value depending on the model locale and settings for how
dates and times are presented.
In date/time settings where the day precedes the month, the example returns a datetime value
corresponding to January 8th of 2009.
In date/time settings where the month precedes the day, the example returns a datetime value
corresponding to August 1st of 2009.
= DATEVALUE("8/1/2009")
See also
Date and time functions
DAY
8/25/2021 • 2 minutes to read
Syntax
DAY(<date>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number indicating the day of the month.
Remarks
The DAY function takes as an argument the date of the day you are trying to find. Dates can be provided
to the function by using another date function, by using an expression that returns a date, or by typing a
date in a datetime format. You can also type a date in one of the accepted string formats for dates.
Values returned by the YEAR, MONTH and DAY functions will be Gregorian values regardless of the
display format for the supplied date value. For example, if the display format of the supplied date is Hijri,
the returned values for the YEAR, MONTH and DAY functions will be values associated with the equivalent
Gregorian date.
When the date argument is a text representation of the date, the day function uses the locale and
date/time settings of the client computer to understand the text value in order to perform the conversion.
If the current date/time settings represent dates in the format of Month/Day/Year, then the string,
"1/8/2009", is interpreted as a datetime value equivalent to January 8th of 2009, and the function
returns 8. However, if the current date/time settings represent dates in the format of Day/Month/Year, the
same string would be interpreted as a datetime value equivalent to August 1st of 2009, and the function
returns 1.
= DAY([Birthdate])
= IF( DAY([SalesDate])=10,"promotion","")
See also
Date and time functions
TODAY function
DATE function
EDATE
8/25/2021 • 2 minutes to read
Returns the date that is the indicated number of months before or after the start date. Use EDATE to calculate
maturity dates or due dates that fall on the same day of the month as the date of issue.
Syntax
EDATE(<start_date>, <months>)
Parameters
T ERM DEF IN IT IO N
Return value
A date (datetime ).
Remarks
In contrast to Microsoft Excel, which stores dates as sequential serial numbers, DAX works with dates in a
datetime format. Dates stored in other formats are converted implicitly.
If star t_date is not a valid date, EDATE returns an error. Make sure that the column reference or date that
you supply as the first argument is a date.
If months is not an integer, it is truncated.
When the date argument is a text representation of the date, the EDATE function uses the locale and date
time settings of the client computer to understand the text value in order to perform the conversion. If the
current date time settings represent a date in the format of Month/Day/Year, then the following string
"1/8/2009" is interpreted as a datetime value equivalent to January 8th of 2009. However, if the current
date time settings represent a date in the format of Day/Month/Year, the same string would be
interpreted as a datetime value equivalent to August 1st of 2009.
If the requested date is past the last day of the corresponding month, then the last day of the month is
returned. For example, the following functions: EDATE("2009-01-29", 1), EDATE("2009-01-30", 1),
EDATE("2009-01-31", 1) return February 28th of 2009; that corresponds to one month after the start
date.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns the date three months after the order date, which is stored in the column
[TransactionDate].
= EDATE([TransactionDate],3)
See also
EOMONTH function
Date and time functions
EOMONTH
8/25/2021 • 2 minutes to read
Returns the date in datetime format of the last day of the month, before or after a specified number of months.
Use EOMONTH to calculate maturity dates or due dates that fall on the last day of the month.
Syntax
EOMONTH(<start_date>, <months>)
Parameters
T ERM DEF IN IT IO N
Return value
A date (datetime ).
Remarks
In contrast to Microsoft Excel, which stores dates as sequential serial numbers, DAX works with dates in a
datetime format. The EOMONTH function can accept dates in other formats, with the following
restrictions:
If star t_date is not a valid date, EOMONTH returns an error.
If star t_date is a numeric value that is not in a datetime format, EOMONTH will convert the number to
a date. To avoid unexpected results, convert the number to a datetime format before using the
EOMONTH function.
If star t_date plus months yields an invalid date, EOMONTH returns an error. Dates before March 1st of
1900 and after December 31st of 9999 are invalid.
When the date argument is a text representation of the date, the EDATE function uses the locale and date
time settings, of the client computer, to understand the text value in order to perform the conversion. If
current date time settings represent a date in the format of Month/Day/Year, then the following string
"1/8/2009" is interpreted as a datetime value equivalent to January 8th of 2009. However, if the current
date time settings represent a date in the format of Day/Month/Year, the same string would be
interpreted as a datetime value equivalent to August 1st of 2009.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following expression returns May 31, 2008, because the months argument is rounded to 2.
= EOMONTH("March 3, 2008",1.5)
See also
EDATE function
Date and time functions
HOUR
8/25/2021 • 2 minutes to read
Syntax
HOUR(<datetime>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number from 0 to 23.
Remarks
The HOUR function takes as argument the time that contains the hour you want to find. You can supply
the time by using a date/time function, an expression that returns a datetime , or by typing the value
directly in one of the accepted time formats. Times can also be entered as any accepted text
representation of a time.
When the datetime argument is a text representation of the date and time, the function uses the locale
and date/time settings of the client computer to understand the text value in order to perform the
conversion. Most locales use the colon (:) as the time separator and any input text using colons as time
separators will parse correctly. Review your locale settings to understand your results.
Example 1
The following example returns the hour from the TransactionTime column of a table named Orders .
= HOUR('Orders'[TransactionTime])
Example 2
The following example returns 15, meaning the hour corresponding to 3 PM in a 24-hour clock. The text value is
automatically parsed and converted to a date/time value.
See also
Date and time functions
MINUTE function
YEAR function
SECOND function
MINUTE
8/25/2021 • 2 minutes to read
Returns the minute as a number from 0 to 59, given a date and time value.
Syntax
MINUTE(<datetime>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number from 0 to 59.
Remarks
In contrast to Microsoft Excel, which stores dates and times in a serial numeric format, DAX uses a
datetime data type for dates and times. You can provide the datetime value to the MINUTE function by
referencing a column that stores dates and times, by using a date/time function, or by using an
expression that returns a date and time.
When the datetime argument is a text representation of the date and time, the function uses the locale
and date/time settings of the client computer to understand the text value in order to perform the
conversion. Most locales use the colon (:) as the time separator and any input text using colons as time
separators will parse correctly. Verify your locale settings to understand your results.
Example 1
The following example returns the minute from the value stored in the TransactionTime column of the Orders
table.
= MINUTE(Orders[TransactionTime])
Example 2
The following example returns 45, which is the number of minutes in the time 1:45 PM.
See also
Date and time functions
HOUR function
YEAR function
SECOND function
MONTH
8/25/2021 • 2 minutes to read
Syntax
MONTH(<datetime>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number from 1 to 12.
Remarks
In contrast to Microsoft Excel, which stores dates as serial numbers, DAX uses a datetime format when
working with dates. You can enter the date used as argument to the MONTH function by typing an
accepted datetime format, by providing a reference to a column that contains dates, or by using an
expression that returns a date.
Values returned by the YEAR, MONTH and DAY functions will be Gregorian values regardless of the
display format for the supplied date value. For example, if the display format of the supplied date is Hijri,
the returned values for the YEAR, MONTH and DAY functions will be values associated with the equivalent
Gregorian date.
When the date argument is a text representation of the date, the function uses the locale and date time
settings of the client computer to understand the text value in order to perform the conversion. If the
current date time settings represent a date in the format of Month/Day/Year, then the following string
"1/8/2009" is interpreted as a datetime value equivalent to January 8th of 2009, and the function yields a
result of 1. However, if the current date time settings represent a date in the format of Day/Month/Year,
then the same string would be interpreted as a datetime value equivalent to August 1st of 2009, and the
function yields a result of 8.
If the text representation of the date cannot be correctly converted to a datetime value, the function
returns an error.
Example 1
The following expression returns 3, which is the integer corresponding to March, the month in the date
argument.
= MONTH(Orders[TransactionDate])
See also
Date and time functions
HOUR function
MINUTE function
YEAR function
SECOND function
NOW
8/25/2021 • 2 minutes to read
Syntax
NOW()
Return value
A date (datetime) .
Remarks
The result of the NOW function changes only when the column that contains the formula is refreshed. It
is not updated continuously.
In the Power BI Service, the result of the NOW function is always in the UTC timezone.
The TODAY function returns the same date but is not precise with regard to time; the time returned is
always 12:00:00 AM and only the date is updated.
Example
The following example returns the current date and time plus 3.5 days:
= NOW()+3.5
See also
UTCNOW function
TODAY function
QUARTER
8/25/2021 • 2 minutes to read
Syntax
QUARTER(<date>)
Parameters
T ERM DEF IN IT IO N
date A date.
Return value
An integer number from 1 to 4.
Remarks
If the input value is BLANK, the output value is also BLANK.
Example 1
The following DAX query:
Returns:
[ VA L UE]
Example 2
The following DAX query:
EVALUATE
ADDCOLUMNS(
FILTER(
VALUES(
FactInternetSales[OrderDate]),
[OrderDate] >= DATE(2008, 3, 31) && [OrderDate] <= DATE(2008, 4, 1)
),
"Quarter", QUARTER([OrderDate])
)
Returns:
3/31/2008 1
4/1/2008 2
See also
YEAR
MONTH
DAY
SECOND
8/25/2021 • 2 minutes to read
Syntax
SECOND(<time>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number from 0 to 59.
Remarks
In contrast to Microsoft Excel, which stores dates and times as serial numbers, DAX uses a datetime
format when working with dates and times. If the source data is not in this format, DAX implicitly
converts the data. You can use formatting to display the dates and times as a serial number of you need
to.
The date/time value that you supply as an argument to the SECOND function can be entered as a text
string within quotation marks (for example, "6:45 PM"). You can also provide a time value as the result of
another expression, or as a reference to a column that contains times.
If you provide a numeric value of another data type, such as 13.60, the value is interpreted as a serial
number and is represented as a datetime data type before extracting the value for seconds. To make it
easier to understand your results, you might want to represent such numbers as dates before using them
in the SECOND function. For example, if you use SECOND with a column that contains a numeric value
such as, 25.56 , the formula returns 24. That is because, when formatted as a date, the value 25.56 is
equivalent to January 25, 1900, 1:26:24 PM.
When the time argument is a text representation of a date and time, the function uses the locale and
date/time settings of the client computer to understand the text value in order to perform the conversion.
Most locales use the colon (:) as the time separator and any input text using colons as time separators will
parse correctly. Review your locale settings to understand your results.
Example 1
The following formula returns the number of seconds in the time contained in the TransactionTime column of
a table named Orders .
= SECOND('Orders'[TransactionTime])
Example 2
The following formula returns 3, which is the number of seconds in the time represented by the value, March 3,
2008 12:00:03 .
See also
Date and time functions
HOUR
MINUTE
YEAR
TIME
8/25/2021 • 2 minutes to read
Converts hours, minutes, and seconds given as numbers to a time in datetime format.
Syntax
TIME(hour, minute, second)
Parameters
T ERM DEF IN IT IO N
Return value
A time (datetime ).
Remarks
In contrast to Microsoft Excel, which stores dates and times as serial numbers, DAX works with date and
time values in a datetime format. Numbers in other formats are implicitly converted when you use a
date/time value in a DAX function. If you need to use serial numbers, you can use formatting to change
the way that the numbers are displayed.
Time values are a portion of a date value, and in the serial number system are represented by a decimal
number. Therefore, the datetime value 12:00 PM is equivalent to 0.5, because it is half of a day.
You can supply the arguments to the TIME function as values that you type directly, as the result of
another expression, or by a reference to a column that contains a numeric value. The following
restrictions apply:
Any value for hours that is greater than 23 will be divided by 24 and the remainder will be treated as
the hour value.
Any value for minutes that is greater than 59 will be converted to hours and minutes.
Any value for seconds that is greater than 59 will be converted to hours, minutes, and seconds.
For minutes or seconds, a value greater than 24 hours will be divided by 24 and the reminder will be
treated as the hour value. A value in excess of 24 hours does not alter the date portion.
Date and datetime can also be specified as a literal in the format dt"YYYY-MM-DD" ,
dt"YYYY-MM-DDThh:mm:ss" , or dt"YYYY-MM-DD hh:mm:ss" . When specified as a literal, using the TIME
function in the expression is not necessary. To learn more, see DAX Syntax | Date and time.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following examples both return the time, 3:00 AM:
= TIME(27,0,0)
= TIME(3,0,0)
Example 2
The following examples both return the time, 12:30 PM:
= TIME(0,750,0)
= TIME(12,30,0)
Example 3
The following example creates a time based on the values in the columns, intHours , intMinutes , intSeconds :
= TIME([intHours],[intMinutes],[intSeconds])
See also
DATE
Date and time functions
TIMEVALUE
8/25/2021 • 2 minutes to read
Syntax
TIMEVALUE(time_text)
Parameters
T ERM DEF IN IT IO N
time_text A text string that that represents a certain time of the day.
Any date information included in the time_text argument is
ignored.
Return value
A date (datetime ).
Remarks
Time values are a portion of a date value and represented by a decimal number. For example, 12:00 PM is
represented as 0.5 because it is half of a day.
When the time_text argument is a text representation of the date and time, the function uses the locale
and date/time settings of the model to understand the text value in order to perform the conversion.
Most locales use the colon (:) as the time separator, and any input text using colons as time separators will
parse correctly. Review your locale settings to understand your results.
Date and datetime can also be specified as a literal in the format dt"YYYY-MM-DD" ,
dt"YYYY-MM-DDThh:mm:ss" , or dt"YYYY-MM-DD hh:mm:ss" . When specified as a literal, using the TIMEVALUE
function in the expression is not necessary. To learn more, see DAX Syntax | Date and time.
Example
= TIMEVALUE("20:45:30")
See also
Date and time functions
TODAY
8/25/2021 • 2 minutes to read
Syntax
TODAY()
Return value
A date (datetime ).
Remarks
The TODAY function is useful when you need to have the current date displayed on a worksheet,
regardless of when you open the workbook. It is also useful for calculating intervals.
If the TODAY function does not update the date when you expect it to, you might need to change the
settings that control when the column or workbook is refreshed..
The NOW function is similar but returns the exact time, whereas TODAY returns the time value 12:00:00
PM for all dates.
Example
If you know that someone was born in 1963, you might use the following formula to find that person's age as of
this year's birthday:
= YEAR(TODAY())-1963
This formula uses the TODAY function as an argument for the YEAR function to obtain the current year, and then
subtracts 1963, returning the person's age.
See also
Date and time functions
NOW
UTCNOW
8/25/2021 • 2 minutes to read
Syntax
UTCNOW()
Return value
A (datetime) .
Remarks
The result of the UTCNOW function changes only when the formula is refreshed. It is not continuously updated.
Example
The following:
Returns:
[ VA L UE]
2/2/2018 4:48:08 AM
See also
NOW function
UTCTODAY function
UTCTODAY
8/25/2021 • 2 minutes to read
Syntax
UTCTODAY()
Return value
A date.
Remarks
UTCTODAY returns the time value 12:00:00 PM for all dates.
The UTCNOW function is similar but returns the exact time and date.
Example
The following:
Returns:
[ VA L UE]
2/2/2018
See also
NOW function
UTCNOW function
WEEKDAY
8/25/2021 • 2 minutes to read
Returns a number from 1 to 7 identifying the day of the week of a date. By default the day ranges from 1
(Sunday) to 7 (Saturday).
Syntax
WEEKDAY(<date>, <return_type>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer number from 1 to 7.
Remarks
In contrast to Microsoft Excel, which stores dates as serial numbers, DAX works with dates and times in a
datetime format. If you need to display dates as serial numbers, you can use the formatting options in
Excel.
You can also type dates in an accepted text representation of a date, but to avoid unexpected results, it is
best to convert the text date to a datetime format first.
When the date argument is a text representation of the date, the function uses the locale and date/time
settings of the client computer to understand the text value in order to perform the conversion. If the
current date/time settings represent dates in the format of Month/Day/Year, then the string, "1/8/2009",
is interpreted as a datetime value equivalent to January 8th of 2009. However, if the current date/time
settings represent dates in the format of Day/Month/Year, then the same string would be interpreted as a
datetime value equivalent to August 1st of 2009.
Example
The following example gets the date from the [HireDate] column, adds 1, and displays the weekday
corresponding to that date. Because the return_type argument has been omitted, the default format is used, in
which 1 is Sunday and 7 is Saturday. If the result is 4, the day would be Wednesday.
= WEEKDAY([HireDate]+1)
See also
Date and time functions
WEEKNUM function
YEARFRAC function
WEEKNUM
8/25/2021 • 2 minutes to read
Returns the week number for the given date according to the return_type value. The week number indicates
where the week falls numerically within a year.
There are two systems used for this function:
System 1 - The week containing January 1 is the first week of the year and is numbered week 1.
System 2 - The week containing the first Thursday of the year is the first week of the year and is numbered
as week 1. This system is the methodology specified in ISO 8601, which is commonly known as the European
week numbering system.
Syntax
WEEKNUM(<date>[, <return_type>])
Parameters
T ERM DEF IN IT IO N
Return value
An integer number.
Remarks
By default, the WEEKNUM function uses a calendar convention in which the week containing January 1 is
considered to be the first week of the year. However, the ISO 8601 calendar standard, widely used in
Europe, defines the first week as the one with the majority of days (four or more) falling in the new year.
This means that if return_type is any valid value other than 21, for any years in which there are three
days or less in the first week of January, the WEEKNUM function returns week numbers that are different
from the ISO 8601 definition.
For return_type , except for 21, the following valid values may not be supported by some DirectQuery
data sources:
1 or omitted Sunday 1
2 Monday 1
RET URN _T Y P E W EEK B EGIN S O N SY ST EM
11 Monday 1
12 Tuesday 1
13 Wednesday 1
14 Thursday 1
15 Friday 1
16 Saturday 1
17 Sunday 1
21 Monday 2
Example 1
The following example returns the week number for February 14, 2010. This calculation assumes weeks begin
on Monday.
Example 2
The following example returns the week number of the date stored in the column, HireDate , from the table,
Employees . This calculation assumes weeks begin on Sunday.
= WEEKNUM('Employees'[HireDate])
See also
YEARFRAC function
WEEKDAY function
YEAR
8/25/2021 • 2 minutes to read
Returns the year of a date as a four digit integer in the range 1900-9999.
Syntax
YEAR(<date>)
Parameters
T ERM DEF IN IT IO N
Return value
An integer in the range 1900-9999.
Remarks
In contrast to Microsoft Excel, which stores dates as serial numbers, DAX uses a datetime data type to
work with dates and times.
Dates should be entered by using the DATE function, or as results of other formulas or functions. You can
also enter dates in accepted text representations of a date, such as March 3, 2007, or Mar-3-2003.
Values returned by the YEAR, MONTH, and DAY functions will be Gregorian values regardless of the
display format for the supplied date value. For example, if the display format of the supplied date uses the
Hijri calendar, the returned values for the YEAR, MONTH, and DAY functions will be values associated with
the equivalent Gregorian date.
When the date argument is a text representation of the date, the function uses the locale and date time
settings of the client computer to understand the text value in order to perform the conversion. Errors
may arise if the format of strings is incompatible with the current locale settings. For example, if your
locale defines dates to be formatted as month/day/year, and the date is provided as day/month/year, then
25/1/2009 will not be interpreted as January 25th of 2009 but as an invalid date.
Example
The following example returns 2007.
= YEAR("March 2007")
See also
Date and time functions
HOUR function
MINUTE function
YEAR function
SECOND function
YEARFRAC
8/25/2021 • 2 minutes to read
Calculates the fraction of the year represented by the number of whole days between two dates. Use the
YEARFRAC worksheet function to identify the proportion of a whole year's benefits or obligations to assign to a
specific term.
Syntax
YEARFRAC(<start_date>, <end_date>, <basis>)
Parameters
T ERM DEF IN IT IO N
basis (Optional) The type of day count basis to use. All arguments
are truncated to integers.
Basis - Description
0 - US (NASD) 30/360
1 - Actual/actual
2 - Actual/360
3 - Actual/365
4 - European 30/360
Return value
A decimal number. The internal data type is a signed IEEE 64-bit (8-byte) double-precision floating-point
number.
Remarks
In contrast to Microsoft Excel, which stores dates as serial numbers, DAX uses a datetime format to work
with dates and times. If you need to view dates as serial numbers, you can use the formatting options in
Excel.
If star t_date or end_date are not valid dates, YEARFRAC returns an error.
If basis < 0 or if basis > 4, YEARFRAC returns an error.
Example 1
The following example returns the fraction of a year represented by the difference between the dates in the two
columns, TransactionDate and ShippingDate :
= YEARFRAC(Orders[TransactionDate],Orders[ShippingDate])
Example 2
The following example returns the fraction of a year represented by the difference between the dates, January 1
and March 1:
Use four-digit years whenever possible, to avoid getting unexpected results. When the year is truncated, the
current year is assumed. When the date is or omitted, the first date of the month is assumed.
The second argument, basis , has also been omitted. Therefore, the year fraction is calculated according to the
US (NASD) 30/360 standard.
See also
Date and time functions
WEEKNUM function
YEARFRAC function
WEEKDAY function
Filter functions
8/25/2021 • 2 minutes to read
The filter and value functions in DAX are some of the most complex and powerful, and differ greatly from Excel
functions. The lookup functions work by using tables and relationships, like a database. The filtering functions let
you manipulate data context to create dynamic calculations.
In this category
F UN C T IO N DESC RIP T IO N
ALL Returns all the rows in a table, or all the values in a column,
ignoring any filters that might have been applied.
ALLEXCEPT Removes all context filters in the table except filters that have
been applied to the specified columns.
ALLNOBLANKROW From the parent table of a relationship, returns all rows but
the blank row, or all distinct values of a column but the blank
row, and disregards any context filters that might exist.
LOOKUPVALUE Returns the value for the row that meets all criteria specified
by search conditions. The function can apply one or more
search conditions.
SELECTEDVALUE Returns the value when the context for columnName has
been filtered down to one distinct value only. Otherwise
returns alternateResult.
ALL
8/25/2021 • 7 minutes to read
Returns all the rows in a table, or all the values in a column, ignoring any filters that might have been applied.
This function is useful for clearing filters and creating calculations on all the rows in a table.
Syntax
ALL( [<table> | <column>[, <column>[, <column>[,…]]]] )
Parameters
T ERM DEF IN IT IO N
The argument to the ALL function must be either a reference to a base table or a reference to a base column. You
cannot use table expressions or column expressions with the ALL function.
Return value
The table or column with filters removed.
Remarks
This function is not used by itself, but serves as an intermediate function that can be used to change the
set of results over which some other calculation is performed.
The normal behavior for DAX expressions containing the ALL() function is that any filters applied will be
ignored. However, there are some scenarios where this is not the case because of auto-exist, a DAX
technology that optimizes filtering in order to reduce the amount of processing required for certain DAX
queries. An example where auto-exist and ALL() provide unexpected results is when filtering on two or
more columns of the same table (like when using slicers), and there is a measure on that same table that
uses ALL(). In this case, auto-exist will merge the multiple filters into one and will only filter on existing
combinations of values. Because of this merge, the measure will be calculated on the existing
combinations of values and the result will be based on filtered values instead of all values as expected. To
learn more about auto-exist and its effect on calculations, see Microsoft MVP Alberto Ferrari's
Understanding DAX Auto-Exist article on sql.bi.com.
The following table describes how you can use the ALL and ALLEXCEPT functions in different scenarios.
ALL (Column[, Column[, …]]) Removes all filters from the specified columns in the
table; all other filters on other columns in the table still
apply. All column arguments must come from the same
table. The ALL(Column) variant is useful when you want
to remove the context filters for one or more specific
columns and to keep all other context filters. The second
and third examples demonstrate this scenario.
ALLEXCEPT(Table, Column1 [,Column2]...) Removes all context filters in the table except filters that
are applied to the specified columns. This is a convenient
shortcut for situations in which you want to remove the
filters on many, but not all, columns in a table.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
Calculate ratio of Category Sales to Total Sales
Assume that you want to find the amount of sales for the current cell, in your PivotTable, divided by the total
sales for all resellers. To ensure that the denominator is the same regardless of how the PivotTable user might be
filtering or grouping the data, you define a formula that uses ALL to create the correct grand total.
The following table shows the results when a new measure, All Reseller Sales Ratio , is created using the
formula shown in the code section. To see how this works, add the field, CalendarYear, to the Row Labels area
of the PivotTable, and add the field, ProductCategoryName, to the Column Labels area. Then, drag the
measure, All Reseller Sales Ratio , to the Values area of the Pivot Table. To view the results as percentages,
use the formatting features of Excel to apply a percentage number formatting to the cells that contains the
measure.
Formula
= SUMX(ResellerSales_USD, ResellerSales_USD[SalesAmount_USD])/SUMX(ALL(ResellerSales_USD),
ResellerSales_USD[SalesAmount_USD])
Example 2
Calculate Ratio of Product Sales to Total Sales Through Current Year
Assume that you want to create a table showing the percentage of sales compared over the years for each
product category (ProductCategoryName). To obtain the percentage for each year over each value of
ProductCategoryName, you need to divide the sum of sales for that particular year and product category by the
sum of sales for the same product category over all years. In other words, you want to keep the filter on
ProductCategoryName but remove the filter on the year when calculating the denominator of the percentage.
The following table shows the results when a new measure, Reseller Sales Year , is created using the formula
shown in the code section. To see how this works, add the field, CalendarYear, to the Row Labels area of a
PivotTable, and add the field, ProductCategoryName, to the Column Labels area. To view the results as
percentages, use Excel's formatting features to apply a percentage number format to the cells containing the
measure, Reseller Sales Year .
Formula
Example 3
Calculate Contribution of Product Categories to Total Sales Per Year
Assume that you want to create a table that shows the percentage of sales for each product category, on a year-
by-year basis. To obtain the percentage for each product category in a particular year, you need to calculate the
sum of sales for that particular product category (ProductCategoryName) in year n, and then divide the
resulting value by the sum of sales for the year n over all product categories. In other words, you want to keep
the filter on year but remove the filter on ProductCategoryName when calculating the denominator of the
percentage.
The following table shows the results when a new measure, Reseller Sales Categor yName , is created using
the formula shown in the code section. To see how this works, add the field, CalendarYear to the Row Labels
area of the PivotTable, and add the field, ProductCategoryName, to the Column Labels area. Then add the new
measure to the Values area of the PivotTable. To view the results as percentages, use Excel's formatting features
to apply a percentage number format to the cells that contain the new measure, Reseller Sales
Categor yName .
Formula
See also
Filter functions
ALL function
ALLEXCEPT function
FILTER function
ALLCROSSFILTERED
8/25/2021 • 2 minutes to read
Syntax
ALLCROSSFILTERED(<table>)
Parameters
T ERM DEF IN IT IO N
Return value
N/A. See remarks.
Remarks
ALLCROSSFILTERED can only be used to clear filters but not to return a table.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DEFINE
MEASURE FactInternetSales[TotalQuantity1] =
CALCULATE(SUM(FactInternetSales[OrderQuantity]), ALLCROSSFILTERED(FactInternetSales))
MEASURE FactInternetSales[TotalQuantity2] =
CALCULATE(SUM(FactInternetSales[OrderQuantity]), ALL(FactInternetSales))
EVALUATE
SUMMARIZECOLUMNS(DimSalesReason[SalesReasonName],
"TotalQuantity1", [TotalQuantity1],
"TotalQuantity2", [TotalQuantity2])
ORDER BY DimSalesReason[SalesReasonName]
Returns,
Sponsorship 60398
NOTE
There is a direct or indirect many-to-many relationship between FactInternetSales table and DimSalesReason table.
ALLEXCEPT
8/25/2021 • 2 minutes to read
Removes all context filters in the table except filters that have been applied to the specified columns.
Syntax
ALLEXCEPT(<table>,<column>[,<column>[,…]])
Parameters
T ERM DEF IN IT IO N
table The table over which all context filters are removed, except
filters on those columns that are specified in subsequent
arguments.
The first argument to the ALLEXCEPT function must be a reference to a base table. All subsequent arguments
must be references to base columns. You cannot use table expressions or column expressions with the
ALLEXCEPT function.
Return value
A table with all filters removed except for the filters on the specified columns.
Remarks
This function is not used by itself, but serves as an intermediate function that can be used to change the
set of results over which some other calculation is performed.
ALL and ALLEXCEPT can be used in different scenarios:
ALL (Column[, Column[, …]]) Removes all filters from the specified columns in the
table; all other filters on other columns in the table still
apply. All column arguments must come from the same
table. The ALL(Column) variant is useful when you want
to remove the context filters for one or more specific
columns and to keep all other context filters.
F UN C T IO N A N D USA GE DESC RIP T IO N
ALLEXCEPT(Table, Column1 [,Column2]...) Removes all context filters in the table except filters that
are applied to the specified columns. This is a convenient
shortcut for situations in which you want to remove the
filters on many, but not all, columns in a table.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following measure formula sums SalesAmount_USD and uses the ALLEXCEPT function to remove any
context filters on the DateTime table except if the filter has been applied to the CalendarYear column.
Because the formula uses ALLEXCEPT, whenever any column but CalendarYear from the table DateTime is used
to slice a visualization, the formula will remove any slicer filters, providing a value equal to the sum of
SalesAmount_USD. However, if the column CalendarYear is used to slice the visualization, the results are
different. Because CalendarYear is specified as the argument to ALLEXCEPT, when the data is sliced on the year, a
filter will be applied on years at the row level
See also
Filter functions
ALL function
FILTER function
ALLNOBLANKROW
3/15/2021 • 4 minutes to read
From the parent table of a relationship, returns all rows but the blank row, or all distinct values of a column but
the blank row, and disregards any context filters that might exist.
Syntax
ALLNOBLANKROW( {<table> | <column>[, <column>[, <column>[,…]]]} )
Parameters
T ERM DEF IN IT IO N
table The table over which all context filters are removed.
Only one parameter must be passed; the parameter is either a table or a column.
Return value
A table, when the passed parameter was a table, or a column of values, when the passed parameter was a
column.
Remarks
The ALLNOBLANKROW function only filters the blank row that a parent table, in a relationship, will show
when there are one or more rows in the child table that have non-matching values to the parent column.
See the example below for a thorough explanation.
The following table summarizes the variations of ALL that are provided in DAX, and their differences:
ALL(Column) Removes all filters from the specified column in the table;
all other filters in the table, over other columns, still
apply.
ALLEXCEPT(Table,Col1,Col2...) Overrides all context filters in the table except over the
specified columns.
For a general description of how the ALL function works, together with step-by-step examples that use
ALL(Table) and ALL(Column), see ALL function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the sample data, the ResellerSales_USD table contains one row that has no values and therefore cannot be
related to any of the parent tables in the relationships within the workbook. You will use this table in a PivotTable
so that you can see the blank row behavior and how to handle counts on unrelated data.
Step 1: Verify the unrelated data
Open the Power Pivot window , then select the ResellerSales_USD table. In the ProductKey column, filter for
blank values. One row will remain. In that row, all column values should be blank except for
SalesOrderLineNumber.
Step 2: Create a PivotTable
Create a new PivotTable, then drag the column, datetime.[Calendar Year], to the Row Labels pane. The following
table shows the expected results:
RO W L A B EL S
2005
2006
2007
2008
Grand Total
Note the blank label between 2008 and Grand Total . This blank label represents the Unknown member, which
is a special group that is created to account for any values in the child table that have no matching value in the
parent table, in this example the datetime.[Calendar Year] column.
When you see this blank label in the PivotTable, you know that in some of the tables that are related to the
column, datetime.[Calendar Year], there are either blank values or non-matching values. The parent table is the
one that shows the blank label, but the rows that do not match are in one or more of the child tables.
The rows that get added to this blank label group are either values that do not match any value in the parent
table-- for example, a date that does not exist in the datetime table-- or null values, meaning no value for date at
all. In this example we have placed a blank value in all columns of the child sales table. Having more values in
the parent table than in the children tables does not cause a problem.
Step 3: Count rows using ALL and ALLNOBLANK
Add the following two measures to the datetime table, to count the table rows: Countrows ALLNOBL ANK of
datetime , Countrows ALL of datetime . The formulas that you can use to define these measures are:
// Countrows ALLNOBLANK of datetime
= COUNTROWS(ALLNOBLANKROW('DateTime'))
On a blank PivotTable add datetime.[Calendar Year] column to the row labels, and then add the newly created
measures. The results should look like the following table:
C O UN T RO W S A L L N O B L A N K O F
RO W L A B EL S DAT ET IM E C O UN T RO W S A L L O F DAT ET IM E
1280 1281
The results show a difference of 1 row in the table rows count. However, if you open the Power Pivot window
and select the datetime table, you cannot find any blank row in the table because the special blank row
mentioned here is the Unknown member.
Step 4: Verify that the count is accurate
In order to prove that the ALLNOBLANKROW does not count any truly blank rows, and only handles the special
blank row on the parent table only, add the following two measures to the ResellerSales_USD table: Countrows
ALLNOBL ANKROW of ResellerSales_USD , Countrows ALL of ResellerSales_USD .
Create a new PivotTable, and drag the column, datetime.[Calendar Year], to the Row Labels pane. Now add the
measures that you just created. The results should look like the following:
C O UN T RO W S A L L N O B L A N K RO W O F C O UN T RO W S A L L O F
RO W L A B EL S RESEL L ERSA L ES_USD RESEL L ERSA L ES_USD
60856 60856
C O UN T RO W S A L L N O B L A N K RO W O F C O UN T RO W S A L L O F
RO W L A B EL S RESEL L ERSA L ES_USD RESEL L ERSA L ES_USD
Now the two measures have the same results. That is because the ALLNOBLANKROW function does not count
truly blank rows in a table, but only handles the blank row that is a special case generated in a parent table,
when one or more of the child tables in the relationship contain non-matching values or blank values.
See also
Filter functions
ALL function
FILTER function
ALLSELECTED
8/25/2021 • 4 minutes to read
Removes context filters from columns and rows in the current query, while retaining all other context filters or
explicit filters.
The ALLSELECTED function gets the context that represents all rows and columns in the query, while keeping
explicit filters and contexts other than row and column filters. This function can be used to obtain visual totals in
queries.
Syntax
ALLSELECTED([<tableName> | <columnName>[, <columnName>[, <columnName>[,…]]]] )
Parameters
T ERM DEF IN IT IO N
Return value
The context of the query without any column and row filters.
Remarks
If there is one argument, the argument is either tableName or columnName. If there is more than one
argument, they must be columns from the same table.
This function is different from ALL() because it retains all filters explicitly set within the query, and it
retains all context filters other than row and column filters.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows how to generate different levels of visual totals in a table report using DAX
expressions. In the report two (2) previous filters have been applied to the Reseller Sales data; one on Sales
Territory Group = Europe and the other on Promotion Type = Volume Discount. Once filters have been applied,
visual totals can be calculated for the entire report, for All Years, or for All Product Categories. Also, for
illustration purposes the grand total for All Reseller Sales is obtained too, removing all filters in the report.
Evaluating the following DAX expression results in a table with all the information needed to build a table with
Visual Totals.
define
measure 'Reseller Sales'[Reseller Sales Amount]=sum('Reseller Sales'[Sales Amount])
measure 'Reseller Sales'[Reseller Grand Total]=calculate(sum('Reseller Sales'[Sales Amount]), ALL('Reseller
Sales'))
measure 'Reseller Sales'[Reseller Visual Total]=calculate(sum('Reseller Sales'[Sales Amount]),
ALLSELECTED())
measure 'Reseller Sales'[Reseller Visual Total for All of Calendar Year]=calculate(sum('Reseller
Sales'[Sales Amount]), ALLSELECTED('Date'[Calendar Year]))
measure 'Reseller Sales'[Reseller Visual Total for All of Product Category Name]=calculate(sum('Reseller
Sales'[Sales Amount]), ALLSELECTED('Product Category'[Product Category Name]))
evaluate
CalculateTable(
//CT table expression
summarize(
//summarize table expression
crossjoin(distinct('Product Category'[Product Category Name]), distinct('Date'[Calendar Year]))
//First Group by expression
, 'Product Category'[Product Category Name]
//Second Group by expression
, 'Date'[Calendar Year]
//Summary expressions
, "Reseller Sales Amount", [Reseller Sales Amount]
, "Reseller Grand Total", [Reseller Grand Total]
, "Reseller Visual Total", [Reseller Visual Total]
, "Reseller Visual Total for All of Calendar Year", [Reseller Visual Total for All of Calendar Year]
, "Reseller Visual Total for All of Product Category Name", [Reseller Visual Total for All of Product
Category Name]
)
//CT filters
, 'Sales Territory'[Sales Territory Group]="Europe", 'Promotion'[Promotion Type]="Volume Discount"
)
order by [Product Category Name], [Calendar Year]
After executing the above expression in SQL Server Management Studio against AdventureWorks DW Tabular
Model, you obtain the following results:
[ RESEL L ER
[ RESEL L ER VISUA L TOTA L
VISUA L TOTA L FOR ALL OF
[ P RO DUC T [ RESEL L ER [ RESEL L ER [ RESEL L ER FOR ALL OF P RO DUC T
C AT EGO RY [ C A L EN DA R SA L ES GRA N D VISUA L C A L EN DA R C AT EGO RY
N A M E] Y EA R] A M O UN T ] TOTA L ] TOTA L ] Y EA R] N A M E]
NOTE
if you have explicit filters in your expression, those filters are also applied to the expression.
CALCULATE
9/15/2021 • 4 minutes to read
NOTE
There's also the CALCULATETABLE function. It performs exactly the same functionality, except it modifies the filter context
applied to an expression that returns a table object.
Syntax
CALCULATE(<expression>[, <filter1> [, <filter2> [, …]]])
Parameters
T ERM DEF IN IT IO N
The expression used as the first parameter is essentially the same as a measure.
Filters can be:
Boolean filter expressions
Table filter expressions
Filter modification functions
When there are multiple filters, they can be evaluated by using the AND (&&) logical operator, meaning all
conditions must be TRUE, or by the OR (||) logical operator, meaning either condition can be true.
Boolean filter expressions
A Boolean expression filter is an expression that evaluates to TRUE or FALSE. There are several rules that they
must abide by:
They can reference columns from a single table.
They cannot reference measures.
They cannot use a nested CALCULATE function.
Beginning with the September 2021 release of Power BI Desktop, the following also apply:
They cannot use functions that scan or return a table unless they are passed as arguments to aggregation
functions.
They can contain an aggregation function that returns a scalar value. For example,
Total sales on the last selected date =
CALCULATE (
SUM ( Sales[Sales Amount] ),
'Sales'[OrderDateKey] = MAX ( 'Sales'[OrderDateKey] )
)
F UN C T IO N P URP O SE
ALL 1 , ALLEXCEPT, ALLNOBLANKROW Remove filters from one or more columns, or from all
columns of a single table.
1 The ALL
function and its variants behave as both filter modifiers and as functions that return table objects. If
the REMOVEFILTERS function is supported by your tool, it's better to use it to remove filters.
Return value
The value that is the result of the expression.
Remarks
When filter expressions are provided, the CALCULATE function modifies the filter context to evaluate the
expression. For each filter expression, there are two possible standard outcomes when the filter
expression is not wrapped in the KEEPFILTERS function:
If the columns (or tables) aren't in the filter context, then new filters will be added to the filter context
to evaluate the expression.
If the columns (or tables) are already in the filter context, the existing filters will be overwritten by the
new filters to evaluate the CALCULATE expression.
The CALCULATE function used without filters achieves a specific requirement. It transitions row context to
filter context. It's required when an expression (not a model measure) that summarizes model data needs
to be evaluated in row context. This scenario can happen in a calculated column formula or when an
expression in an iterator function is evaluated. Note that when a model measure is used in row context,
context transition is automatic.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
The following Sales table measure definition produces a revenue result, but only for products that have the
color blue.
Examples in this article can be added to the Power BI Desktop sample model. To get the model, see DAX sample
model.
Blue Revenue =
CALCULATE(
SUM(Sales[Sales Amount]),
'Product'[Color] = "Blue"
)
C AT EGO RY SA L ES A M O UN T B L UE REVEN UE
The CALCULATE function evaluates the sum of the Sales table Sales Amount column in a modified filter
context. A new filter is added to the Product table Color column—or, the filter overwrites any filter that's
already applied to the column.
The following Sales table measure definition produces a ratio of sales over sales for all sales channels.
C H A N N EL SA L ES A M O UN T REVEN UE % TOTA L C H A N N EL
The DIVIDE function divides an expression that sums of the Sales table Sales Amount column value (in the
filter context) by the same expression in a modified filter context. It's the CALCULATE function that modifies the
filter context by using the REMOVEFILTERS function, which is a filter modifier function. It removes filters from
the Sales Order table Channel column.
The following Customer table calculated column definition classifies customers into a loyalty class. It's a very
simple scenario: When the revenue produced by the customer is less than $2500, they're classified as Low ;
otherwise they're High.
Customer Segment =
IF(
CALCULATE(SUM(Sales[Sales Amount]), ALLEXCEPT(Customer, Customer[CustomerKey])) < 2500,
"Low",
"High"
)
In this example, row context is converted to the filter context. It's known as context transition. The ALLEXCEPT
function removes filters from all Customer table columns except the CustomerKey column.
See also
Filter context
Row context
CALCULATETABLE function
Filter functions
CALCULATETABLE
9/15/2021 • 3 minutes to read
NOTE
There's also the CALCULATE function. It performs exactly the same functionality, except it modifies the filter context
applied to an expression that returns a scalar value.
Syntax
CALCULATETABLE(<expression>[, <filter1> [, <filter2> [, …]]])
Parameters
T ERM DEF IN IT IO N
The expression used as the first parameter must be a model table or a function that returns a table.
Filters can be:
Boolean filter expressions
Table filter expressions
Filter modification functions
When there are multiple filters, they're evaluated by using the AND logical operator. That means all conditions
must be TRUE at the same time.
Boolean filter expressions
A Boolean expression filter is an expression that evaluates to TRUE or FALSE. There are several rules that they
must abide by:
They can reference only a single column.
They cannot reference measures.
They cannot use a nested CALCULATE function.
Beginning with the September 2021 release of Power BI Desktop, the following also apply:
They cannot use functions that scan or return a table unless they are passed as arguments to aggregation
functions.
They can contain an aggregation function that returns a scalar value.
Table filter expression
A table expression filter applies a table object as a filter. It could be a reference to a model table, but more likely
it's a function that returns a table object. You can use the FILTER function to apply complex filter conditions,
including those that cannot be defined by a Boolean filter expression.
Filter modifier functions
Filter modifier functions allow you to do more than simply add filters. They provide you with additional control
when modifying filter context.
F UN C T IO N P URP O SE
ALL 1 , ALLEXCEPT, ALLNOBLANKROW Remove filters from one or more columns, or from all
columns of a single table.
1 The ALL
function and its variants behave as both filter modifiers and as functions that return table objects. If
the REMOVEFILTERS function is supported by your tool, it's better to use it to remove filters.
Return value
A table of values.
Remarks
When filter expressions are provided, the CALCULATETABLE function modifies the filter context to
evaluate the expression. For each filter expression, there are two possible standard outcomes when the
filter expression is not wrapped in the KEEPFILTERS function:
If the columns (or tables) aren't in the filter context, then new filters will be added to the filter context
to evaluate the expression.
If the columns (or tables) are already in the filter context, the existing filters will be overwritten by the
new filters to evaluate the CALCULATETABLE expression.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example uses the CALCULATETABLE function to get the sum of Internet sales for 2006. This value
is later used to calculate the ratio of Internet sales compared to all sales for the year 2006.
The following formula:
= SUMX(
CALCULATETABLE(
'InternetSales_USD',
'DateTime'[CalendarYear] = 2006
),
[SalesAmount_USD]
)
See also
Filter context
CALCULATE function (DAX)
Filter functions (DAX)
EARLIER
8/25/2021 • 4 minutes to read
Returns the current value of the specified column in an outer evaluation pass of the mentioned column.
EARLIER is useful for nested calculations where you want to use a certain value as an input and produce
calculations based on that input. In Microsoft Excel, you can do such calculations only within the context of the
current row; however, in DAX you can store the value of the input and then make calculation using data from the
entire table.
EARLIER is mostly used in the context of calculated columns.
Syntax
EARLIER(<column>, <number>)
Parameters
T ERM DEF IN IT IO N
Return value
The current value of row, from column , at number of outer evaluation passes.
Exceptions
Description of errors
Remarks
EARLIER succeeds if there is a row context prior to the beginning of the table scan. Otherwise it returns
an error.
The performance of EARLIER might be slow because it theoretically, it might have to perform a number
of operations that is close to the total number of rows (in the column) times the same number
(depending on the syntax of the expression). For example if you have 10 rows in the column,
approximately a 100 operations could be required; if you have 100 rows then close to 10,000 operations
might be performed.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
NOTE
In practice, the VertiPaq in-memory analytics engine performs optimizations to reduce the actual number of calculations,
but you should be cautious when creating formulas that involve recursion.
Example
To illustrate the use of EARLIER, it is necessary to build a scenario that calculates a rank value and then uses that
rank value in other calculations.
The following example is based on this simple table, ProductSubcategor y , which shows the total sales for
each ProductSubcategory.
The final table, including the ranking column is shown here.
18 Bib-Shorts $156,167.88 18
6 Brakes $62,113.16 23
19 Caps $47,934.54 28
7 Chains $8,847.08 35
29 Cleaners $16,882.62 32
8 Cranksets $191,522.09 15
9 Derailleurs $64,965.33 22
30 Fenders $41,974.10 29
10 Forks $74,727.66 21
20 Gloves $228,353.58 12
4 Handlebars $163,257.06 17
11 Headsets $57,659.99 25
31 Helmets $451,192.31 9
21 Jerseys $699,429.78 7
33 Lights 36
34 Locks $15,059.47 33
35 Panniers 36
13 Pedals $140,422.20 19
36 Pumps $12,695.18 34
15 Saddles $52,526.47 26
22 Shorts $385,707.80 10
23 Socks $28,337.85 31
24 Tights $189,179.37 16
25 Vests $240,990.04 11
17 Wheels $648,240.04 8
= COUNTROWS(FILTER(ProductSubcategory, EARLIER(ProductSubcategory[TotalSubcategorySales])
<ProductSubcategory[TotalSubcategorySales]))+1
The following steps describe the method of calculation in more detail.
1. The EARLIER function gets the value of TotalSubcategorySales for the current row in the table. In this
case, because the process is starting, it is the first row in the table
2. EARLIER ([TotalSubcategorySales]) evaluates to $156,167.88, the current row in the outer loop.
3. The FILTER function now returns a table where all rows have a value of TotalSubcategorySales larger
than $156,167.88 (which is the current value for EARLIER ).
4. The COUNTROWS function counts the rows of the filtered table and assigns that value to the new
calculated column in the current row plus 1. Adding 1 is needed to prevent the top ranked value from
become a Blank.
5. The calculated column formula moves to the next row and repeats steps 1 to 4. These steps are repeated
until the end of the table is reached.
The EARLIER function will always get the value of the column prior to the current table operation. If you need to
get a value from the loop before that, set the second argument to 2.
See also
EARLIEST function
Filter functions
EARLIEST
8/25/2021 • 2 minutes to read
Returns the current value of the specified column in an outer evaluation pass of the specified column.
Syntax
EARLIEST(<column>)
Parameters
T ERM DEF IN IT IO N
Return value
A column with filters removed.
Remarks
The EARLIEST function is similar to EARLIER, but lets you specify one additional level of recursion.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The current sample data does not support this scenario.
= EARLIEST(<column>)
See also
EARLIER function
Filter functions
FILTER
8/25/2021 • 2 minutes to read
Syntax
FILTER(<table>,<filter>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing only the filtered rows.
Remarks
You can use FILTER to reduce the number of rows in the table that you are working with, and use only
specific data in calculations. FILTER is not used independently, but as a function that is embedded in other
functions that require a table as an argument.
For best practices when using FILTER, see Avoid using FILTER as a filter argument.
Use COUNTROWS instead of COUNT in DAX
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following example creates a report of Internet sales outside the United States by using a measure that filters
out sales in the United States, and then slicing by calendar year and product categories. To create this measure,
you filter the table, Internet Sales USD, by using Sales Territory, and then use the filtered table in a SUMX
function.
In this example, the expression:
Returns a table that is a subset of Internet Sales minus all rows that belong to the United States sales territory.
The RELATED function is what links the Territory key in the Internet Sales table to SalesTerritoryCountry in the
SalesTerritory table.
The following table demonstrates the proof of concept for the measure, NON USA Internet Sales, the formula
for which is provided in the code section below. The table compares all Internet sales with non- USA Internet
sales, to show that the filter expression works, by excluding United States sales from the computation.
To re-create this table, add the field, SalesTerritoryCountry, to the Row Labels area of a report or PivotTable.
Table 1. Comparing total sales for U.S. vs. all other regions
RO W L A B EL S IN T ERN ET SA L ES N O N USA IN T ERN ET SA L ES
The final report table shows the results when you create a PivotTable by using the measure, NON USA Internet
Sales. Add the field, CalendarYear, to the Row Labels area of the PivotTable and add the field,
ProductCategoryName, to the Column Labels area.
Table 2. Comparing non- U.S. sales by product categories
RO W L A B EL S A C C ESSO RIES B IK ES C LOT H IN G GRA N D TOTA L
See also
Filter functions
ALL function
ALLEXCEPT function
KEEPFILTERS
8/25/2021 • 3 minutes to read
Modifies how filters are applied while evaluating a CALCULATE or CALCULATETABLE function.
Syntax
KEEPFILTERS(<expression>)
Parameters
T ERM DEF IN IT IO N
Return value
A table of values.
Remarks
You use KEEPFILTERS within the context CALCULATE and CALCULATETABLE functions, to override the
standard behavior of those functions.
By default, filter arguments s in functions such as CALCULATE are used as the context for evaluating the
expression, and as such filter arguments for CALCULATE replace all existing filters over the same
columns. The new context effected by the filter argument for CALCULATE affects only existing filters on
columns mentioned as part of the filter argument. Filters on columns other than those mentioned in the
arguments of CALCULATE or other related functions remain in effect and unaltered.
The KEEPFILTERS function allows you to modify this behavior. When you use KEEPFILTERS, any existing
filters in the current context are compared with the columns in the filter arguments, and the intersection
of those arguments is used as the context for evaluating the expression. The net effect over any one
column is that both sets of arguments apply: both the filter arguments used in CALCULATE and the filters
in the arguments of the KEEPFILTER function. In other words, whereas CALCULATE filters replace the
current context, KEEPFILTERS adds filters to the current context.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example takes you through some common scenarios that demonstrate use of the KEEPFILTERS
function as part of a CALCULATE or CALCULATETABLE formula.
The first three expressions obtain simple data to be used for comparisons:
Internet Sales for the state of Washington.
Internet Sales for the states of Washington and Oregon (both states combined).
Internet Sales for the state of Washington and the province of British Columbia (both regions combined).
The fourth expression calculates Internet Sales for Washington and Oregon, while the filter for Washington and
British Columbia is applied.
The next expression calculates Internet Sales for Washington and Oregon but uses KEEPFILTERS; the filter for
Washington and British Columbia is part of the prior context.
EVALUATE ROW(
"$$ in WA"
, CALCULATE('Internet Sales'[Internet Total Sales]
, 'Geography'[State Province Code]="WA"
)
, "$$ in WA and OR"
, CALCULATE('Internet Sales'[Internet Total Sales]
, 'Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="OR"
)
, "$$ in WA and BC"
, CALCULATE('Internet Sales'[Internet Total Sales]
, 'Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="BC"
)
, "$$ in WA and OR ??"
, CALCULATE(
CALCULATE('Internet Sales'[Internet Total Sales]
,'Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="OR"
)
, 'Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="BC"
)
, "$$ in WA !!"
, CALCULATE(
CALCULATE('Internet Sales'[Internet Total Sales]
, KEEPFILTERS('Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="OR"
)
)
, 'Geography'[State Province Code]="WA"
|| 'Geography'[State Province Code]="BC"
)
)
When this expression is evaluated against the sample database AdventureWorks DW, the following results are
obtained.
C O L UM N VA L UE
First, examine the expression, [$$ in WA and OR ??] . You might wonder how this formula could return the
value for sales in Washington and Oregon, since the outer CALCULATE expression includes a filter for
Washington and British Columbia. The answer is that the default behavior of CALCULATE overrides the outer
filters in 'Geography'[State Province Code] and substitutes its own filter arguments, because the filters apply to
the same column.
Next, examine the expression, [$$ in WA !!] . You might wonder how this formula could return the value for
sales in Washington and nothing else, since the argument filter includes Oregon and the outer CALCULATE
expression includes a filter in Washington and British Columbia. The answer is that KEEPFILTERS modifies the
default behavior of CALCULATE and adds an additional filter. Because the intersection of filters is used, now the
outer filter 'Geography'[State Province Code]="WA" || 'Geography'[State Province Code]="BC") is
added to the filter argument 'Geography'[State Province Code]="WA" || 'Geography'[State Province
Code]="OR" ,. Because both filters apply to the same column, the resulting filter 'Geography'[State Province
Code]="WA" is the filter that is applied when evaluating the expression.
See also
Filter functions
CALCULATE function
CALCULATETABLE function
LOOKUPVALUE
9/15/2021 • 2 minutes to read
Returns the value for the row that meets all criteria specified by one or more search conditions.
Syntax
LOOKUPVALUE(
<result_columnName>,
<search_columnName>,
<search_value>
[, <search2_columnName>, <search2_value>]…
[, <alternateResult>]
)
Parameters
T ERM DEF IN IT IO N
result_columnName The name of an existing column that contains the value you
want to return. It cannot be an expression.
Return value
The value of result_column at the row where all pairs of search_column and search_value have an exact
match.
If there's no match that satisfies all the search values, BLANK or alternateResult (if supplied) is returned. In
other words, the function won't return a lookup value if only some of the criteria match.
If multiple rows match the search values and in all cases result_column values are identical, then that value is
returned. However, if result_column returns different values, an error or alternateResult (if supplied) is
returned.
Remarks
If there is a relationship between the result and search tables, in most cases, using RELATED function
instead of LOOKUPVALUE is more efficient and provides better performance.
The search_value and alternateResult parameters are evaluated before the function iterates through
the rows of the search table.
Avoid using ISERROR or IFERROR functions to capture an error returned by LOOKUPVALUE. If some
inputs to the function will result in an error when a single output value cannot be determined, providing
an alternateResult parameter is the most reliable and highest performing way to handle the error.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
Examples in this article can be added to the Power BI Desktop sample model. To get the model, see DAX sample
model.
The following calculated column defined in the Sales table uses the LOOKUPVALUE function to return channel
values from the Sales Order table.
However, in this case, because there is a relationship between the Sales Order and Sales tables, it's more
efficient to use the RELATED function.
See also
RELATED function (DAX)
Information functions
REMOVEFILTERS
8/25/2021 • 2 minutes to read
Syntax
REMOVEFILTERS([<table> | <column>[, <column>[, <column>[,…]]]])
Parameters
T ERM DEF IN IT IO N
Return value
N/A. See remarks.
Remarks
REMOVEFILTERS can only be used to clear filters but not to return a table.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
DAX query
DEFINE
MEASURE FactInternetSales[TotalSales] = SUM(FactInternetSales[SalesAmount])
MEASURE FactInternetSales[%Sales] = DIVIDE([TotalSales], CALCULATE([TotalSales],REMOVEFILTERS()))
EVALUATE
SUMMARIZECOLUMNS(
ROLLUPADDISSUBTOTAL(DimProductCategory[EnglishProductCategoryName], "IsGrandTotal"),
"TotalSales", [TotalSales],
"%Sales", [%Sales]
)
ORDER BY
[IsGrandTotal] DESC, [TotalSales] DESC
Returns
DIM P RO DUC TC AT EGO RY [ E
N GL ISH P RO DUC TC AT EGO R
Y N A M E] [ ISGRA N DTOTA L ] [ TOTA L SA L ES] [ % SA L ES]
Example 2
DAX query
DEFINE
MEASURE FactInternetSales[TotalSales] = SUM(FactInternetSales[SalesAmount])
MEASURE FactInternetSales[%Sales] = DIVIDE([TotalSales],
CALCULATE([TotalSales],REMOVEFILTERS(DimProductSubcategory[EnglishProductSubcategoryName])))
EVALUATE
SUMMARIZECOLUMNS(
DimProductCategory[EnglishProductCategoryName],
DimProductSubcategory[EnglishProductSubcategoryName],
"TotalSales", [TotalSales],
"%Sales", [%Sales]
)
ORDER BY
DimProductCategory[EnglishProductCategoryName] ASC,
DimProductSubcategory[EnglishProductSubcategoryName] ASC
Returns
Returns the value when the context for columnName has been filtered down to one distinct value only.
Otherwise returns alternateResult.
Syntax
SELECTEDVALUE(<columnName>[, <alternateResult>])
Parameters
T ERM DEF IN IT IO N
Return value
The value when the context for columnName has been filtered down to one distinct value only. Else,
alternateResult.
Remarks
An equivalent expression for SELECTEDVALUE(<columnName>, <alternateResult>) is
IF(HASONEVALUE(<columnName>), VALUES(<columnName>), <alternateResult>) .
To learn more about best practices when using SELECTEDVALUE, see Use SELECTEDVALUE instead of
VALUES in DAX.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
DEFINE
MEASURE DimProduct[Selected Color] = SELECTEDVALUE(DimProduct[Color], "No Single Selection")
EVALUATE
SUMMARIZECOLUMNS
(ROLLUPADDISSUBTOTAL(DimProduct[Color], "Is Total"),
"Selected Color", [Selected Color])ORDER BY [Is Total] ASC,
[Color] ASC
NA FALSE NA
Financial functions in DAX are used in formulas that perform financial calculations, such as net present value
and rate of return. These functions are similar to financial functions used in Microsoft Excel.
In this category
F UN C T IO N DESC RIP T IO N
ACCRINT Returns the accrued interest for a security that pays periodic
interest.
ACCRINTM Returns the accrued interest for a security that pays interest
at maturity.
COUPDAYSNC Returns the number of days from the settlement date to the
next coupon date.
COUPNCD Returns the next coupon date after the settlement date.
EFFECT Returns the effective annual interest rate, given the nominal
annual interest rate and the number of compounding
periods per year.
ISPMT Calculates the interest paid (or received) for the specified
period of a loan (or investment) with even principal
payments.
NOMINAL Returns the nominal annual interest rate, given the effective
rate and the number of compounding periods per year.
ODDFPRICE Returns the price per $100 face value of a security having an
odd (short or long) first period.
ODDLPRICE Returns the price per $100 face value of a security having an
odd (short or long) last coupon period.
PPMT Returns the payment on the principal for a given period for
an investment based on periodic, constant payments and a
constant interest rate.
PRICE Returns the price per $100 face value of a security that pays
periodic interest.
PRICEMAT Returns the price per $100 face value of a security that pays
interest at maturity.
TBILLPRICE Returns the price per $100 face value for a Treasury bill.
XNPV Returns the present value for a schedule of cash flows that is
not necessarily periodic.
Returns the accrued interest for a security that pays periodic interest.
Syntax
ACCRINT(<issue>, <first_interest>, <settlement>, <rate>, <par>, <frequency>[, <basis>[, <calc_method>]])
Parameters
T ERM DEF IN IT IO N
1 Actual/actual
2 Actual/360
B A SIS DAY C O UN T B A SIS
3 Actual/365
4 European 30/360
Return Value
The accrued interest.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
ACCRINT is calculated as follows:
$$\text{ACCRINT} = \text{par} \times \frac{\text{rate}}{\text{frequency}} \times
\sum^{\text{NC}}_{i=1}\frac{\text{A}_{i}}{\text{NL}_{i}}$$
where:
$\text{A}_{i}$ = number of accrued days for the $i^{th}$ quasi-coupon period within odd period.
$\text{NC}$ = number of quasi-coupon periods that fit in odd period. If this number contains a
fraction, raise it to the next whole number.
$\text{NL}_{i}$ = normal length in days of the quasi-coupon period within odd period.
issue, first_interest, and settlement are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
issue, first_interest, or settlement is not a valid date.
issue ≥ settlement.
rate ≤ 0.
par ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
Example 1
The following DAX query:
EVALUATE
{
ACCRINT(DATE(2007,3,1), DATE(2008,8,31), DATE(2008,5,1), 0.1, 1000, 2, 0)
}
Returns the accrued interest from issue to settlement, for a security with the terms specified above.
[ VA L UE]
116.944444444444
Example 2
The following DAX query:
EVALUATE
{
ACCRINT(DATE(2007,3,1), DATE(2008,8,31), DATE(2008,5,1), 0.1, 1000, 2, 0, FALSE)
}
Returns the accrued interest from first_interest to settlement, for a security with the terms specified above.
[ VA L UE]
66.9444444444445
ACCRINTM
8/25/2021 • 2 minutes to read
Returns the accrued interest for a security that pays interest at maturity.
Syntax
ACCRINTM(<issue>, <maturity>, <rate>, <par>[, <basis>])
Parameters
T ERM DEF IN IT IO N
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The accrued interest.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
ACCRINTM is calculated as follows:
$$\text{ACCRINTM} = \text{par} \times \text{rate} \times \frac{\text{A}}{\text{D}}$$
where:
$\text{A}$ = Number of accrued days counted according to a monthly basis. For interest at maturity
items, the number of days from the issue date to the maturity date is used.
$\text{D}$ = Annual Year Basis.
issue and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
issue or maturity is not a valid date.
issue ≥ maturity.
rate ≤ 0.
par ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
ACCRINTM(DATE(2008,4,1), DATE(2008,6,15), 0.1, 1000, 3)
}
Returns the accrued interest for a security with the terms specified above.
[ VA L UE]
20.5479452054795
AMORDEGRC
8/25/2021 • 2 minutes to read
Returns the depreciation for each accounting period. This function is provided for the French accounting system.
If an asset is purchased in the middle of the accounting period, the prorated depreciation is taken into account.
The function is similar to AMORLINC, except that a depreciation coefficient is applied in the calculation
depending on the life of the assets.
Syntax
AMORDEGRC(<cost>, <date_purchased>, <first_period>, <salvage>, <period>, <rate>[, <basis>])
Parameters
T ERM DEF IN IT IO N
salvage The salvage value at the end of the life of the asset.
B A SIS DAT E SY ST EM
1 Actual
Return Value
The depreciation for each accounting period.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
This function will return the depreciation until the last period of the life of the assets or until the
cumulated value of depreciation is greater than the cost of the assets minus the salvage value.
The depreciation coefficients are:
The depreciation rate will grow to 50 percent for the period preceding the last period and will grow to
100 percent for the last period.
period and basis are rounded to the nearest integer.
An error is returned if:
cost < 0.
first_period or date_purchased is not a valid date.
date_purchased > first_period.
salvage < 0 or salvage > cost.
period < 0.
rate ≤ 0.
The life of assets is between 0 (zero) and 1, 1 and 2, 2 and 3, or 4 and 5.
basis is any number other than 0, 1, 3, or 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
2400 Cost
1 Period
EVALUATE
{
AMORDEGRC(2400, DATE(2008,8,19), DATE(2008,12,31), 300, 1, 0.15, 1)
}
Returns the first period's depreciation, given the terms specified above.
[ VA L UE]
776
AMORLINC
8/25/2021 • 2 minutes to read
Returns the depreciation for each accounting period. This function is provided for the French accounting system.
If an asset is purchased in the middle of the accounting period, the prorated depreciation is taken into account.
Syntax
AMORLINC(<cost>, <date_purchased>, <first_period>, <salvage>, <period>, <rate>[, <basis>])
Parameters
T ERM DEF IN IT IO N
salvage The salvage value at the end of the life of the asset.
B A SIS DAT E SY ST EM
1 Actual
Return Value
The depreciation for each accounting period.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
period and basis are rounded to the nearest integer.
An error is returned if:
cost < 0.
first_period or date_purchased is not a valid date.
date_purchased > first_period.
salvage < 0 or salvage > cost.
period < 0.
rate ≤ 0.
basis is any number other than 0, 1, 3, or 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
2400 Cost
1 Period
EVALUATE
{
AMORLINC(2400, DATE(2008,8,19), DATE(2008,12,31), 300, 1, 0.15, 1)
}
Returns the first period's depreciation, given the terms specified above.
[ VA L UE]
360
COUPDAYBS
8/25/2021 • 2 minutes to read
Returns the number of days from the beginning of a coupon period until its settlement date.
Syntax
COUPDAYBS(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The number of days from the beginning of a coupon period until its settlement date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, 30 years after the January 1,
2008, issue date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPDAYBS(DATE(2011,1,25), DATE(2011,11,15), 2, 1)
}
Returns the number of days from the beginning of the coupon period until the settlement date, for a bond with
terms above.
[ VA L UE]
71
COUPDAYS
8/25/2021 • 2 minutes to read
Returns the number of days in the coupon period that contains the settlement date.
Syntax
COUPDAYS(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The number of days in the coupon period that contains the settlement date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date is January 1, 2038, 30 years after the January 1, 2008 issue
date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPDAYS(DATE(2011,1,25), DATE(2011,11,15), 2, 1)
}
Returns the number of days in the coupon period that contains the settlement date, for a bond with the terms
specified above.
[ VA L UE]
181
COUPDAYSNC
8/25/2021 • 2 minutes to read
Returns the number of days from the settlement date to the next coupon date.
Syntax
COUPDAYSNC(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The number of days from the settlement date to the next coupon date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPDAYSNC(DATE(2011,1,25), DATE(2011,11,15), 2, 1)
}
Returns the number of days from the settlement date to the next coupon date, for a bond with the terms
specified above.
[ VA L UE]
110
COUPNCD
8/25/2021 • 2 minutes to read
Syntax
COUPNCD(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The next coupon date after the settlement date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date is January 1, 2038, 30 years after the January 1, 2008 issue
date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPNCD(DATE(2011,1,25), DATE(2011,11,15), 2, 1)
}
Returns the next coupon date after the settlement date, for a bond with the terms specified above.
[ VA L UE]
5/15/2011 12:00:00 AM
COUPNUM
8/25/2021 • 2 minutes to read
Returns the number of coupons payable between the settlement date and maturity date, rounded up to the
nearest whole coupon.
Syntax
COUPNUM(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The number of coupons payable between the settlement date and maturity date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPNUM(DATE(2007,1,25), DATE(2008,11,15), 2, 1)
}
Returns the number of coupon payments for a bond with the terms specified above.
[ VA L UE]
4
COUPPCD
8/25/2021 • 2 minutes to read
Syntax
COUPPCD(<settlement>, <maturity>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The previous coupon date before the settlement date.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement and maturity are truncated to integers.
frequency and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
COUPPCD(DATE(2011,1,25), DATE(2011,11,15), 2, 1)
}
Returns the previous coupon date before the settlement date, for a bond using the terms specified above.
[ VA L UE]
11/15/2010 12:00:00 AM
CUMIPMT
8/25/2021 • 2 minutes to read
Returns the cumulative interest paid on a loan between start_period and end_period.
Syntax
CUMIPMT(<rate>, <nper>, <pv>, <start_period>, <end_period>, <type>)
Parameters
T ERM DEF IN IT IO N
type The timing of the payment. The accepted values are listed
below this table.
TYPE T IM IN G
Return Value
The cumulative interest paid in the specified period.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at an annual interest rate of 10 percent, use 0.1/12 for rate and
4*12 for nper. If you make annual payments on the same loan, use 0.1 for rate and 4 for nper.
start_period, end_period, and type are rounded to the nearest integer.
An error is returned if:
rate ≤ 0.
nper < 1.
pv ≤ 0.
start_period < 1 or start_period > end_period.
end_period < start_period or end_period > nper.
type is any number other than 0 or 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
Example 1
The following DAX query:
EVALUATE
{
CUMIPMT(0.09/12, 30*12, 125000, 13, 24, 1)
}
Returns the total interest paid in the second year of payments, periods 13 through 24, assuming that the
payments are made at the beginning of each month.
[ VA L UE]
-11052.3395838718
Example 2
The following DAX query:
EVALUATE
{
CUMIPMT(0.09/12, 30*12, 125000, 1, 1, 0)
}
Returns the interest paid in a single payment in the first month, assuming that the payment is made at the end
of the month.
[ VA L UE]
-937.5
CUMPRINC
8/25/2021 • 2 minutes to read
Returns the cumulative principal paid on a loan between start_period and end_period.
Syntax
CUMPRINC(<rate>, <nper>, <pv>, <start_period>, <end_period>, <type>)
Parameters
T ERM DEF IN IT IO N
type The timing of the payment. The accepted values are listed
below this table.
TYPE T IM IN G
Return Value
The cumulative principal paid in the specified period.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at an annual interest rate of 10 percent, use 0.1/12 for rate and
4*12 for nper. If you make annual payments on the same loan, use 0.1 for rate and 4 for nper.
start_period, end_period, and type are rounded to the nearest integer.
An error is returned if:
rate ≤ 0.
nper < 1.
pv ≤ 0.
start_period < 1 or start_period > end_period.
end_period < start_period or end_period > nper.
type is any number other than 0 or 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
30 Term in years
Example 1
The following DAX query:
EVALUATE
{
CUMPRINC(0.09/12, 30*12, 125000, 13, 24, 1)
}
Returns the total principal paid in the second year of payments, periods 13 through 24, assuming the payments
are made at the beginning of each month.
[ VA L UE]
-927.153472378062
Example 2
The following DAX query:
EVALUATE
{
CUMPRINC(0.09/12, 30*12, 125000, 1, 1, 0)
}
Returns the principal paid in a single payment in the first month, assuming the payment is made at the end of
the month.
[ VA L UE]
-68.2782711809784
DB
8/25/2021 • 2 minutes to read
Returns the depreciation of an asset for a specified period using the fixed-declining balance method.
Syntax
DB(<cost>, <salvage>, <life>, <period>[, <month>])
Parameters
T ERM DEF IN IT IO N
period The period for which you want to calculate the depreciation.
Period must use the same units as life. Must be between 1
and life (inclusive).
Return Value
The depreciation over the specified period.
Remarks
The fixed-declining balance method computes depreciation at a fixed rate. DB uses the following formulas
to calculate depreciation for a period:
$$(\text{cost} - \text{total depreciation from prior periods}) \times \text{rate}$$
where:
$\text{rate} = 1 - ((\frac{\text{salvage}}{\text{cost}})^{(\frac{1}{\text{life}})})\text{, rounded to three
decimal places}$
Depreciation for the first and last periods is a special case.
For the first period, DB uses this formula:
$$\frac{\text{cost} \times \text{rate} \times \text{month}}{12}$$
For the last period, DB uses this formula:
$$\frac{(\text{cost} - \text{total depreciation from prior periods}) \times \text{rate} \times (12 -
\text{month})}{12}$$
period and month are rounded to the nearest integer.
An error is returned if:
cost < 0.
salvage < 0.
life < 1.
period < 1 or period > life.
month < 1 or month > 12.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
Example 1
The following DAX query:
EVALUATE
{
DB(1000000, 0, 6, 1, 2)
}
Returns an asset's depreciation in the last two months of the first year, assuming it will be worth \$0 after 6
years.
[ VA L UE]
166666.666666667
Example 2
The following calculates the total depreciation of all assets in different years over their lifetimes. Here, the first
year only includes 7 months of depreciation, and the last year only includes 5 months.
DEFINE
VAR NumDepreciationPeriods = MAX(Asset[LifeTimeYears])+1
VAR DepreciationPeriods = GENERATESERIES(1, NumDepreciationPeriods)
EVALUATE
ADDCOLUMNS (
DepreciationPeriods,
"Current Period Total Depreciation",
SUMX (
FILTER (
Asset,
[Value] <= [LifetimeYears]+1
),
DB([InitialCost], [SalvageValue], [LifetimeYears], [Value], 7)
)
)
DDB
8/25/2021 • 2 minutes to read
Returns the depreciation of an asset for a specified period using the double-declining balance method or some
other method you specify.
Syntax
DDB(<cost>, <salvage>, <life>, <period>[, <factor>])
Parameters
T ERM DEF IN IT IO N
period The period for which you want to calculate the depreciation.
Period must use the same units as life. Must be between 1
and life (inclusive).
Return Value
The depreciation over the specified period.
Remarks
The double-declining balance method computes depreciation at an accelerated rate. Depreciation is
highest in the first period and decreases in successive periods. DDB uses the following formula to
calculate depreciation for a period:
$$\text{Min}((\text{cost} - \text{total depreciation from prior periods}) \times (\frac{\text{factor}}
{\text{life}}),(\text{cost} - \text{salvage} - \text{total depreciation from prior periods}))$$
Change factor if you do not want to use the double-declining balance method.
Use the VDB function if you want to switch to the straight-line depreciation method when depreciation is
greater than the declining balance calculation.
period is rounded to the nearest integer.
An error is returned if:
cost < 0.
salvage < 0.
life < 1.
period < 1 or period > life.
factor ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
Example 1
The following DAX query:
EVALUATE
{
DDB(1000000, 0, 10, 5, 1.5)
}
Returns an asset's depreciation in the 5$^{th}$ year, assuming it will be worth \$0 after 10 years. This
calculation uses a factor of 1.5.
[ VA L UE]
78300.9375
Example 2
The following calculates the total depreciation of all assets in different years over their lifetimes. This calculation
uses the default factor of 2 (the double-declining balance method).
DEFINE
VAR NumDepreciationPeriods = MAX(Asset[LifeTimeYears])
VAR DepreciationPeriods = GENERATESERIES(1, NumDepreciationPeriods)
EVALUATE
ADDCOLUMNS (
DepreciationPeriods,
"Current Period Total Depreciation",
SUMX (
FILTER (
Asset,
[Value] <= [LifetimeYears]
),
DDB([InitialCost], [SalvageValue], [LifetimeYears], [Value])
)
)
DISC
8/25/2021 • 2 minutes to read
Syntax
DISC(<settlement>, <maturity>, <pr>, <redemption>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The discount rate.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2018, and is
purchased by a buyer six months later. The issue date would be January 1, 2018, the settlement date
would be July 1, 2018, and the maturity date would be January 1, 2048, 30 years after the January 1,
2018, issue date.
DISC is calculated as follows:
$$\text{DISC} = \frac{\text{redemption} - \text{par}}{\text{redemption}} \times \frac{\text{B}}
{\text{DSM}}$$
where:
$\text{B}$ = number of days in a year, depending on the year basis.
$\text{DSM}$ = number of days between settlement and maturity.
settlement and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
pr ≤ 0.
redemption ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
97.975 Price
EVALUATE
{
DISC(DATE(2018,7,1), DATE(2048,1,1), 97.975, 100, 1)
}
Returns the bond discount rate, for a bond with the terms specified above.
[ VA L UE]
0.000686384169121348
DOLLARDE
8/25/2021 • 2 minutes to read
Converts a dollar price expressed as an integer part and a fraction part, such as 1.02, into a dollar price
expressed as a decimal number. Fractional dollar numbers are sometimes used for security prices.
Syntax
DOLLARDE(<fractional_dollar>, <fraction>)
Parameters
T ERM DEF IN IT IO N
Return Value
The decimal value of fractional_dollar.
Remarks
The fraction part of the value is divided by an integer that you specify. For example, if you want your price
to be expressed to a precision of 1/16 of a dollar, you divide the fraction part by 16. In this case, 1.02
represents \$1.125 (\$1 + 2/16 = \$1.125).
fraction is rounded to the nearest integer.
An error is returned if:
fraction < 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
EVALUATE
{
DOLLARDE(1.02, 16)
}
Returns 1.125, the decimal price of the original fractional price, 1.02, read as 1 and 2/16. Since the fraction value
is 16, the price has a precision of 1/16 of a dollar.
DOLLARFR
8/25/2021 • 2 minutes to read
Converts a dollar price expressed as a decimal number into a dollar price expressed as an integer part and a
fraction part, such as 1.02. Fractional dollar numbers are sometimes used for security prices.
Syntax
DOLLARFR(<decimal_dollar>, <fraction>)
Parameters
T ERM DEF IN IT IO N
Return Value
The fractional value of decimal_dollar, expressed as an integer part and a fraction part.
Remarks
fraction is rounded to the nearest integer.
An error is returned if:
fraction < 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
EVALUATE
{
DOLLARFR(1.125, 16)
}
Returns 1.02, read as 1 and 2/16, which is the corresponding fraction price of the original decimal price, 1.125.
Since the fraction value is 16, the price has a precision of 1/16 of a dollar.
DURATION
8/25/2021 • 2 minutes to read
Returns the Macauley duration for an assumed par value of \$100. Duration is defined as the weighted average
of the present value of cash flows, and is used as a measure of a bond price's response to changes in yield.
Syntax
DURATION(<settlement>, <maturity>, <coupon>, <yld>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The Macauley duration.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date is January 1, 2038, which is 30 years after the January 1,
2008, issue date.
settlement and maturity are truncated to integers.
frequency, and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
coupon < 0.
yld < 0
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
DURATION(DATE(2018,7,1), DATE(2048,1,1), 0.08, 0.09, 2, 1)
}
Returns the Macauley duration for a bond with the terms specified above.
[ VA L UE]
10.9191452815919
EFFECT
8/25/2021 • 2 minutes to read
Returns the effective annual interest rate, given the nominal annual interest rate and the number of
compounding periods per year.
Syntax
EFFECT(<nominal_rate>, <npery>)
Parameters
T ERM DEF IN IT IO N
Return Value
The effective annual interest rate.
Remarks
EFFECT is calculated as follows:
$$\text{EFFECT} = \bigg( 1 + \frac{\text{nominal_rate}}{\text{npery}} \bigg)^{\text{npery}} - 1$$
npery is rounded to the nearest integer.
An error is returned if:
nominal_rate ≤ 0.
npery < 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
Returns the effective interest rate using the terms specified above.
[ VA L UE]
0.0535426673707584
FV
8/25/2021 • 2 minutes to read
Calculates the future value of an investment based on a constant interest rate. You can use FV with either
periodic, constant payments, and/or a single lump sum payment.
Syntax
FV(<rate>, <nper>, <pmt>[, <pv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
pmt The payment made each period; it cannot change over the
life of the annuity. Typically, pmt contains principal and
interest but no other fees or taxes.
Note: For a more complete description of the arguments in FV and for more information on annuity functions,
see the PV function.
Return Value
The future value of an investment.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at 12 percent annual interest, use 0.12/12 for rate and 4*12 for
nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
For all the arguments, cash you pay out, such as deposits to savings, is represented by negative numbers;
cash you receive, such as dividend checks, is represented by positive numbers.
type is rounded to the nearest integer.
An error is returned if:
nper < 1
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
10 Number of payments
EVALUATE
{
FV(0.06/12, 10, -200, -500, 1)
}
Returns the future value of an investment using the terms specified above.
[ VA L UE]
2581.40337406012
INTRATE
8/25/2021 • 2 minutes to read
Syntax
INTRATE(<settlement>, <maturity>, <investment>, <redemption>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The interest rate.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date is January 1, 2038, which is 30 years after the January 1,
2008, issue date.
INTRATE is calculated as follows:
$$\text{INTRATE} = \frac{\text{redemption} - \text{investment}}{\text{investment}} \times \frac{\text{B}}
{\text{DIM}}$$
where:
$\text{B}$ = number of days in a year, depending on the year basis.
$\text{DIM}$ = number of days from settlement to maturity.
settlement and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
investment ≤ 0.
redemption ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
\$1,000,000 Investment
2 Actual/360 basis
EVALUATE
{
INTRATE(DATE(2008,2,15), DATE(2008,5,15), 1000000, 1014420, 2)
}
Returns the discount rate for a bond using the terms specified above.
[ VA L UE]
0.05768
IPMT
8/25/2021 • 2 minutes to read
Returns the interest payment for a given period for an investment based on periodic, constant payments and a
constant interest rate.
Syntax
IPMT(<rate>, <per>, <nper>, <pv>[, <fv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
per The period for which you want to find the interest. Must be
between 1 and nper (inclusive).
Return Value
The interest payment for the given period.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at 12 percent annual interest, use 0.12/12 for rate and 4*12 for
nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
For all the arguments, cash you pay out, such as deposits to savings, is represented by negative numbers;
cash you receive, such as dividend checks, is represented by positive numbers.
type is rounded to the nearest integer.
An error is returned if:
per < 1 or per > nper
nper < 1
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
3 Years of loan
Example 1
The following DAX query:
EVALUATE
{
IPMT(0.1/12, 1, 3*12, 8000)
}
Returns the monthly interest due in the first month for a loan with the terms specified above.
[ VA L UE]
-66.6666666666667
Example 2
The following DAX query:
EVALUATE
{
IPMT(0.1, 3, 3, 8000)
}
Returns the yearly interest due in the last year for a loan with the terms specified above, where payments are
made yearly.
[ VA L UE]
-292.447129909366
ISPMT
8/25/2021 • 2 minutes to read
Calculates the interest paid (or received) for the specified period of a loan (or investment) with even principal
payments.
Syntax
ISPMT(<rate>, <per>, <nper>, <pv>)
Parameters
T ERM DEF IN IT IO N
per The period for which you want to find the interest. Must be
between 0 and nper-1 (inclusive).
Return Value
The interest paid (or received) for the specified period.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at an annual interest rate of 12 percent, use 0.12/12 for rate and
4*12 for nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
For all the arguments, the cash you pay out, such as deposits to savings or other withdrawals, is
represented by negative numbers; the cash you receive, such as dividend checks and other deposits, is
represented by positive numbers.
ISPMT counts each period beginning with zero, not one.
Most loans use a repayment schedule with even periodic payments. The IPMT function returns the
interest payment for a given period for this type of loan.
Some loans use a repayment schedule with even principal payments. The ISPMT function returns the
interest payment for a given period for this type of loan.
An error is returned if:
nper = 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
4 Number of periods
10% Rate
To illustrate when to use ISPMT, the amortization table below uses an even-principal repayment schedule with
the terms specified above. The interest charge each period is equal to the rate times the unpaid balance for the
previous period. And the payment each period is equal to the even principal plus the interest for the period.
4,000.00
DEFINE
VAR NumPaymentPeriods = 4
VAR PaymentPeriods = GENERATESERIES(0, NumPaymentPeriods-1)
EVALUATE
ADDCOLUMNS (
PaymentPeriods,
"Interest Payment",
ISPMT(0.1, [Value], NumPaymentPeriods, 4000)
)
Returns the interest paid during each period, using the even-principal repayment schedule and terms specified
above. The values are negative to indicate that it is interest paid, not received.
0 -400
1 -300
2 -200
3 -100
MDURATION
8/25/2021 • 2 minutes to read
Returns the modified Macauley duration for a security with an assumed par value of \$100.
Syntax
MDURATION(<settlement>, <maturity>, <coupon>, <yld>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The modified Macauley duration.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date is January 1, 2038, which is 30 years after the January 1,
2008, issue date.
Modified duration is defined as follows:
$$\text{MDURATION} = \frac{\text{DURATION}}{1 + (\frac{\text{Market yield}}{\text{Coupon payments
per year}})}$$
settlement and maturity are truncated to integers.
frequency, and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
coupon < 0.
yld < 0
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
8% Percent coupon
9% Percent yield
EVALUATE
{
MDURATION(DATE(2008,1,1), DATE(2016,1,1), 0.08, 0.09, 2, 1)
}
Returns the modified Macauley duration of a bond using the terms specified above.
[ VA L UE]
5.73566981391884
NOMINAL
8/25/2021 • 2 minutes to read
Returns the nominal annual interest rate, given the effective rate and the number of compounding periods per
year.
Syntax
NOMINAL(<effect_rate>, <npery>)
Parameters
T ERM DEF IN IT IO N
Return Value
The nominal annual interest rate.
Remarks
The relationship between NOMINAL and EFFECT is shown in the following equation:
$$\text{EFFECT} = \Big( 1 + \frac{\text{nominal_rate}}{\text{npery}} \Big)^{\text{npery}} - 1$$
npery is rounded to the nearest integer.
An error is returned if:
effect_rate ≤ 0.
npery < 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
Returns the nominal interest rate, using the terms specified above.
[ VA L UE]
0.052500319868356
NPER
8/25/2021 • 2 minutes to read
Returns the number of periods for an investment based on periodic, constant payments and a constant interest
rate.
Syntax
NPER(<rate>, <pmt>, <pv>[, <fv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
pmt The payment made each period; it cannot change over the
life of the annuity. Typically, pmt contains principal and
interest but no other fees or taxes.
Return Value
The number of periods for an investment.
Remarks
type is rounded to the nearest integer.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
NPER(0.12/12, -100, -1000, 10000, 1)
}
Returns the number of periods for the investment described by the terms specified above.
[ VA L UE]
59.6738656742946
ODDFPRICE
8/25/2021 • 4 minutes to read
Returns the price per \$100 face value of a security having an odd (short or long) first period.
Syntax
ODDFPRICE(<settlement>, <maturity>, <issue>, <first_coupon>, <rate>, <yld>, <redemption>, <frequency>[,
<basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
B A SIS DAY C O UN T B A SIS
4 European 30/360
Return Value
The price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
ODDFPRICE is calculated as follows:
Odd shor t first coupon:
$$\text{ODDFPRICE} = \bigg[ \frac{\text{redemption}}{(1 + \frac{\text{yld}}{\text{frequency}})^{(N - 1 +
\frac{\text{DSC}}{\text{E}})}} \bigg] + \bigg[ \frac{100 \times \frac{\text{rate}}{\text{frequency}} \times
\frac{\text{DFC}}{\text{E}}}{(1 + \frac{\text{yld}}{\text{frequency}})^{(\frac{\text{DSC}}{\text{E}})}} \bigg] +
\bigg[ \sum^{N}_{k=2} \frac{100 \times \frac{\text{rate}}{\text{frequency}}}{(1 + \frac{\text{yld}}
{\text{frequency}})^{(k - 1 + \frac{\text{DSC}}{\text{E}})}} \bigg] - \Big[ 100 \times \frac{\text{rate}}
{\text{frequency}} \times \frac{\text{A}}{\text{E}} \Big] $$
where:
$\text{A}$ = number of days from the beginning of the coupon period to the settlement date (accrued
days).
$\text{DSC}$ = number of days from the settlement to the next coupon date.
$\text{DFC}$ = number of days from the beginning of the odd first coupon to the first coupon date.
$\text{E}$ = number of days in the coupon period.
$\text{N}$ = number of coupons payable between the settlement date and the redemption date. (If
this number contains a fraction, it is raised to the next whole number.)
Odd long first coupon:
$$\text{ODDFPRICE} = \bigg[ \frac{\text{redemption}}{(1 + \frac{\text{yld}}{\text{frequency}})^{(\text{N} +
\text{N}_{q} + \frac{\text{DSC}}{\text{E}})}} \bigg] + \bigg[ \frac{100 \times \frac{\text{rate}}
{\text{frequency}} \times \Big[ \sum^{\text{NC}}_{i=1} \frac{\text{DC}_{i}}{\text{NL}_{i}} \Big] }{(1 +
\frac{\text{yld}}{\text{frequency}})^{(\text{N}_{q} + \frac{\text{DSC}}{\text{E}})}} \bigg] + \bigg[
\sum^{\text{N}}_{k=1} \frac{100 \times \frac{\text{rate}}{\text{frequency}}}{(1 + \frac{\text{yld}}
{\text{frequency}})^{(k - \text{N}_{q} + \frac{\text{DSC}}{\text{E}})}} \bigg] - \Big[ 100 \times
\frac{\text{rate}}{\text{frequency}} \times \sum^{\text{NC}}_{i=1} \frac{\text{A}_{i}}{\text{NL}_{i}} \Big]$$
where:
$\text{A}_{i}$ = number of days from the beginning of the $i^{th}$, or last, quasi-coupon period
within odd period.
$\text{DC}_{i}$ = number of days from dated date (or issue date) to first quasi-coupon ($i = 1$) or
number of days in quasi-coupon ($i = 2$,..., $i = \text{NC}$).
$\text{DSC}$ = number of days from settlement to next coupon date.
$\text{E}$ = number of days in coupon period.
$\text{N}$ = number of coupons payable between the first real coupon date and redemption date. (If
this number contains a fraction, it is raised to the next whole number.)
$\text{NC}$ = number of quasi-coupon periods that fit in odd period. (If this number contains a
fraction, it is raised to the next whole number.)
$\text{NL}_{i}$ = normal length in days of the full $i^{th}$, or last, quasi-coupon period within odd
period.
$\text{N}_{q}$ = number of whole quasi-coupon periods between settlement date and first coupon.
settlement, maturity, issue, and first_coupon are truncated to integers.
basis and frequency are rounded to the nearest integer.
An error is returned if:
settlement, maturity, issue, or first_coupon is not a valid date.
maturity > first_coupon > settlement > issue is not satisfied.
rate < 0.
yld < 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA A RGUM EN T DESC RIP T IO N
2 Frequency is semiannual
1 Actual/actual basis
Returns the price per \$100 face value of a security having an odd (short or long) first period, using the terms
specified above.
[ VA L UE]
113.597717474079
ODDFYIELD
8/25/2021 • 2 minutes to read
Returns the yield of a security that has an odd (short or long) first period.
Syntax
ODDFYIELD(<settlement>, <maturity>, <issue>, <first_coupon>, <rate>, <pr>, <redemption>, <frequency>[,
<basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
B A SIS DAY C O UN T B A SIS
4 European 30/360
Return Value
The security's yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
ODDFYIELD is calculated using an iterative method. It uses the Newton method based on the formula
used for the function ODDFPRICE. The yield is changed through 100 iterations until the estimated price
with the given yield is close to the price. See ODDFPRICE for the formula that ODDFYIELD uses.
settlement, maturity, issue, and first_coupon are truncated to integers.
basis and frequency are rounded to the nearest integer.
An error is returned if:
settlement, maturity, issue, or first_coupon is not a valid date.
maturity > first_coupon > settlement > issue is not satisfied.
rate < 0.
pr ≤ 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA A RGUM EN T DESC RIP T IO N
84.50 Price
2 Frequency is semiannual
0 30/360 basis
EVALUATE
{
ODDFYIELD(DATE(2008,11,11), DATE(2021,3,1), DATE(2008,10,15), DATE(2009,3,1), 0.0575, 84.50, 100, 2, 0)
}
Returns the yield of a security that has an odd (short or long) first period, using the terms specified above.
[ VA L UE]
0.0772455415972989
ODDLPRICE
8/25/2021 • 2 minutes to read
Returns the price per \$100 face value of a security having an odd (short or long) last coupon period.
Syntax
ODDLPRICE(<settlement>, <maturity>, <last_interest>, <rate>, <yld>, <redemption>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement, maturity, and last_interest are truncated to integers.
basis and frequency are rounded to the nearest integer.
An error is returned if:
settlement, maturity, or last_interest is not a valid date.
maturity > settlement > last_interest is not satisfied.
rate < 0.
yld < 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
2 Frequency is semiannual
0 30/360 basis
EVALUATE
{
ODDLPRICE(DATE(2008,2,7), DATE(2008,6,15), DATE(2007,10,15), 0.0375, 0.0405, 100, 2, 0)
}
Returns the price per \$100 face value of a security that has an odd (short or long) last coupon period, using the
terms specified above.
[ VA L UE]
99.8782860147213
ODDLYIELD
8/25/2021 • 2 minutes to read
Returns the yield of a security that has an odd (short or long) last period.
Syntax
ODDLYIELD(<settlement>, <maturity>, <last_interest>, <rate>, <pr>, <redemption>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The security's yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
ODDLYIELD is calculated as follows:
$$\text{ODDLYIELD} = \bigg[ \frac{(\text{redemption} + ((\sum^{\text{NC}}_{i=1} \frac{\text{DC}_{i}}
{\text{NL}_{i}}) \times \frac{100 \times \text{rate}}{\text{frequency}})) - (\text{par} +
((\sum^{\text{NC}}_{i=1} \frac{\text{A}_{i}}{\text{NL}_{i}}) \times \frac{100 \times \text{rate}}
{\text{frequency}}))}{\text{par} + ((\sum^{\text{NC}}_{i=1} \frac{\text{A}_{i}}{\text{NL}_{i}}) \times \frac{100
\times \text{rate}}{\text{frequency}})} \bigg] \times \bigg[ \frac{\text{frequency}}{(\sum^{\text{NC}}_{i=1}
\frac{\text{DSC}_{i}}{\text{NL}_{i}})} \bigg]$$
where:
$\text{A}_{i}$ = number of accrued days for the $i^{th}$, or last, quasi-coupon period within odd
period counting forward from last interest date before redemption.
$\text{DC}_{i}$ = number of days counted in the $i^{th}$, or last, quasi-coupon period as delimited by
the length of the actual coupon period.
$\text{NC}$ = number of quasi-coupon periods that fit in odd period; if this number contains a
fraction it will be raised to the next whole number.
$\text{NL}_{i}$ = normal length in days of the $i^{th}$, or last, quasi-coupon period within odd
coupon period.
settlement, maturity, last_interest are truncated to integers.
basis and frequency are rounded to the nearest integer.
An error is returned if:
settlement, maturity, last_interest is not a valid date.
maturity > settlement > last_interest is not satisfied.
rate < 0.
pr ≤ 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
DATA A RGUM EN T DESC RIP T IO N
\$99.875 Price
2 Frequency is semiannual
0 30/360 basis
EVALUATE
{
ODDLYIELD(DATE(2008,4,20), DATE(2008,6,15), DATE(2007,12,24), 0.0375, 99.875, 100, 2, 0)
}
Returns the yield of a security that has an odd (short of long) last period, using the terms specified above.
[ VA L UE]
0.0451922356291692
PDURATION
8/25/2021 • 2 minutes to read
Syntax
PDURATION(<rate>, <pv>, <fv>)
Parameters
T ERM DEF IN IT IO N
Return Value
The number of periods.
Remarks
PDURATION uses the following equation:
$$\text{PDURATION} = \frac{log(\text{fv}) - log(\text{pv})}{log(1 + \text{rate})}$$
An error is returned if:
rate ≤ 0.
pv ≤ 0.
fv ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following DAX query:
EVALUATE
{
PDURATION(0.025, 2000, 2200)
}
Returns the number of years required for an investment of \$2000, earning 2.5% annually, to reach \$2200.
[ VA L UE]
3.85986616262266
Example 2
The following DAX query:
EVALUATE
{
PDURATION(0.025/12, 1000, 1200)
}
Returns the number of months required for an investment of \$1000, earning 2.5% annually, to reach \$1200.
[ VA L UE]
87.6054764193714
PMT
8/25/2021 • 2 minutes to read
Calculates the payment for a loan based on constant payments and a constant interest rate.
Syntax
PMT(<rate>, <nper>, <pv>[, <fv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
Note: For a more complete description of the arguments in PMT, see the PV function.
Return Value
The amount of a single loan payment.
Remarks
The payment returned by PMT includes principal and interest but no taxes, reserve payments, or fees
sometimes associated with loans.
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at an annual interest rate of 12 percent, use 0.12/12 for rate and
4*12 for nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
type is rounded to the nearest integer.
An error is returned if:
nper < 1
Tip : To find the total amount paid over the duration of the loan, multiply the returned PMT value by nper.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Examples
Example 1
DATA DESC RIP T IO N
EVALUATE
{
PMT(0.08/12, 10, 10000, 0, 1)
}
Returns the monthly payment amount, paid at the beginning of the month, for a loan with the terms specified
above.
[ VA L UE]
-1030.16432717797
Note: 1030.16432717797 is the payment per period. As a result, the total amount paid over the duration of the
loan is approximately 1030.16 * 10 = \$10,301.60. In other words, approximately \$301.60 of interest is paid.
Example 2
DATA DESC RIP T IO N
[ VA L UE]
-129.081160867991
Returns the amount to save each month to have \$50,000 at the end of 18 years, using the terms specified
above.
PPMT
8/25/2021 • 2 minutes to read
Returns the payment on the principal for a given period for an investment based on periodic, constant payments
and a constant interest rate.
Syntax
PPMT(<rate>, <per>, <nper>, <pv>[, <fv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
Note: For a more complete description of the arguments in PPMT, see the PV function.
Return Value
The payment on the principal for a given period.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at an annual interest rate of 12 percent, use 0.12/12 for rate and
4*12 for nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
type is rounded to the nearest integer.
An error is returned if:
per < 1 or per > nper
nper < 1
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
DATA A RGUM EN T DESC RIP T IO N
EVALUATE
{
PPMT(0.1/12, 1, 2*12, 2000.00)
}
Returns the principal payment made in the first month for a loan with the terms specified above.
[ VA L UE]
-75.6231860083663
Example 2
DATA A RGUM EN T DESC RIP T IO N
EVALUATE
{
PPMT(0.08, 10, 10, 200000.00)
}
Returns the principal payment made in the 10th year for a loan with the terms specified above.
[ VA L UE]
-27598.0534624214
PRICE
8/25/2021 • 2 minutes to read
Returns the price per \$100 face value of a security that pays periodic interest.
Syntax
PRICE(<settlement>, <maturity>, <rate>, <yld>, <redemption>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement and maturity are truncated to integers.
basis and frequency are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
rate < 0.
yld < 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Impor tant:
When N > 1 (N is the number of coupons payable between the settlement date and redemption
date), PRICE is calculated as follows:
$$\text{PRICE} = \bigg[ \frac{\text{redemption}}{(1 + \frac{\text{yld}}{\text{frequency}})^{(N - 1 +
\frac{\text{DSC}}{\text{E}})})} \bigg] + \bigg[ \sum^{N}_{k=1} \frac{100 \times \frac{\text{rate}}
{\text{frequency}}}{(1 + \frac{\text{yld}}{\text{frequency}})^{(k - 1 + \frac{\text{DSC}}{\text{E}})}} \bigg] -
\bigg[ 100 \times \frac{\text{rate}}{\text{frequency}} \times \frac{\text{A}}{\text{E}} \bigg]$$
When N = 1 (N is the number of coupons payable between the settlement date and redemption
date), PRICE is calculated as follows:
$$\text{DSR} = \text{E} - \text{A}$$
$$\text{T1} = 100 \times \frac{\text{rate}}{\text{frequency}} + \text{redemption}$$
$$\text{T2} = \frac{\text{yld}}{\text{frequency}} \times \frac{\text{DSR}}{\text{E}} + 1$$
$$\text{T3} = 100 \times \frac{\text{rate}}{\text{frequency}} \times \frac{\text{A}}{\text{E}}$$
$$\text{PRICE} = \frac{\text{T1}}{\text{T2}} - \text{T3}$$
where:
$\text{DSC}$ = number of days from settlement to next coupon date.
$\text{E}$ = number of days in coupon period in which the settlement date falls.
$\text{A}$ = number of days from beginning of coupon period to settlement date.
Example
DATA A RGUM EN T DESC RIP T IO N
2 Frequency is semiannual
0 30/360 basis
EVALUATE
{
PRICE(DATE(2008,2,15), DATE(2017,11,15), 0.0575, 0.065, 100, 2, 0)
}
Returns the bond price, for a bond using the terms specified above.
[ VA L UE]
94.6343616213221
PRICEDISC
8/25/2021 • 2 minutes to read
Syntax
PRICEDISC(<settlement>, <maturity>, <discount>, <redemption>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2018, and is
purchased by a buyer six months later. The issue date would be January 1, 2018, the settlement date
would be July 1, 2018, and the maturity date would be January 1, 2048, 30 years after the January 1,
2018, issue date.
PRICEDISC is calculated as follows:
$$\text{PRICEDISC} = \text{redemption} - \text{discount} \times \text{redemption} \times
\frac{\text{DSM}}{\text{B}}$$
where:
$\text{B}$ = number of days in year, depending on year basis.
$\text{DSM}$ = number of days from settlement to maturity.
settlement and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
discount ≤ 0.
redemption ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA A RGUM EN T DESC RIP T IO N
2 Actual/360 basis
EVALUATE
{
PRICEDISC(DATE(2008,2,16), DATE(2008,3,1), 0.0525, 100, 2)
}
Returns the bond price per \$100 face value, for a bond with the terms specified above.
[ VA L UE]
99.7958333333333
PRICEMAT
8/25/2021 • 2 minutes to read
Returns the price per \$100 face value of a security that pays interest at maturity.
Syntax
PRICEMAT(<settlement>, <maturity>, <issue>, <rate>, <yld>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
PRICEMAT is calculated as follows:
$$\text{PRICEMAT} = \frac{100 + (\frac{\text{DIM}}{\text{B}} \times \text{rate} \times 100)}{1 +
(\frac{\text{DSM}}{\text{B}} \times \text{yld})} - (\frac{\text{A}}{\text{B}} \times \text{rate} \times 100)$$
where:
$\text{B}$ = number of days in year, depending on year basis.
$\text{DSM}$ = number of days from settlement to maturity.
$\text{DIM}$ = number of days from issue to maturity.
$\text{A}$ = number of days from issue to settlement.
settlement, maturity, and issue are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement, maturity, or issue is not a valid date.
maturity > settlement > issue is not satisfied.
rate < 0.
yld < 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
0 30/360 basis
EVALUATE
{
PRICEMAT(DATE(2008,2,15), DATE(2008,4,13), DATE(2007,11,11), 0.061, 0.061, 0)
}
Returns the price per \$100 face value of a security with the terms specified above.
[ VA L UE]
99.9844988755569
PV
8/25/2021 • 3 minutes to read
Calculates the present value of a loan or an investment, based on a constant interest rate. You can use PV with
either periodic, constant payments (such as a mortgage or other loan), and/or a future value that's your
investment goal.
Syntax
PV(<rate>, <nper>, <pmt>[, <fv>[, <type>]])
Parameters
T ERM DEF IN IT IO N
rate The interest rate per period. For example, if you obtain an
automobile loan at a 10 percent annual interest rate and
make monthly payments, your interest rate per month is
0.1/12, or 0.0083. You would enter 0.1/12, or 0.0083, into
the formula as the rate.
pmt The payment made each period that cannot change over the
life of the annuity. Typically, pmt includes principal and
interest but no other fees or taxes. For example, the monthly
payments on a \$10,000, four-year car loan at 12 percent
are \$263.33. You would enter -263.33 into the formula as
the pmt.
Remarks
Make sure that you are consistent about the units you use for specifying rate and nper. If you make
monthly payments on a four-year loan at 12 percent annual interest, use 0.12/12 for rate and 4*12 for
nper. If you make annual payments on the same loan, use 0.12 for rate and 4 for nper.
The following functions apply to annuities:
CUMIPMT
CUMPRINC
FV
IPMT
PMT
PPMT
PV
RATE
XIRR
XNPV
An annuity is a series of constant cash payments made over a continuous period. For example, a car loan
or a mortgage is an annuity. For more information, see the description for each annuity function.
In annuity functions, cash you pay out, such as a deposit to savings, is represented by a negative number;
cash you receive, such as a dividend check, is represented by a positive number. For example, a \$1,000
deposit to the bank would be represented by the argument -1000 if you are the depositor and by the
argument 1000 if you are the bank.
One financial argument is solved in terms of the others.
If rate is not 0, then:
$$\text{pv} \times (1 + \text{rate})^{\text{nper}} + \text{pmt}(1 + \text{rate} \times \text{type})
\times \bigg( \frac{(1 + \text{rate})^{\text{nper}} - 1}{\text{rate}} \bigg) + \text{fv} = 0$$
If rate is 0, then:
$$(\text{pmt} \times \text{nper}) + \text{pv} + \text{fv} = 0$$
type is rounded to the nearest integer.
An error is returned if:
nper < 1
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
PV(0.08/12, 12*20, 500.00, 0, 0)
}
Returns the present value of an annuity using the terms specified above.
[ VA L UE]
-59777.1458511878
RATE
8/25/2021 • 2 minutes to read
Returns the interest rate per period of an annuity. RATE is calculated by iteration and can have zero or more
solutions. If the successive results of RATE do not converge to within 0.0000001 after 20 iterations, an error is
returned.
Syntax
RATE(<nper>, <pmt>, <pv>[, <fv>[, <type>[, <guess>]]])
Parameters
T ERM DEF IN IT IO N
pmt The payment made each period and cannot change over the
life of the annuity. Typically, pmt includes principal and
interest but no other fees or taxes.
guess (Optional) Your guess for what the rate will be.
- If omitted, it is assumed to be 10%.
- If RATE does not converge, try different values for guess.
RATE usually converges if guess is between 0 and 1.
Return Value
The interest rate per period.
Remarks
Make sure that you are consistent about the units you use for specifying guess and nper. If you make
monthly payments on a four-year loan at 12 percent annual interest, use 0.12/12 for guess and 4*12 for
nper. If you make annual payments on the same loan, use 0.12 for guess and 4 for nper.
type is rounded to the nearest integer.
An error is returned if:
nper ≤ 0.
RATE does not converge to within 0.0000001 after 20 iterations
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
Example 1
The following DAX query:
EVALUATE
{
RATE(4*12, -200, 8000)
}
Returns the monthly rate of the loan using the terms specified above.
[ VA L UE]
0.00770147248820137
Example 2
The following DAX query:
EVALUATE
{
RATE(4*12, -200, 8000) * 12
}
Returns the annual rate of the loan using the terms specified above.
[ VA L UE]
0.0924176698584164
RECEIVED
8/25/2021 • 2 minutes to read
Syntax
RECEIVED(<settlement>, <maturity>, <investment>, <discount>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The amount received at maturity.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
RECEIVED is calculated as follows:
$$\text{RECEIVED} = \frac{\text{investment}}{1 - (\text{discount} \times \frac{\text{DIM}}{\text{B}})}$$
where:
$\text{B}$ = number of days in a year, depending on the year basis.
$\text{DIM}$ = number of days from issue to maturity.
settlement and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
investment ≤ 0.
discount ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
\$1,000,000.00 Investment
2 Actual/360 basis
EVALUATE
{
RECEIVED(DATE(2008,2,15), DATE(2008,5,15), 1000000.00, 0.0575, 2)
}
Returns the total amount to be received at maturity, for a bond with the terms specified above.
[ VA L UE]
1014584.6544071
RRI
8/25/2021 • 2 minutes to read
Syntax
RRI(<nper>, <pv>, <fv>)
Parameters
T ERM DEF IN IT IO N
Return Value
The equivalent interest rate.
Remarks
RRI returns the interest rate given $\text{nper}$ (the number of periods), $\text{pv}$ (present value), and
$\text{fv}$ (future value), calculated by using the following equation:
$$\bigg( \frac{\text{fv}}{\text{pv}} \bigg)^{(\frac{1}{\text{}nper})} - 1$$
An error is returned if:
nper ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
4 Years invested
Returns an equivalent interest rate for the growth of an investment with the terms specified above.
[ VA L UE]
0.0155771057566627
SLN
8/25/2021 • 2 minutes to read
Syntax
SLN(<cost>, <salvage>, <life>)
Parameters
T ERM DEF IN IT IO N
Return Value
The straight-line depreciation for one period.
Remarks
An error is returned if:
life = 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
\$30,000 Cost
EVALUATE
{
SLN(30000, 7500, 10)
}
Returns the yearly depreciation allowance using the terms specified above.
[ VA L UE]
2250
SYD
8/25/2021 • 2 minutes to read
Syntax
SYD(<cost>, <salvage>, <life>, <per>)
Parameters
T ERM DEF IN IT IO N
per The period. Must use the same units as life. Must be
between 1 and life (inclusive).
Return Value
The sum-of-years' digits depreciation for the specified period.
Remarks
SYD is calculated as follows:
$$\text{SYD} = \frac{(\text{cost} - \text{salvage}) \times (\text{life} - \text{per} + 1) \times 2}{(\text{life})
\times (\text{life} + 1)}$$
An error is returned if:
life < 1.
per < 1 or per > life.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
10 Lifespan in years
Example 1
The following DAX query:
EVALUATE
{
SYD(30000.00, 7500.00, 10, 1)
}
Returns an asset's sum-of-years' digits depreciation allowance for the first year, given the terms specified above.
[ VA L UE]
4090.90909090909
Example 2
The following DAX query:
EVALUATE
{
SYD(30000.00, 7500.00, 10, 10)
}
Returns an asset's sum-of-years' digits depreciation allowance for the tenth (final) year, given the terms specified
above.
[ VA L UE]
409.090909090909
TBILLEQ
8/25/2021 • 2 minutes to read
Syntax
TBILLEQ(<settlement>, <maturity>, <discount>)
Parameters
T ERM DEF IN IT IO N
maturity The Treasury bill's maturity date. The maturity date is the
date when the Treasury bill expires.
Return Value
The Treasury Bill's bond-equivalent yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
TBILLEQ is calculated as:
$$\text{TBILLEQ} = \frac{365 \times \text{discount}}{360 - (\text{discount} \times \text{DSM})}$$
where:
$\text{DSM}$ is the number of days between settlement and maturity computed according to the 360
days per year basis.
settlement and maturity are truncated to integers.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity or maturity is more than one year after settlement.
discount ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
TBILLEQ(DATE(2008,3,31), DATE(2008,6,1), 0.0914)
}
Returns the bond-equivalent yield for a Treasury bill using the terms specified above.
[ VA L UE]
0.094151493565943
TBILLPRICE
8/25/2021 • 2 minutes to read
Returns the price per \$100 face value for a Treasury bill.
Syntax
TBILLPRICE(<settlement>, <maturity>, <discount>)
Parameters
T ERM DEF IN IT IO N
maturity The Treasury bill's maturity date. The maturity date is the
date when the Treasury bill expires.
Return Value
The Treasury Bill's price per \$100 face value.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
TBILLPRICE is calculated as follows:
$$\text{TBILLPRICE} = 100 \times (1 - \frac{\text{discount} \times \text{DSM}}{360})$$
where:
$\text{DSM}$ = number of days from settlement to maturity, excluding any maturity date that is more
than one calendar year after the settlement date.
settlement and maturity are truncated to integers.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity or maturity is more than one year after settlement.
discount ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
EVALUATE
{
TBILLPRICE(DATE(2008,3,31), DATE(2008,6,1), 0.09)
}
Returns the Treasury Bill's price per \$100 face value, given the terms specified above.
[ VA L UE]
98.45
TBILLYIELD
8/25/2021 • 2 minutes to read
Syntax
TBILLYIELD(<settlement>, <maturity>, <pr>)
Parameters
T ERM DEF IN IT IO N
maturity The Treasury bill's maturity date. The maturity date is the
date when the Treasury bill expires.
Return Value
The Treasury bill's yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
TBILLYIELD is calculated as follows:
$$\text{TBILLYIELD} = \frac{100 - \text{pr}}{\text{pr}} \times \frac{360}{\text{DSM}}$$
where:
$\text{DSM}$ = number of days from settlement to maturity, excluding any maturity date that is more
than one calendar year after the settlement date.
settlement and maturity are truncated to integers.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity or maturity is more than one year after settlement.
pr ≤ 0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query:
EVALUATE
{
TBILLYIELD(DATE(2008,3,31), DATE(2008,6,1), 98.45)
}
Returns the yield of a Treasury bill using the terms specified above.
[ VA L UE]
0.0914169629253426
VDB
8/25/2021 • 2 minutes to read
Returns the depreciation of an asset for any period you specify, including partial periods, using the double-
declining balance method or some other method you specify. VDB stands for variable declining balance.
Syntax
VDB(<cost>, <salvage>, <life>, <start_period>, <end_period>[, <factor>[, <no_switch>]])
Parameters
T ERM DEF IN IT IO N
start_period The starting period for which you want to calculate the
depreciation. Start_period must use the same units as life.
Must be between 1 and life (inclusive).
end_period The ending period for which you want to calculate the
depreciation. End_period must use the same units as life.
Must be between start_period and life (inclusive).
Return Value
The depreciation over the specified period.
Remarks
An error is returned if:
cost < 0.
salvage < 0.
life < 1.
start_period < 1 or start_period > end_period.
end_period < start_period or end_period > life.
factor < 0.
no_switch does not evaluate to either TRUE or FALSE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
DATA DESC RIP T IO N
10 Lifetime in years
Example 1
The following DAX query:
EVALUATE
{
VDB(2400, 300, 10*365, 0, 1)
}
[ VA L UE]
1.31506849315068
Example 2
The following DAX query:
EVALUATE
{
VDB(2400, 300, 10*12, 6, 18, 3)
}
Returns an asset's depreciation between the 6$^{th}$ month and the 18$^{th}$ month. This calculation uses a
factor of 3.
[ VA L UE]
540.185558199698
Example 3
The following DAX query:
EVALUATE
{
VDB(2400, 300, 10, 0, 0.875, 1.5)
}
Returns an asset's depreciation in the first fiscal year that you own it, assuming that tax laws limit you to 150%
depreciation of the declining balance. The asset is purchased in the middle of the first quarter of the fiscal year.
[ VA L UE]
315
XIRR
9/15/2021 • 2 minutes to read
Returns the internal rate of return for a schedule of cash flows that is not necessarily periodic.
Syntax
XIRR(<table>, <values>, <dates>, [, <guess>[, <alternateResult>]])
Parameters
T ERM DEF IN IT IO N
table A table for which the values and dates expressions should be
calculated.
values An expression that returns the cash flow value for each row
of the table.
dates An expression that returns the cash flow date for each row
of the table.
Return value
Internal rate of return for the given inputs. If the calculation fails to return a valid result, an error or value
specified as alternateResult is returned.
Remarks
The value is calculated as the rate that satisfies the following function:
$$\sum^{N}_{ j=1} \frac{P_{ j}}{(1 + \text{rate})^{\frac{d_{ j} - d_{1}}{365}}}$$
Where:
$P_{ j}$ is the $j^{th}$ payment
$d_{ j}$ is the $j^{th}$ payment date
$d_{1}$ is the first payment date
The series of cash flow values must contain at least one positive number and one negative number.
Avoid using ISERROR or IFERROR functions to capture an error returned by XIRR. If some inputs to the
function may result in a no solution error, providing an alternateResult parameter is the most reliable and
highest performing way to handle the error.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following formula calculates the internal rate of return of the CashFlows table:
DAT E PAY M EN T
1/1/2014 -10000
3/1/2014 2750
10/30/2014 4250
2/15/2015 3250
4/1/2015 2750
Returns the present value for a schedule of cash flows that is not necessarily periodic.
Syntax
XNPV(<table>, <values>, <dates>, <rate>)
Parameters
T ERM DEF IN IT IO N
table A table for which the values and dates expressions should be
calculated.
values An expression that returns the cash flow value for each row
of the table.
dates An expression that returns the cash flow date for each row
of the table.
rate The discount rate to apply to the cash flow for each row of
the table.
Return value
Net present value.
Remarks
The value is calculated as the following summation:
$$\sum^{N}_{ j=1} \frac{P_{ j}}{(1 + \text{rate})^{\frac{d_{ j} - d_{1}}{365}}}$$
Where:
$P_{ j}$ is the $j^{th}$ payment
$d_{ j}$ is the $j^{th}$ payment date
$d_{1}$ is the first payment date
The series of cash flow values must contain at least one positive number and one negative number.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following calculates the present value of the CashFlows table:
= XNPV( CashFlows, [Payment], [Date], 0.09 )
DAT E PAY M EN T
1/1/2014 -10000
3/1/2014 2750
10/30/2014 4250
2/15/2015 3250
4/1/2015 2750
Returns the yield on a security that pays periodic interest. Use YIELD to calculate bond yield.
Syntax
YIELD(<settlement>, <maturity>, <rate>, <pr>, <redemption>, <frequency>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The yield on the security.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
If there is one coupon period or less until redemption, YIELD is calculated as follows:
$$\text{YIELD} = \frac{(\frac{\text{redemption}}{100} + \frac{\text{rate}}{\text{frequency}}) -
(\frac{\text{par}}{100} + (\frac{\text{A}}{\text{E}} \times \frac{\text{rate}}{\text{frequency}}))}
{\frac{\text{par}}{100} + (\frac{\text{A}}{\text{E}} \times \frac{\text{rate}}{\text{frequency}})} \times
\frac{\text{frequency} \times \text{E}}{\text{DSR}}$$
where:
$\text{A}$ = number of days from the beginning of the coupon period to the settlement date (accrued
days).
$\text{DSR}$ = number of days from the settlement date to the redemption date.
$\text{E}$ = number of days in the coupon period.
If there is more than one coupon period until redemption, YIELD is calculated through a hundred
iterations. The resolution uses the Newton method, based on the formula used for the function PRICE.
The yield is changed until the estimated price given the yield is close to price.
settlement and maturity are truncated to integers.
frequency, and basis are rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
rate < 0.
pr ≤ 0.
redemption ≤ 0.
frequency is any number other than 1, 2, or 4.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
95.04287 Price
EVALUATE
{
YIELD(DATE(2008,2,15), DATE(2016,11,15), 0.0575, 95.04287, 100, 2,0)
}
[ VA L UE]
0.0650000068807314
YIELDDISC
8/25/2021 • 2 minutes to read
Syntax
YIELDDISC(<settlement>, <maturity>, <pr>, <redemption>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The annual yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement and maturity are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement or maturity is not a valid date.
settlement ≥ maturity.
pr ≤ 0.
redemption ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA -
99.795 Price
2 Actual/360 basis
EVALUATE
{
YIELDDISC(DATE(2008,2,16), DATE(2008,3,1), 99.795, 100, 2)
}
Returns the security's annual yield, given the terms specified above.
[ VA L UE]
0.0528225719868583
YIELDMAT
8/25/2021 • 2 minutes to read
Syntax
YIELDMAT(<settlement>, <maturity>, <issue>, <rate>, <pr>[, <basis>])
Parameters
T ERM DEF IN IT IO N
maturity The security's maturity date. The maturity date is the date
when the security expires.
1 Actual/actual
2 Actual/360
3 Actual/365
4 European 30/360
Return Value
The annual yield.
Remarks
Dates are stored as sequential serial numbers so they can be used in calculations. In DAX, December 30,
1899 is day 0, and January 1, 2008 is 39448 because it is 39,448 days after December 30, 1899.
The settlement date is the date a buyer purchases a coupon, such as a bond. The maturity date is the date
when a coupon expires. For example, suppose a 30-year bond is issued on January 1, 2008, and is
purchased by a buyer six months later. The issue date would be January 1, 2008, the settlement date
would be July 1, 2008, and the maturity date would be January 1, 2038, which is 30 years after the
January 1, 2008, issue date.
settlement, maturity, and issue are truncated to integers.
basis is rounded to the nearest integer.
An error is returned if:
settlement, maturity, or issue is not a valid date.
maturity > settlement > issue is not satisfied.
rate < 0.
pr ≤ 0.
basis < 0 or basis > 4.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DATA DESC RIP T IO N
100.0123 Price
EVALUATE
{
YIELDMAT(DATE(2008,3,15), DATE(2008,11,3), DATE(2007,11,8), 0.0625, 100.0123, 0)
}
Returns the yield for a security using the terms specified above.
[ VA L UE]
0.0609543336915387
Information functions
9/3/2021 • 2 minutes to read
DAX information functions look at the cell or row that is provided as an argument and tells you whether the
value matches the expected type. For example, the ISERROR function returns TRUE if the value that you
reference contains an error.
In this category
F UN C T IO N DESC RIP T IO N
CONTAINS Returns true if values for all referred columns exist, or are
contained, in those columns; otherwise, the function returns
false.
HASONEVALUE Returns TRUE when the context for columnName has been
filtered down to one distinct value only. Otherwise is FALSE.
ISNONTEXT Checks if a value is not text (blank cells are not text), and
returns TRUE or FALSE.
Returns true if values for all referred columns exist, or are contained, in those columns; otherwise, the function
returns false.
Syntax
CONTAINS(<table>, <columnName>, <value>[, <columnName>, <value>]…)
Parameters
T ERM DEF IN IT IO N
value Any DAX expression that returns a single scalar value, that is
to be sought in columnName. The expression is to be
evaluated exactly once and before it is passed to the
argument list.
Return value
A value of TRUE if each specified value can be found in the corresponding columnName, or are contained, in
those columns; otherwise, the function returns FALSE .
Remarks
The arguments columnName and value must come in pairs; otherwise an error is returned.
columnName must belong to the specified table, or to a table that is related to table.
If columnName refers to a column in a related table then it must be fully qualified; otherwise, an error is
returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example creates a measure that tells you whether there were any Internet sales of product 214
and to customer 11185 at the same time.
Returns TRUE if a row of values exists or contained in a table, otherwise returns FALSE.
Syntax
CONTAINSROW(<tableExpr>, <scalarExpr>[, <scalarExpr>, …])
Parameters
T ERM DEF IN IT IO N
Return value
TRUE or FALSE.
Remarks
Except syntax, the IN operator and CONTAINSROW function are functionally equivalent.
<scalarExpr> IN <tableExpr>
( <scalarExpr1>, <scalarExpr2>, … ) IN <tableExpr>
Example 1
The following equivalent DAX queries:
and
and
EVALUATE FILTER(ALL(DimProduct[Color]), CONTAINSROW({ "Red", "Yellow", "Blue" }, [Color]))
ORDER BY [Color]
DIM P RO DUC T [ C O LO R]
Blue
Red
Yellow
Example 2
The following equivalent DAX queries:
and
Return:
Black L
Example 3
The following equivalent DAX queries:
and
DIM P RO DUC T [ C O LO R]
Black
Grey
Multi
DIM P RO DUC T [ C O LO R]
NA
Silver
Silver\Black
White
CONTAINSSTRING
8/25/2021 • 2 minutes to read
Returns TRUE or FALSE indicating whether one string contains another string.
Syntax
CONTAINSSTRING(<within_text>, <find_text>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if find_text is a substring of within_text; otherwise FALSE.
Remarks
CONTAINSSTRING is not case-sensitive.
You can use ? and * wildcard characters. Use ~ to escape wildcard characters.
Example
DAX query
EVALUATE
ROW(
"Case 1", CONTAINSSTRING("abcd", "bc"),
"Case 2", CONTAINSSTRING("abcd", "BC"),
"Case 3", CONTAINSSTRING("abcd", "a*d"),
"Case 4", CONTAINSSTRING("abcd", "ef")
)
Returns
[ C A SE 1] [ C A SE 2] [ C A SE 3] [ C A SE 4]
Returns TRUE or FALSE indicating whether one string contains another string.
Syntax
CONTAINSSTRINGEXACT(<within_text>, <find_text>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if find_text is a substring of within_text; otherwise FALSE.
Remarks
CONTAINSSTRINGEXACT is case-sensitive.
Example
DAX query
EVALUATE
ROW(
"Case 1", CONTAINSSTRINGEXACT("abcd", "bc"),
"Case 2", CONTAINSSTRINGEXACT("abcd", "BC"),
"Case 3", CONTAINSSTRINGEXACT("abcd", "a*d"),
"Case 4", CONTAINSSTRINGEXACT("abcd", "ef")
)
Returns
[ C A SE 1] [ C A SE 2] [ C A SE 3] [ C A SE 4]
Syntax
CUSTOMDATA()
Return value
The content of the CustomData property in the connection string.
Blank, if CustomData property was not defined at connection time.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following DAX formula verifies if the CustomData property was set to "OK" .
= IF(CUSTOMDATA()="OK", "Correct Custom data in connection string", "No custom data in connection string
property or unexpected value")
HASONEFILTER
8/25/2021 • 2 minutes to read
Returns TRUE when the number of directly filtered values on columnName is one; otherwise returns FALSE .
Syntax
HASONEFILTER(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE when the number of directly filtered values on columnName is one; otherwise returns FALSE .
Remarks
This function is similar to HASONEVALUE() with the difference that HASONEVALUE() works based on
cross-filters while HASONEFILTER() works by a direct filter.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows how to use HASONEFILTER() to return the filter for
ResellerSales_USD[ProductKey]) if there is one filter, or to return BLANK if there are no filters or more than one
filter on ResellerSales_USD[ProductKey]).
= IF(HASONEFILTER(ResellerSales_USD[ProductKey]),FILTERS(ResellerSales_USD[ProductKey]),BLANK())
HASONEVALUE
8/25/2021 • 2 minutes to read
Returns TRUE when the context for columnName has been filtered down to one distinct value only. Otherwise is
FALSE .
Syntax
HASONEVALUE(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE when the context for columnName has been filtered down to one distinct value only. Otherwise is FALSE .
Remarks
An equivalent expression for HASONEVALUE() is COUNTROWS(VALUES(<columnName>)) = 1 .
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following measure formula verifies if the context is being sliced by one value in order to estimate a
percentage against a predefined scenario; in this case you want to compare Reseller Sales against sales in 2007,
then you need to know if the context is filtered by single years. Also, if the comparison is meaningless you want
to return BLANK.
=
IF(HASONEVALUE(DateTime[CalendarYear]),SUM(ResellerSales_USD[SalesAmount_USD])/CALCULATE(SUM(ResellerSales_U
SD[SalesAmount_USD]),DateTime[CalendarYear]=2007),BLANK())
ISAFTER
9/3/2021 • 2 minutes to read
A boolean function that emulates the behavior of a 'Start At' clause and returns true for a row that meets all of
the condition parameters.
Based on the sort order, the first parameter is compared with the second parameter. If the sort order is
ascending, the comparison to be done is first parameter greater than the second parameter. If the sort order is
descending, the comparison to be done is second parameter less than the first parameter.
Syntax
ISAFTER(<scalar_expression>, <scalar_expression>[, sort_order [, <scalar_expression>, <scalar_expression>[,
sort_order]]…)
Parameters
T ERM DEF IN IT IO N
scalar expression Any expression that returns a scalar value like a column
reference or integer or string value. Typically the first
parameter is a column reference and the second parameter
is a scalar value.
sort order (optional) The order in which the column is sorted. Can be
ascending (ASC) or descending (DEC). By default the sort
order is ascending.
Return value
True or false.
Remarks
This function is similar to ISONORAFTER. The difference is ISAFTER returns true for values sorted strictly after
the filter values, where ISONORAFTER returns true for values sorted on or after the filter values.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
Table name: 'Info'
C O UN T RY STAT E C O UN T TOTA L
IND JK 20 800
IND MH 25 1000
C O UN T RY STAT E C O UN T TOTA L
IND WB 10 900
USA CA 5 500
USA WA 10 900
FILTER (
Info,
ISAFTER (
Info[Country], "IND", ASC,
Info[State], "MH", ASC )
)
Returns:
C O UN T RY STAT E C O UN T TOTA L
IND WB 10 900
USA CA 5 500
USA WA 10 900
See also
ISONORAFTER
ISBLANK
8/25/2021 • 2 minutes to read
Syntax
ISBLANK(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
A Boolean value of TRUE if the value is blank; otherwise FALSE.
Remarks
To learn more about best practices when working with BLANKS, see Avoid converting BLANKs to values in DAX.
Example
This formula computes the increase or decrease ratio in sales compared to the previous year. The example uses
the IF function to check the value for the previous year's sales in order to avoid a divide by zero error.
= IF( ISBLANK('CalculatedMeasures'[PreviousYearTotalSales])
, BLANK()
, ( 'CalculatedMeasures'[Total Sales]-'CalculatedMeasures'[PreviousYearTotalSales] )
/'CalculatedMeasures'[PreviousYearTotalSales])
Result,
2005 $10,209,985.08
Returns TRUE when columnName or another column in the same or related table is being filtered.
Syntax
ISCROSSFILTERED(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE when columnName or another column in the same or related table is being filtered. Otherwise returns
FALSE .
Remarks
A column is said to be cross-filtered when a filter applied to another column in the same table or in a
related table affects columnName by filtering it. A column is said to be filtered directly when the filter or
filters apply over the column.
The related function ISFILTERED function returns TRUE when columnName is filtered directly.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
ISFILTERED function
FILTERS function
HASONEFILTER function
HASONEVALUE function
ISEMPTY
8/25/2021 • 2 minutes to read
Syntax
ISEMPTY(<table_expression>)
Parameters
T ERM DEF IN IT IO N
Return value
True if the table is empty (has no rows), if else, False.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
For the below table named 'Info':
C O UN T RY STAT E C O UN T Y TOTA L
IND JK 20 800
IND MH 25 1000
IND WB 10 900
USA CA 5 500
USA WA 10 900
EVALUATE
ROW("Any countries with count > 25?", NOT(ISEMPTY(FILTER(Info, [County]>25))))
Syntax
ISERROR(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
A Boolean value of TRUE if the value is an error; otherwise FALSE.
Remarks
For best practices when using ISERROR, see Appropriate use of error functions.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example calculates the ratio of total Internet sales to total reseller sales. The ISERROR function is
used to check for errors, such as division by zero. If there is an error a blank is returned, otherwise the ratio is
returned.
= IF( ISERROR(
SUM('ResellerSales_USD'[SalesAmount_USD])
/SUM('InternetSales_USD'[SalesAmount_USD])
)
, BLANK()
, SUM('ResellerSales_USD'[SalesAmount_USD])
/SUM('InternetSales_USD'[SalesAmount_USD])
)
See also
Information functions
IFERROR function
IF function
ISEVEN
8/25/2021 • 2 minutes to read
Syntax
ISEVEN(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns TRUE if number is even, or FALSE if number is odd.
Remarks
If number is nonnumeric, ISEVEN returns the #VALUE! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
ISFILTERED
8/25/2021 • 2 minutes to read
Returns TRUE when columnName is being filtered directly. If there is no filter on the column or if the filtering
happens because a different column in the same table or in a related table is being filtered then the function
returns FALSE .
Syntax
ISFILTERED(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE when columnName is being filtered directly.
Remarks
columnName is said to be filtered directly when the filter or filters apply over the column; a column is
said to be cross-filtered when a filter applied to another column in the same table or in a related table
affects columnName the column by filtering it as well.
The related function ISCROSSFILTERED returns TRUE when columnName or another column in the same
or related table is being filtered.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
ISCROSSFILTERED function
FILTERS function
HASONEFILTER function
HASONEVALUE function
ISINSCOPE
8/25/2021 • 2 minutes to read
Returns true when the specified column is the level in a hierarchy of levels.
Syntax
ISINSCOPE(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE when the specified column is the level in a hierarchy of levels.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
DEFINE
MEASURE FactInternetSales[% of Parent] =
SWITCH (TRUE(),
ISINSCOPE(DimProduct[Subcategory]),
DIVIDE(
SUM(FactInternetSales[Sales Amount]),
CALCULATE(
SUM(FactInternetSales[Sales Amount]),
ALLSELECTED(DimProduct[Subcategory]))
),
ISINSCOPE(DimProduct[Category]),
DIVIDE(
SUM(FactInternetSales[Sales Amount]),
CALCULATE(
SUM(FactInternetSales[Sales Amount]),
ALLSELECTED(DimProduct[Category]))
),
1
) * 100
EVALUATE
SUMMARIZECOLUMNS
(
ROLLUPADDISSUBTOTAL
(
DimProduct[Category], "Category Subtotal",
DimProduct[Subcategory], "Subcategory Subtotal"
),
TREATAS(
{"Bike Racks", "Bike Stands", "Mountain Bikes", "Road Bikes", "Touring Bikes"},
DimProduct[Subcategory]),
"Sales", SUM(FactInternetSales[Sales Amount]),
"% of Parent", [% of Parent]
)
ORDER BY
[Category Subtotal] DESC, [Category],
[Subcategory Subtotal] DESC, [Subcategory]
Returns,
See also
SUMMARIZECOLUMNS function
CALCULATE function
ISLOGICAL
8/25/2021 • 2 minutes to read
Checks whether a value is a logical value, (TRUE or FALSE), and returns TRUE or FALSE.
Syntax
ISLOGICAL(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if the value is a logical value; FALSE if any value other than TRUE OR FALSE.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following three samples show the behavior of ISLOGICAL.
See also
Information functions
ISNONTEXT
8/25/2021 • 2 minutes to read
Checks if a value is not text (blank cells are not text), and returns TRUE or FALSE.
Syntax
ISNONTEXT(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if the value is not text or blank; FALSE if the value is text.
Remarks
An empty string is considered text.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following examples show the behavior of the ISNONTEXT function.
//RETURNS: Is Non-Text
= IF(ISNONTEXT(1), "Is Non-Text", "Is Text")
//RETURNS: Is Non-Text
= IF(ISNONTEXT(BLANK()), "Is Non-Text", "Is Text")
//RETURNS: Is Text
= IF(ISNONTEXT(""), "Is Non-Text", "Is Text")
See also
Information functions
ISNUMBER
8/25/2021 • 2 minutes to read
Syntax
ISNUMBER(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if the value is numeric; otherwise FALSE.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following three samples show the behavior of ISNUMBER.
//RETURNS: Is number
= IF(ISNUMBER(0), "Is number", "Is Not number")
//RETURNS: Is number
= IF(ISNUMBER(3.1E-1),"Is number", "Is Not number")
See also
Information functions
ISODD
8/25/2021 • 2 minutes to read
Syntax
ISODD(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns TRUE if number is odd, or FALSE if number is even.
Remarks
If number is nonnumeric, ISODD returns the #VALUE! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
ISONORAFTER
9/3/2021 • 2 minutes to read
A boolean function that emulates the behavior of a Start At clause and returns true for a row that meets all of
the condition parameters.
Based on the sort order, the first parameter is compared with the second parameter. If the sort order is
ascending, the comparison to be done is first parameter greater than the second parameter. If the sort order is
descending, the comparison to be done is second parameter less than the first parameter.
Syntax
ISONORAFTER(<scalar_expression>, <scalar_expression>[, sort_order [, <scalar_expression>,
<scalar_expression>[, sort_order]]…)
Parameters
T ERM DEF IN IT IO N
scalar expression Any expression that returns a scalar value like a column
reference or integer or string value. Typically the first
parameter is a column reference and the second parameter
is a scalar value.
sort order (optional) The order in which the column is sorted. Can be
ascending (ASC) or descending (DEC). By default the sort
order is ascending.
Return value
True or false.
Remarks
This function is similar to ISAFTER. The difference is ISONORAFTER returns true for values sorted on or after the
filter values, where ISAFTER returns true for values sorted strictly after the filter values.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
Table name: 'Info'
C O UN T RY STAT E C O UN T TOTA L
IND JK 20 800
IND MH 25 1000
C O UN T RY STAT E C O UN T TOTA L
IND WB 10 900
USA CA 5 500
USA WA 10 900
FILTER (
Info,
ISONORAFTER (
Info[Country], "IND", ASC,
Info[State], "MH", ASC )
)
Returns:
C O UN T RY STAT E C O UN T TOTA L
IND MH 25 1000
IND WB 10 900
USA CA 5 500
USA WA 10 900
See also
ISAFTER
ISSELECTEDMEASURE
8/25/2021 • 2 minutes to read
Used by expressions for calculation items to determine the measure that is in context is one of those specified in
a list of measures.
Syntax
ISSELECTEDMEASURE( M1, M2, ... )
Parameters
T ERM DEF IN IT IO N
Return value
A Boolean indicating whether the measure that is currently in context is one of those specified in the list of
parameters.
Remarks
Can only be referenced in the expression for a calculation item.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following calculation item expression checks if the current measure is one of those specified in the list of
parameters. If the measures are renamed, formula fixup will reflect the name changes in the expression.
IF (
ISSELECTEDMEASURE ( [Expense Ratio 1], [Expense Ratio 2] ),
SELECTEDMEASURE (),
DIVIDE ( SELECTEDMEASURE (), COUNTROWS ( DimDate ) )
)
See also
SELECTEDMEASURE
SELECTEDMEASURENAME
ISSUBTOTAL
8/25/2021 • 2 minutes to read
Creates another column in a SUMMARIZE expression that returns True if the row contains subtotal values for the
column given as argument, otherwise returns False.
Syntax
ISSUBTOTAL(<columnName>)
With SUMMARIZE,
Parameters
T ERM DEF IN IT IO N
Return value
A True value if the row contains a subtotal value for the column given as argument, otherwise returns False.
Remarks
This function can only be used in the expression of a SUMMARIZE function.
This function must be preceded by the name of the Boolean column.
Example
See SUMMARIZE.
ISTEXT
8/25/2021 • 2 minutes to read
Syntax
ISTEXT(<value>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE if the value is text; otherwise FALSE.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following examples show the behavior of the ISTEXT function.
//RETURNS: Is Text
= IF(ISTEXT("text"), "Is Text", "Is Non-Text")
//RETURNS: Is Text
= IF(ISTEXT(""), "Is Text", "Is Non-Text")
//RETURNS: Is Non-Text
= IF(ISTEXT(1), "Is Text", "Is Non-Text")
//RETURNS: Is Non-Text
= IF(ISTEXT(BLANK()), "Is Text", "Is Non-Text")
See also
Information functions
NONVISUAL
8/25/2021 • 2 minutes to read
Marks a value filter in a SUMMARIZECOLUMNS expression as non-visual. This function can only be used within
a SUMMARIZECOLUMNS expression.
Syntax
NONVISUAL(<expression>)
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single value (not a table).
Return value
A table of values.
Remarks
Marks a value filter in SUMMARIZECOLUMNS as not affecting measure values, but only applying to
group-by columns.
This function can only be used within a SUMMARIZECOLUMNS expression. It's used as either a filterTable
argument of the SUMMARIZECOLUMNS function or a groupLevelFilter argument of the
ROLLUPADDISSUBTOTAL or ROLLUPISSUBTOTAL function.
Example
See SUMMARIZECOLUMNS.
SELECTEDMEASURE
8/25/2021 • 2 minutes to read
Used by expressions for calculation items to reference the measure that is in context.
Syntax
SELECTEDMEASURE()
Parameters
None
Return value
A reference to the measure that is currently in context when the calculation item is evaluated.
Remarks
Can only be referenced in the expression for a calculation item.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following calculation item expression calculates the year-to-date for whatever the measure is in context.
CALCULATE(SELECTEDMEASURE(), DATESYTD(DimDate[Date]))
See also
SELECTEDMEASURENAME
ISSELECTEDMEASURE
SELECTEDMEASUREFORMATSTRING
8/25/2021 • 2 minutes to read
Used by expressions for calculation items to retrieve the format string of the measure that is in context.
Syntax
SELECTEDMEASUREFORMATSTRING()
Parameters
None
Return value
A string holding the format string of the measure that is currently in context when the calculation item is
evaluated.
Remarks
This function can only be referenced in expressions for calculation items in calculation groups. It is
designed to be used by the Format String Expression property of calculation items.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following expression is evaluated by the Format String Expression property for a calculation item. If there is
a single currency in filter context, the format string is retrieved from the DimCurrency[FormatString] column;
otherwise the format string of the measure in context is used.
See also
SELECTEDMEASURE
ISSELECTEDMEASURE
SELECTEDMEASURENAME
8/25/2021 • 2 minutes to read
Used by expressions for calculation items to determine the measure that is in context by name.
Syntax
SELECTEDMEASURENAME()
Parameters
None
Return value
A string value holding the name of the measure that is currently in context when the calculation item is
evaluated.
Remarks
Can only be referenced in the expression for a calculation item.
This function is often used for debugging purposes when authoring calculation groups.
Example
The following calculation item expression checks if the current measure is Expense Ratio and conditionally
applies calculation logic. Since the check is based on a string comparison, it is not subject to formula fixup and
will not benefit from object renaming being automatically reflected. For a similar comparison that would benefit
from formula fixup, please see the ISSLECTEDMEASURE function instead.
IF (
SELECTEDMEASURENAME = "Expense Ratio",
SELECTEDMEASURE (),
DIVIDE ( SELECTEDMEASURE (), COUNTROWS ( DimDate ) )
)
See also
SELECTEDMEASURE
ISSELECTEDMEASURE
USERNAME
8/25/2021 • 2 minutes to read
Returns the domain name and username from the credentials given to the system at connection time.
Syntax
USERNAME()
Parameters
This expression has no parameters.
Return value
The username from the credentials given to the system at connection time
Example
The following formula verifies if the user login is part of the UsersTable.
Returns the current user's Object ID from Azure AD or security identifier (SID).
Syntax
USEROBJECTID()
Parameters
This expression has no parameters.
Return value
The current user's Object ID from Azure AD for Power BI or Azure Analysis Services models or SID for SQL
Server Analysis Services models.
USERPRINCIPALNAME
8/25/2021 • 2 minutes to read
Syntax
USERPRINCIPALNAME()
Parameters
This expression has no parameters.
Return value
The userprincipalname at connection time.
Logical functions
8/25/2021 • 2 minutes to read
Logical functions act upon an expression to return information about the values or sets in the expression. For
example, you can use the IF function to check the result of an expression and create conditional results.
In this category
F UN C T IO N DESC RIP T IO N
Checks whether both arguments are TRUE, and returns TRUE if both arguments are TRUE. Otherwise returns
false.
Syntax
AND(<logical1>,<logical2>)
Parameters
T ERM DEF IN IT IO N
Return value
Returns true or false depending on the combination of values that you test.
Remarks
The AND function in DAX accepts only two (2) arguments. If you need to perform an AND operation on multiple
expressions, you can create a series of calculations or, better, use the AND operator (&& ) to join all of them in a
simpler expression.
Example 1
The following formula shows the syntax of the AND function.
= IF(AND(10 > 9, -10 < -1), "All true", "One or more false"
Because both conditions, passed as arguments, to the AND function are true, the formula returns "All True".
Example 2
The following sample uses the AND function with nested formulas to compare two sets of calculations at the
same time. For each product category, the formula determines if the current year sales and previous year sales
of the Internet channel are larger than the Reseller channel for the same periods. If both conditions are true, for
each category the formula returns the value, "Internet hit".
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
Bib-Shorts
Bike Racks
Bottom
Brackets
Brakes
Caps
Chains
Cleaners
Cranksets
Derailleurs
Forks
Gloves
Handlebars
Headsets
Helmets
Hydration
Packs
Jerseys
Lights
Locks
Mountain
Bikes
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
Mountain
Frames
Panniers
Pedals
Pumps
Road Bikes
Road Frames
Saddles
Shorts
Socks
Tights
Touring Bikes
Touring
Frames
Vests
Wheels
Grand Total
See also
Logical functions
COALESCE
8/25/2021 • 2 minutes to read
Returns the first expression that does not evaluate to BLANK. If all expressions evaluate to BLANK, BLANK is
returned.
Syntax
COALESCE(<expression>, <expression>[, <expression>]…)
Parameters
T ERM DEF IN IT IO N
Return value
A scalar value coming from one of the expressions or BLANK if all expressions evaluate to BLANK.
Remarks
Input expressions may be of different data types.
Example 1
The following DAX query:
Returns 10 , which is the first expression that does not evaluate to BLANK.
Example 2
The following DAX expression:
= COALESCE(SUM(FactInternetSales[SalesAmount]), 0)
Returns the sum of all values in the SalesAmount column in the FactInternetSales table, or 0 . This can be used
to convert BLANK values of total sales to 0 .
FALSE
8/25/2021 • 2 minutes to read
Syntax
FALSE()
Return value
Always FALSE.
Remarks
The word FALSE is also interpreted as the logical value FALSE.
Example
The formula returns the logical value FALSE when the value in the column,
'InternetSales_USD'[SalesAmount_USD], is less than or equal to 200000.
The following table shows the results when the example formula is used with
'ProductCategory'[ProductCategoryName] in Row Labels and 'DateTime'[CalendarYear] in Column Labels.
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
See also
TRUE function
NOT function
IF function
IF
8/25/2021 • 2 minutes to read
Checks a condition, and returns one value when it's TRUE, otherwise it returns a second value.
Syntax
IF(<logical_test>, <value_if_true>[, <value_if_false>])
Parameters
T ERM DEF IN IT IO N
Return value
Either value_if_true , value_if_false , or BLANK.
Remarks
The IF function can return a variant data type if value_if_true and value_if_false are of different data
types, but the function attempts to return a single data type if both value_if_true and value_if_false
are of numeric data types. In the latter case, the IF function will implicitly convert data types to
accommodate both values.
For example, the formula IF(<condition>, TRUE(), 0)returns TRUE or 0, but the formula
IF(<condition>, 1.0, 0) returns only decimal values even though value_if_false is of the whole
number data type. To learn more about implicit data type conversion, see Data types.
To execute the branch expressions regardless of the condition expression, use IF.EAGER instead.
Examples
The following Product table calculated column definitions use the IF function in different ways to classify each
product based on its list price.
The first example tests whether the List Price column value is less than 500. When this condition is true, the
value Low is returned. Because there's no value_if_false value, BLANK is returned.
Examples in this article can be added to the Power BI Desktop sample model. To get the model, see DAX sample
model.
Price Group =
IF(
'Product'[List Price] < 500,
"Low"
)
The second example uses the same test, but this time includes a value_if_false value. So, the formula classifies
each product as either Low or High .
Price Group =
IF(
'Product'[List Price] < 500,
"Low",
"High"
)
The third example uses the same test, but this time nests an IF function to perform an additional test. So, the
formula classifies each product as either Low , Medium , or High .
Price Group =
IF(
'Product'[List Price] < 500,
"Low",
IF(
'Product'[List Price] < 1500,
"Medium",
"High"
)
)
TIP
When you need to nest multiple IF functions, the SWITCH function might be a better option. This function provides a
more elegant way to write an expression that returns more than two possible values.
See also
IF.EAGER function
SWITCH function (DAX)
Logical functions
IF.EAGER
8/25/2021 • 2 minutes to read
Checks a condition, and returns one value when TRUE, otherwise it returns a second value. It uses an eager
execution plan which always executes the branch expressions regardless of the condition expression.
Syntax
IF.EAGER(<logical_test>, <value_if_true>[, <value_if_false>])
Parameters
T ERM DEF IN IT IO N
Return value
Either value_if_true , value_if_false , or BLANK.
Remarks
The IF.EAGER function can return a variant data type if value_if_true and value_if_false are of different
data types, but the function attempts to return a single data type if both value_if_true and
value_if_false are of numeric data types. In the latter case, the IF.EAGER function will implicitly convert
data types to accommodate both values.
For example, the formula IF.EAGER(<condition>, TRUE(), 0)returns TRUE or 0, but the formula
IF.EAGER(<condition>, 1.0, 0)returns only decimal values even though value_if_false is of the whole
number data type. To learn more about implicit data type conversion, see Data types.
IF.EAGER has the same functional behavior as the IF function, but performance may differ due to
differences in execution plans. IF.EAGER(<logical_test>, <value_if_true>, <value_if_false>) has the
same execution plan as the following DAX expression:
Note: The two branch expressions are evaluated regardless of the condition expression.
Examples
See IF Examples.
See also
IF function
Logical functions
IFERROR
8/25/2021 • 2 minutes to read
Evaluates an expression and returns a specified value if the expression returns an error; otherwise returns the
value of the expression itself.
Syntax
IFERROR(value, value_if_error)
Parameters
T ERM DEF IN IT IO N
Return value
A scalar of the same type as value
Remarks
You can use the IFERROR function to trap and handle errors in an expression.
If value or value_if_error is an empty cell, IFERROR treats it as an empty string value ("").
The IFERROR function is based on the IF function, and uses the same error messages, but has fewer
arguments. The relationship between the IFERROR function and the IF function as follows:
IFERROR(A,B) := IF(ISERROR(A), B, A)
Values that are returned for A and B must be of the same data type; therefore, the column or expression
used for value and the value returned for value_if_error must be the same data type.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
For best practices when using IFERROR, see Appropriate use of error functions.
Example
The following example returns 9999 if the expression 25/0 evaluates to an error. If the expression returns a
value other than error, that value is passed to the invoking expression.
= IFERROR(25/0,9999)
See also
Logical functions
NOT
8/25/2021 • 2 minutes to read
Syntax
NOT(<logical>)
Parameters
T ERM DEF IN IT IO N
Return value
TRUE OR FALSE.
Example
The following example retrieves values from the calculated column that was created to illustrate the IF function.
For that example, the calculated column was named using the default name, Calculated Column1 , and
contains the following formula: = IF([Orders]<300,"true","false")
The formula checks the value in the column, [Orders], and returns "true" if the number of orders is under 300.
Now create a new calculated column, Calculated Column2 , and type the following formula.
= NOT([CalculatedColumn1])
For each row in Calculated Column1 , the values "true" and "false" are interpreted as the logical values TRUE or
FALSE, and the NOT function returns the logical opposite of that value.
See also
TRUE function
FALSE function
IF function
OR
8/25/2021 • 2 minutes to read
Checks whether one of the arguments is TRUE to return TRUE. The function returns FALSE if both arguments are
FALSE.
Syntax
OR(<logical1>,<logical2>)
Parameters
T ERM DEF IN IT IO N
Return value
A Boolean value. The value is TRUE if any of the two arguments is TRUE; the value is FALSE if both the
arguments are FALSE.
Remarks
The OR function in DAX accepts only two (2) arguments. If you need to perform an OR operation on
multiple expressions, you can create a series of calculations or, better, use the OR operator (|| ) to join all of
them in a simpler expression.
The function evaluates the arguments until the first TRUE argument, then returns TRUE.
Example
The following example shows how to use the OR function to obtain the sales people that belong to the Circle of
Excellence. The Circle of Excellence recognizes those who have achieved more than a million dollars in Touring
Bikes sales or sales of over two and a half million dollars in 2007.
Returns
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
Abbas, Syed E
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
Alberts, Amy
E
Ansman-
Wolfe, Pamela
O
Campbell,
David R
Ito, Shu K
Jiang,
Stephen Y
Mensa-
Annan, Tete A
Reiter, Tsvi
Michael
Tsoflias, Lynn
N
Valdez, Rachel
B
Vargas,
Garrett R
Varkey Circle of
Chudukatil, Excellence
Ranjit R
Evaluates an expression against a list of values and returns one of multiple possible result expressions.
Syntax
SWITCH(<expression>, <value>, <result>[, <value>, <result>]…[, <else>])
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A scalar value coming from one of the result expressions, if there was a match with value, or from the else
expression, if there was no match with any value.
Remarks
All result expressions and the else expression must be of the same data type.
Example
The following example creates a calculated column of month names.
Syntax
TRUE()
Return value
Always TRUE.
Remarks
The word TRUE is also interpreted as the logical value TRUE.
Example
The formula returns the logical value TRUE when the value in the column,
'InternetSales_USD'[SalesAmount_USD], is greater than 200000.
The following table shows the results when the example formula is used in a report with
'ProductCategory'[ProductCategoryName] in Row Labels and 'DateTime'[CalendarYear] in Column Labels.
GRA N D
RO W L A B EL S 2005 2006 2007 2008 - TOTA L
See also
FALSE
NOT
IF
Math and Trig functions
8/25/2021 • 2 minutes to read
The mathematical functions in Data Analysis Expressions (DAX) are very similar to the Excel mathematical and
trigonometric functions. This section lists the mathematical functions provided by DAX.
In this category
F UN C T IO N DESC RIP T IO N
QUOTIENT Performs division and returns only the integer portion of the
division result.
Syntax
ABS(<number>)
Parameters
T ERM DEF IN IT IO N
number The number for which you want the absolute value.
Return value
A decimal number.
Remarks
The absolute value of a number is a decimal number, whole or decimal, without its sign. You can use the ABS
function to ensure that only non-negative numbers are returned from expressions when nested in functions that
require a positive number.
Example
The following example returns the absolute value of the difference between the list price and the dealer price,
which you might use in a new calculated column, DealerMarkup .
= ABS([DealerPrice]-[ListPrice])
See also
Math and Trig functions
SIGN function
ACOS
8/25/2021 • 2 minutes to read
Returns the arccosine, or inverse cosine, of a number. The arccosine is the angle whose cosine is number. The
returned angle is given in radians in the range 0 (zero) to pi.
Syntax
ACOS(number)
Parameters
T ERM DEF IN IT IO N
Number The cosine of the angle you want and must be from -1 to 1.
Return value
Returns the arccosine, or inverse cosine, of a number.
Remarks
If you want to convert the result from radians to degrees, multiply it by 180/PI() or use the DEGREES function.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the inverse hyperbolic cosine of a number. The number must be greater than or equal to 1. The inverse
hyperbolic cosine is the value whose hyperbolic cosine is number, so ACOSH(COSH(number)) equals number.
Syntax
ACOSH(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse hyperbolic cosine of a number.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
ACOT(number)
Parameters
T ERM DEF IN IT IO N
Number The cosine of the angle you want. Must be a real number.
Return value
A single decimal value.
ACOTH
8/25/2021 • 2 minutes to read
Syntax
ACOTH(number)
Parameters
T ERM DEF IN IT IO N
Return value
A single decimal value.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
ASIN
8/25/2021 • 2 minutes to read
Returns the arcsine, or inverse sine, of a number. The arcsine is the angle whose sine is number. The returned
angle is given in radians in the range -pi/2 to pi/2.
Syntax
ASIN(number)
Parameters
T ERM DEF IN IT IO N
number The sine of the angle you want and must be from -1 to 1.
Return value
Returns the arcsine, or inverse sine, of a number.
Remarks
To express the arcsine in degrees, multiply the result by 180/PI( ) or use the DEGREES function.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the inverse hyperbolic sine of a number. The inverse hyperbolic sine is the value whose hyperbolic sine
is number, so ASINH(SINH(number)) equals number.
Syntax
ASINH(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse hyperbolic sine of a number.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the arctangent, or inverse tangent, of a number. The arctangent is the angle whose tangent is number.
The returned angle is given in radians in the range -pi/2 to pi/2.
Syntax
ATAN(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse hyperbolic tangent of a number.
Remarks
To express the arctangent in degrees, multiply the result by 180/PI( ) or use the DEGREES function.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the inverse hyperbolic tangent of a number. Number must be between -1 and 1 (excluding -1 and 1).
The inverse hyperbolic tangent is the value whose hyperbolic tangent is number, so ATANH(TANH(number))
equals number.
Syntax
ATANH(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse hyperbolic tangent of a number.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
= ATANH(-0.1) -0.100335348
See also
ATAN function
CEILING
8/25/2021 • 2 minutes to read
Rounds a number up, to the nearest integer or to the nearest multiple of significance.
Syntax
CEILING(<number>, <significance>)
Parameters
T ERM DEF IN IT IO N
Return value
A number rounded as specified.
Remarks
There are two CEILING functions in DAX, with the following differences:
The CEILING function emulates the behavior of the CEILING function in Excel.
The ISO.CEILING function follows the ISO-defined behavior for determining the ceiling value.
The two functions return the same value for positive numbers, but different values for negative numbers.
When using a positive multiple of significance, both CEILING and ISO.CEILING round negative numbers
upward (toward positive infinity). When using a negative multiple of significance, CEILING rounds
negative numbers downward (toward negative infinity), while ISO.CEILING rounds negative numbers
upward (toward positive infinity).
The return type is usually of the same type of the significant argument, with the following exceptions:
If the number argument type is currency, the return type is currency.
If the significance argument type is Boolean, the return type is integer.
If the significance argument type is non-numeric, the return type is real.
Example 1
The following formula returns 4.45. This might be useful if you want to avoid using smaller units in your pricing.
If an existing product is priced at $4.42, you can use CEILING to round prices up to the nearest unit of five cents.
= CEILING(4.42,0.05)
Example 2
The following formula returns similar results as the previous example, but uses numeric values stored in the
column, ProductPrice .
= CEILING([ProductPrice],0.05)
See also
Math and Trig functions
FLOOR function
ISO.CEILING function
ROUNDUP function
CONVERT
8/25/2021 • 2 minutes to read
Syntax
CONVERT(<Expression>, <Datatype>)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the value of <Expression>, translated to <Datatype>.
Remarks
The function returns an error when a value cannot be converted to the specified data type.
DAX calculated columns must be of a single data type. Since MEDIAN and MEDIANX functions over an
integer column return mixed data types, either integer or double, the following calculated column
expression will return an error as a result: MedianNumberCarsOwned = MEDIAN(DimCustomer[NumberCarsOwned]) .
To avoid mixed data types, change the expression to always return the double data type, for example:
MedianNumberCarsOwned = MEDIANX(DimCustomer, CONVERT([NumberCarsOwned], DOUBLE)) .
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
DAX query
Returns
[ VA L UE]
2
COS
8/25/2021 • 2 minutes to read
Syntax
COS(number)
Parameters
T ERM DEF IN IT IO N
number Required. The angle in radians for which you want the cosine.
Return value
Returns the cosine of the given angle.
Remarks
If the angle is in degrees, either multiply the angle by PI()/180 or use the RADIANS function to convert the angle
to radians.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
COSH(number)
Parameters
T ERM DEF IN IT IO N
number Required. Any real number for which you want to find the
hyperbolic cosine.
Return value
The hyperbolic cosine of a number.
Remarks
The formula for the hyperbolic cosine is:
$$\text{COSH}(z) = \frac{e^{z} + e^{-z}}{2}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
COT (<number>)
Parameters
T ERM DEF IN IT IO N
number The angle in radians for which you want the cotangent.
Return value
The cotangent of the given angle.
Remarks
The absolute value of number must be less than 2^27 and cannot be 0.
If number is outside its constraints, an error is returned.
If number is a non-numeric value, an error is returned.
Example
The following DAX query,
EVALUATE { COT(30) }
Returns
[ VA L UE]
-0.156119952161659
COTH
8/25/2021 • 2 minutes to read
Syntax
COTH (<number>)
Parameters
T ERM DEF IN IT IO N
number The hyperbolic angle in radians for which you want the
hyperbolic cotangent.
Return value
The hyperbolic cotangent of the given angle.
Remarks
The hyperbolic cotangent is an analog of the ordinary (circular) cotangent.
The absolute value of number must be less than $2^{27}$ and cannot be 0.
If number is outside its constraints, an error is returned
If number is a non-numeric value, an error is returned.
The following equation is used:
$$\text{COTH}(N) = \frac{1}{\text{TANH}(N)} = \frac{\text{COSH(N)}}{\text{SINH(N)}} = \frac{e^{N} + e^{-
N}}{e^{N} - e^{-N}}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query,
EVALUATE { COTH(2) }
Returns
[ VA L UE]
1.03731472072755
CURRENCY
8/25/2021 • 2 minutes to read
Evaluates the argument and returns the result as currency data type.
Syntax
CURRENCY(<value>)
Parameters
T ERM DEF IN IT IO N
value Any DAX expression that returns a single scalar value where
the expression is to be evaluated exactly once before all
other operations.
Return value
The value of the expression evaluated and returned as a currency type value.
Remarks
The CURRENCY function rounds up the 5th significant decimal, in value, to return the 4th decimal digit.
Rounding up occurs if the 5th significant decimal is equal or larger than 5. For example, if value is
3.6666666666666 then converting to currency returns \$3.6667. However, if value is 3.0123456789 then
converting to currency returns \$3.0123.
If the data type of the expression is TrueFalse then CURRENCY(<TrueFalse>) will return \$1.0000 for True
values and \$0.0000 for False values.
If the data type of the expression is Text then CURRENCY(<Text>) will try to convert text to a number. If
conversion succeeds the number will be converted to currency, otherwise an error is returned.
If the data type of the expression is DateTime then CURRENCY(<DateTime>) will convert the datetime
value to a number and that number to currency. DateTime values have an integer part that represents the
number of days between the given date and 1900-03-01 and a fraction that represents the fraction of a
day (where 12 hours or noon is 0.5 day). If the value of the expression is not a proper DateTime value an
error is returned.
Example
Convert number 1234.56 to currency data type.
= CURRENCY(1234.56)
Syntax
DEGREES(angle)
Parameters
T ERM DEF IN IT IO N
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
DIVIDE(<numerator>, <denominator> [,<alternateresult>])
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
Alternate result on divide by 0 must be a constant.
For best practices when using DIVIDE, see DIVIDE function vs. divide operator (/) in DAX.
Example
The following example returns 2.5.
= DIVIDE(5,2)
Example 1
The following example returns BLANK.
= DIVIDE(5,0)
Example 2
The following example returns 1.
= DIVIDE(5,0,1)
See also
QUOTIENT function
Math and Trig functions
EVEN
8/25/2021 • 2 minutes to read
Returns number rounded up to the nearest even integer. You can use this function for processing items that
come in twos. For example, a packing crate accepts rows of one or two items. The crate is full when the number
of items, rounded up to the nearest two, matches the crate's capacity.
Syntax
EVEN(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns number rounded up to the nearest even integer.
Remarks
If number is nonnumeric, EVEN returns the #VALUE! error value.
Regardless of the sign of number, a value is rounded up when adjusted away from zero. If number is an
even integer, no rounding occurs.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns e raised to the power of a given number. The constant e equals 2.71828182845904, the base of the
natural logarithm.
Syntax
EXP(<number>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Exceptions
Remarks
EXP is the inverse of LN, which is the natural logarithm of the given number.
To calculate powers of bases other than e, use the exponentiation operator (^). For more information, see
DAX Operator Reference.
Example
The following formula calculates e raised to the power of the number contained in the column, [Power] .
= EXP([Power])
See also
Math and Trig functions
LN function
EXP function
LOG function
LOG function
FACT
8/25/2021 • 2 minutes to read
Returns the factorial of a number, equal to the series 1*2*3*...* , ending in the given number.
Syntax
FACT(<number>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If the number is not an integer, it is truncated and an error is returned. If the result is too large, an error is
returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following formula returns the factorial for the series of integers in the column, [Values] .
= FACT([Values])
VA L UES RESULT S
0 1
1 1
2 2
3 6
4 24
VA L UES RESULT S
5 120
170 7.257415615308E+306
See also
Math and Trig functions
TRUNC function
FLOOR
8/25/2021 • 2 minutes to read
Syntax
FLOOR(<number>, <significance>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If either argument is nonnumeric, FLOOR returns **#VALUE!**error value.
If number and significance have different signs, FLOOR returns the **#NUM!**error value.
Regardless of the sign of the number, a value is rounded down when adjusted away from zero. If the
number is an exact multiple of significance, no rounding occurs.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following formula takes the values in the [Total Product Cost] column from the table, InternetSales.and
rounds down to the nearest multiple of .1.
The following table shows the expected results for some sample values.
10.8423 10.8
8.0373 8
VA L UES EXP EC T ED RESULT
2.9733 2.9
See also
Math and Trig functions
GCD
8/25/2021 • 2 minutes to read
Returns the greatest common divisor of two or more integers. The greatest common divisor is the largest
integer that divides both number1 and number2 without a remainder.
Syntax
GCD(number1, [number2], ...)
Parameters
T ERM DEF IN IT IO N
Return value
The greatest common divisor of two or more integers.
Remarks
If any argument is nonnumeric, GCD returns the #VALUE! error value.
If any argument is less than zero, GCD returns the #NUM! error value.
One divides any value evenly.
A prime number has only itself and one as even divisors.
If a parameter to GCD is >=2^53, GCD returns the #NUM! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
INT(<number>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
TRUNC and INT are similar in that both return integers. TRUNC removes the fractional part of the number. INT
rounds numbers down to the nearest integer based on the value of the fractional part of the number. INT and
TRUNC are different only when using negative numbers: TRUNC(-4.3) returns -4, but INT(-4.3) returns -5
because -5 is the lower number.
Example
The following expression rounds the value to 1. If you use the ROUND function, the result would be 2.
= INT(1.5)
See also
Math and Trig functions
ROUND function
ROUNDUP function
ROUNDDOWN function
MROUND function
ISO.CEILING
8/25/2021 • 2 minutes to read
Rounds a number up, to the nearest integer or to the nearest multiple of significance.
Syntax
ISO.CEILING(<number>[, <significance>])
Parameters
T ERM DEF IN IT IO N
Return value
A number, of the same type as the number argument, rounded as specified.
Remarks
There are two CEILING functions in DAX, with the following differences:
The CEILING function emulates the behavior of the CEILING function in Excel.
The ISO.CEILING function follows the ISO-defined behavior for determining the ceiling value.
The two functions return the same value for positive numbers, but different values for negative numbers. When
using a positive multiple of significance, both CEILING and ISO.CEILING round negative numbers upward
(toward positive infinity). When using a negative multiple of significance, CEILING rounds negative numbers
downward (toward negative infinity), while ISO.CEILING rounds negative numbers upward (toward positive
infinity).
The result type is usually the same type of the significance used as argument with the following exceptions:
If the first argument is of currency type then the result will be currency type.
If the optional argument is not included the result is of integer type.
If the significance argument is of Boolean type then the result is of integer type.
If the significance argument is non-numeric type then the result is of real type.
= ISO.CEILING(4.42,0.05)
= ISO.CEILING(-4.42,0.05)
See also
Math and Trig functions
FLOOR function
CEILING function
ROUNDUP function
LCM
8/25/2021 • 2 minutes to read
Returns the least common multiple of integers. The least common multiple is the smallest positive integer that is
a multiple of all integer arguments number1, number2, and so on. Use LCM to add fractions with different
denominators.
Syntax
LCM(number1, [number2], ...)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the least common multiple of integers.
Remarks
If any argument is nonnumeric, LCM returns the #VALUE! error value.
If any argument is less than zero, LCM returns the #NUM! error value.
If LCM(a,b) >=2^53, LCM returns the #NUM! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the natural logarithm of a number. Natural logarithms are based on the constant e
(2.71828182845904).
Syntax
LN(<number>)
Parameters
T ERM DEF IN IT IO N
number The positive number for which you want the natural
logarithm.
Return value
A decimal number.
Remarks
LN is the inverse of the EXP function.
Example
The following example returns the natural logarithm of the number in the column, [Values] .
= LN([Values])
See also
Math and Trig functions
EXP function
LOG
8/25/2021 • 2 minutes to read
Syntax
LOG(<number>,<base>)
Parameters
T ERM DEF IN IT IO N
number The positive number for which you want the logarithm.
Return value
A decimal number.
Remarks
You might receive an error if the value is too large to be displayed.
The function LOG10 is similar, but always returns the common logarithm, meaning the logarithm for the base
10.
Example
The following formulas return the same result, 2.
= LOG(100,10)
= LOG(100)
= LOG10(100)
See also
Math and Trig functions
EXP function
LOG function
LOG function
LOG10
8/25/2021 • 2 minutes to read
Syntax
LOG10(<number>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
The LOG function lets you change the base of the logarithm, instead of using the base 10.
Example
The following formulas return the same result, 2:
= LOG(100,10)
= LOG(100)
= LOG10(100)
See also
Math and Trig functions
EXP function
LOG function
LOG function
MOD
8/25/2021 • 2 minutes to read
Returns the remainder after a number is divided by a divisor. The result always has the same sign as the divisor.
Syntax
MOD(<number>, <divisor>)
Parameters
T ERM DEF IN IT IO N
number The number for which you want to find the remainder after
the division is performed.
Return value
A whole number.
Remarks
If the divisor is 0 (zero), MOD returns an error. You cannot divide by 0.
The MOD function can be expressed in terms of the INT function: MOD(n, d) = n - d*INT(n/d)
Example 1
The following formula returns 1, the remainder of 3 divided by 2.
= MOD(3,2)
Example 2
The following formula returns -1, the remainder of 3 divided by 2. Note that the sign is always the same as the
sign of the divisor.
= MOD(-3,-2)
See also
Math and Trig functions
ROUND function
ROUNDUP function
ROUNDDOWN function
MROUND function
INT function
MROUND
8/25/2021 • 2 minutes to read
Syntax
MROUND(<number>, <multiple>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
MROUND rounds up, away from zero, if the remainder of dividing number by the specified multiple is greater
than or equal to half the value of multiple .
= MROUND(1.3,0.2)
= MROUND(-10,-3)
Example: Error
The following expression returns an error, because the numbers have different signs.
= MROUND(5,-2)
See also
Math and Trig functions
ROUND function
ROUNDUP function
ROUNDDOWN function
MROUND function
INT function
ODD
8/25/2021 • 2 minutes to read
Syntax
ODD(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns number rounded up to the nearest odd integer.
Remarks
If number is nonnumeric, ODD returns the #VALUE! error value.
Regardless of the sign of number, a value is rounded up when adjusted away from zero. If number is an
odd integer, no rounding occurs.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
PI()
Return value
A decimal number with the value of Pi, 3.14159265358979, accurate to 15 digits.
Remarks
Pi is a mathematical constant. In DAX, Pi is represented as a real number accurate to 15 digits, the same as Excel.
Example
The following formula calculates the area of a circle given the radius in the column, [Radius] .
= PI()*([Radius]*2)
See also
Math and Trig functions
POWER
8/25/2021 • 2 minutes to read
Syntax
POWER(<number>, <power>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Example
The following example returns 25.
= POWER(5,2)
See also
Math and Trig functions
QUOTIENT
8/25/2021 • 2 minutes to read
Performs division and returns only the integer portion of the division result. Use this function when you want to
discard the remainder of division.
Syntax
QUOTIENT(<numerator>, <denominator>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
If either argument is non-numeric, QUOTIENT returns the #VALUE! error value.
You can use a column reference instead of a literal value for either argument. However, if the column that
you reference contains a 0 (zero), an error is returned for the entire column of values.
Example
The following formulas return the same result, 2.
= QUOTIENT(5,2)
= QUOTIENT(10/2,2)
See also
Math and Trig functions
RADIANS
8/25/2021 • 2 minutes to read
Syntax
RADIANS(angle)
Parameters
T ERM DEF IN IT IO N
Example
F O RM UL A DESC RIP T IO N RESULT
Returns a random number greater than or equal to 0 and less than 1, evenly distributed. The number that is
returned changes each time the cell containing this function is recalculated.
Syntax
RAND()
Return value
A decimal number.
Remarks
Recalculation depends on various factors, including whether the model is set to Manual or Automatic
recalculation mode, and whether data has been refreshed.
RAND and other volatile functions that do not have fixed values are not always recalculated. For example,
execution of a query or filtering will usually not cause such functions to be re-evaluated. However, the
results for these functions will be recalculated when the entire column is recalculated. These situations
include refresh from an external data source or manual editing of data that causes re-evaluation of
formulas that contain these functions.
RAND is always recalculated if the function is used in the definition of a measure.
RAND function cannot return a result of zero, to prevent errors such as division by zero.
Examples
To generate a random real number between two other numbers, use:
= RAND()*(b-a)+a
= RAND()
= RAND()*100
To generate a random whole number greater than 0 and less than 100
INT(RAND()*100)
See also
Math and Trig functions
Statistical functions
RANDBETWEEN
8/25/2021 • 2 minutes to read
Returns a random number in the range between two numbers you specify.
Syntax
RANDBETWEEN(<bottom>,<top>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following formula returns a random number between 1 and 10.
= RANDBETWEEN(1,10)
See also
Math and Trig functions
Statistical functions
ROUND
8/25/2021 • 2 minutes to read
Syntax
ROUND(<number>, <num_digits>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If num_digits is greater than 0 (zero), then number is rounded to the specified number of decimal
places.
If num_digits is 0, the number is rounded to the nearest integer.
If num_digits is less than 0, the number is rounded to the left of the decimal point.
Related functions
To always round up (away from zero), use the ROUNDUP function.
To always round down (toward zero), use the ROUNDDOWN function.
To round a number to a specific multiple (for example, to round to the nearest multiple of 0.5), use the
MROUND function.
Use the functions TRUNC and INT to obtain the integer portion of the number.
Example 1
The following formula rounds 2.15 up, to one decimal place. The expected result is 2.2.
= ROUND(2.15,1)
Example 2
The following formula rounds 21.5 to one decimal place to the left of the decimal point. The expected result is
20.
= ROUND(21.5,-1)
See also
Math and Trig functions
ROUND
ROUNDDOWN
MROUND
INT
TRUNC
ROUNDDOWN
8/25/2021 • 2 minutes to read
Syntax
ROUNDDOWN(<number>, <num_digits>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If num_digits is greater than 0 (zero), then the value in number is rounded down to the specified
number of decimal places.
If num_digits is 0, then the value in number is rounded down to the nearest integer.
If num_digits is less than 0, then the value in number is rounded down to the left of the decimal point.
ROUNDDOWN behaves like ROUND, except that it always rounds a number down. The INT function also
rounds down, but with INT the result is always an integer, whereas with ROUNDDOWN you can control
the precision of the result.
Example 1
The following example rounds 3.14159 down to three decimal places. The expected result is 3.141.
= ROUNDDOWN(3.14159,3)
Example 2
The following example rounds the value of 31415.92654 down to 2 decimal places to the left of the decimal. The
expected result is 31400.
= ROUNDDOWN(31415.92654, -2)
See also
Math and Trig functions
ROUND
ROUNDUP
ROUNDDOWN
MROUND
INT
ROUNDUP
8/25/2021 • 2 minutes to read
Syntax
ROUNDUP(<number>, <num_digits>)
Parameters
T ERM DEF IN IT IO N
Return value
A decimal number.
Remarks
If num_digits is greater than 0 (zero), then the number is rounded up to the specified number of decimal
places.
If num_digits is 0, then number is rounded up to the nearest integer.
If num_digits is less than 0, then number is rounded up to the left of the decimal point.
ROUNDUP behaves like ROUND, except that it always rounds a number up.
Example
The following formula rounds Pi to four decimal places. The expected result is 3.1416.
= ROUNDUP(PI(),4)
= ROUNDUP(1.3,0.2)
= ROUNDUP([Values],-1)
When num_digits is less than zero, the number of places to the left of the decimal sign is increased by the
value you specify.
13.25 20
2.45 10
25.56 30
1.34 10
345.01 350
See also
Math and Trig functions
ROUND
ROUNDDOWN
MROUND
INT
SIGN
8/25/2021 • 2 minutes to read
Determines the sign of a number, the result of a calculation, or a value in a column. The function returns 1 if the
number is positive, 0 (zero) if the number is zero, or -1 if the number is negative.
Syntax
SIGN(<number>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number. The possible Return values are 1, 0, and -1.
Example
The following formula returns the sign of the result of the expression that calculates sale price minus cost.
See also
Math and Trig functions
SIN
8/25/2021 • 2 minutes to read
Syntax
SIN(number)
Parameters
T ERM DEF IN IT IO N
number Required. The angle in radians for which you want the sine.
Return value
Returns the sine of the given angle.
Remarks
If an argument is in degrees, multiply it by PI()/180 or use the RADIANS function to convert it to radians.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
SINH(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the hyperbolic sine of a number.
Remarks
The formula for the hyperbolic sine is:
$$\text{SINH}(z) = \frac{e^{z} - e^{-z}}{2}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
Probability of obtaining a result of less than 1.03 seconds.
= 2.868*SINH(0.0342\*1.03)
Returns, 0.1010491
SQRT
8/25/2021 • 2 minutes to read
Syntax
SQRT(<number>)
Parameters
T ERM DEF IN IT IO N
number The number for which you want the square root, a column
that contains numbers, or an expression that evaluates to a
number.
Return value
A decimal number.
Remarks
If the number is negative, the SQRT function returns an error.
Example
The following formula,
= SQRT(25)
See also
Math and Trig functions
SQRTPI
8/25/2021 • 2 minutes to read
Syntax
SQRTPI(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the square root of (number * pi).
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
TAN(number)
Parameters
T ERM DEF IN IT IO N
number Required. The angle in radians for which you want the
tangent.
Return value
Returns the tangent of the given angle.
Remarks
If your argument is in degrees, multiply it by PI()/180 or use the RADIANS function to convert it to radians.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
TANH(number)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the hyperbolic tangent of a number.
Remarks
The formula for the hyperbolic tangent is:
$$\text{TANH}(z) = \frac{\text{SINH}(z)}{\text{COSH}(z)}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Truncates a number to an integer by removing the decimal, or fractional, part of the number.
Syntax
TRUNC(<number>,<num_digits>)
Parameters
T ERM DEF IN IT IO N
Return value
A whole number.
Remarks
TRUNC and INT are similar in that both return integers. TRUNC removes the fractional part of the number. INT
rounds numbers down to the nearest integer based on the value of the fractional part of the number. INT and
TRUNC are different only when using negative numbers: TRUNC(-4.3) returns -4, but INT(-4.3) returns -5
because -5 is the smaller number.
Example 1
The following formula returns 3, the integer part of pi.
= TRUNC(PI())
Example 2
The following formula returns -8, the integer part of -8.9.
= TRUNC(-8.9)
See also
Math and Trig functions
ROUND
ROUNDUP
ROUNDDOWN
MROUND
INT
Other functions
8/25/2021 • 2 minutes to read
These functions perform unique actions that cannot be defined by any of the categories.
In this category
F UN C T IO N DESC RIP T IO N
Returns a blank.
Syntax
BLANK()
Return value
A blank.
Remarks
Blanks are not equivalent to nulls. DAX uses blanks for both database nulls and for blank cells in Excel.
Some DAX functions treat blank cells somewhat differently from Microsoft Excel. Blanks and empty
strings ("") are not always equivalent, but some operations may treat them as such.
Example
The following example illustrates how you can work with blanks in formulas. The formula calculates the ratio of
sales between the Resellers and the Internet channels. However, before attempting to calculate the ratio the
denominator should be checked for zero values. If the denominator is zero then a blank value should be
returned; otherwise, the ratio is calculated.
The table shows the expected results when this formula is used to create a table visualization.
In the original data source, the column evaluated by the BLANK function might have included text, empty
strings, or nulls. If the original data source was a SQL Server database, nulls and empty strings are different
kinds of data. However, for this operation an implicit type cast is performed and DAX treats them as the same.
See also
Text functions
ISBLANK function
ERROR
8/25/2021 • 2 minutes to read
Syntax
ERROR(<text>)
Parameters
T ERM DEF IN IT IO N
Return value
None
Remarks
The ERROR function can be placed in a DAX expression anywhere a scalar value is expected.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following DAX query:
DEFINE
MEASURE DimProduct[Measure] =
IF(
SELECTEDVALUE(DimProduct[Color]) = "Red",
ERROR("red color encountered"),
SELECTEDVALUE(DimProduct[Color])
)
EVALUATE SUMMARIZECOLUMNS(DimProduct[Color], "Measure", [Measure])
ORDER BY [Color]
Fails and raises and error message containing "red color encountered".
Example 2
The following DAX query:
DEFINE
MEASURE DimProduct[Measure] =
IF(
SELECTEDVALUE(DimProduct[Color]) = "Magenta",
ERROR("magenta color encountered"),
SELECTEDVALUE(DimProduct[Color])
)
EVALUATE SUMMARIZECOLUMNS(DimProduct[Color], "Measure", [Measure])
ORDER BY [Color]
Black Black
Blue Blue
Grey Grey
Multi Multi
NA NA
Red Red
Silver Silver
Silver\Black Silver\Black
White White
Yellow Yellow
Because Magenta is not one of the product colors, the ERROR function is not executed.
Parent and Child functions
8/25/2021 • 2 minutes to read
These functions manage data that is presented as parent/child hierarchies. To learn more, see Understanding
functions for Parent-Child Hierarchies in DAX.
In this category
F UN C T IO N DESC RIP T IO N
PATH Returns a delimited text string with the identifiers of all the
parents of the current identifier.
PATHCONTAINS Returns TRUE if the specified item exists within the specified
path.
DAX provides five functions to help users manage data that is presented as a parent-child hierarchy in their
models. With this functions a user can obtain the entire lineage of parents a row has, how many levels has the
lineage to the top parent, who is the parent n-levels above the current row, who is the n-descendant from the
top of the current row hierarchy and is certain parent a parent in the current row hierarchy?
112
14 112
3 14
11 3
13 3
162 3
117 162
221 162
81 162
In the above table you can see that employee 112 has no parent defined, employee 14 has employee 112 as
manager (ParentEmployeeKey), employee 3 has employee 14 as manager and employees 11, 13, and 162 have
employee 3 as manager. The above helps to understand that employee 112 has no manager above her/him and
she/he is the top manager for all employees shown here; also, employee 3 reports to employee 14 and
employees 11, 13, 162 report to 3.
The following table presents the available functions, a brief description of the function and an example of the
function over the same data shown above.
PATH function - Returns a delimited text with the identifiers of all the parents to the current row, starting with the
oldest or top most until current.
112 112
EM P LO Y EEK EY PA REN T EM P LO Y EEK EY PAT H
14 112 112|14
3 14 112|14|3
11 3 112|14|3|11
13 3 112|14|3|13
162 3 112|14|3|162
81 162 112|14|3|162|81
PATHLENGTH function - Returns the number of levels in a given PATH(), starting at current level until the oldest
or top most parent level. In the following example column PathLength is defined as ' = PATHLENGTH([Path]) '; the
example includes all data from the Path() example to help understand how this function works.
112 112 1
14 112 112|14 2
3 14 112|14|3 3
11 3 112|14|3|11 4
13 3 112|14|3|13 4
162 3 112|14|3|162 4
81 162 112|14|3|162|81 5
PATHITEM function - Returns the item at the specified position from a PATH() like result, counting from left to
right. In the following example column PathItem - 4th from left is defined as ' = PATHITEM([Path], 4) '; this
example returns the EmployeKey at fourth position in the Path string from the left, using the same sample data
from the Path() example.
PAT H IT EM - 4T H F RO M
EM P LO Y EEK EY PA REN T EM P LO Y EEK EY PAT H L EF T
112 112
14 112 112|14
PAT H IT EM - 4T H F RO M
EM P LO Y EEK EY PA REN T EM P LO Y EEK EY PAT H L EF T
3 14 112|14|3
11 3 112|14|3|11 11
13 3 112|14|3|13 13
PATHITEMREVERSE function - Returns the item at position from a PATH() like function result, counting backwards
from right to left.
In the following example column PathItemReverse - 3rd from right is defined as ' = PATHITEMREVERSE([Path], 3) ';
this example returns the EmployeKey at third position in the Path string from the right, using the same sample
data from the Path() example.
112 112
14 112 112|14
3 14 112|14|3 112
11 3 112|14|3|11 14
13 3 112|14|3|13 14
162 3 112|14|3|162 14
81 162 112|14|3|162|81 3
PATHCONTAINS function - Returns TRUE if the specified item exists within the specified path. In the following
example column PathContains - employee 162 is defined as ' = PATHCONTAINS([Path], "162") '; this example
returns TRUE if the given path contains employee 162. This example uses the results from the Path() example
above.
PAT H C O N TA IN S -
EM P LO Y EEK EY PA REN T EM P LO Y EEK EY PAT H EM P LO Y EE 162
3 14 112|14|3 FALSE
11 3 112|14|3|11 FALSE
13 3 112|14|3|13 FALSE
Returns a delimited text string with the identifiers of all the parents of the current identifier, starting with the
oldest and continuing until current.
Syntax
PATH(<ID_columnName>, <parent_columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
A delimited text string containing the identifiers of all the parents to the current identifier.
Remarks
This function is used in tables that have some kind of internal hierarchy, to return the items that are
related to the current row value. For example, in an Employees table that contains employees, the
managers of employees, and the managers of the managers, you can return the path that connects an
employee to his or her manager.
The path is not constrained to a single level of parent-child relationships; it can return related rows that
are several levels up from the specified starting row.
The delimiter used to separate the ascendants is the vertical bar, '|'.
The values in ID_columnName and parent_columnName must have the same data type, text or integer.
Values in parent_columnName must be present in ID_columnName. That is, you cannot look up a
parent if there is no value at the child level.
If parent_columnName is BLANK then PATH() returns ID_columnName value. In other words, if you
look for the manager of an employee but the parent_columnName column has no data, the PATH
function returns just the employee ID.
If ID_columnName has duplicates and parent_columnName is the same for those duplicates then
PATH() returns the common parent_columnName value; however, if parent_columnName value is
different for those duplicates then PATH() returns an error. In other words, if you have two listings for
the same employee ID and they have the same manager ID, the PATH function returns the ID for that
manager. However, if there are two identical employee IDs that have different manager IDs, the PATH
function returns an error.
If ID_columnName is BLANK then PATH() returns BLANK.
If ID_columnName contains a vertical bar '|' then PATH() returns an error.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example creates a calculated column that lists all the managers for each employee.
= PATH(Employee[EmployeeKey], Employee[ParentEmployeeKey])
PATHCONTAINS
8/25/2021 • 2 minutes to read
Returns TRUE if the specified item exists within the specified path.
Syntax
PATHCONTAINS(<path>, <item>)
Parameters
T ERM DEF IN IT IO N
Return value
A value of TRUE if item exists in path; otherwise FALSE .
Remarks
If item is an integer number it is converted to text and then the function is evaluated. If conversion fails
then the function returns an error.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example creates a calculated column that takes a manager ID and checks a set of employees. If the
manager ID is among the list of managers returned by the PATH function, the PATHCONTAINS function returns
true; otherwise it returns false.
Returns the item at the specified position from a string resulting from evaluation of a PATH function. Positions
are counted from left to right.
Syntax
PATHITEM(<path>, <position>[, <type>])
Parameters
T ERM DEF IN IT IO N
type enumeration
Return value
The identifier returned by the PATH function at the specified position in the list of identifiers. Items returned by
the PATH function are ordered by most distant to current.
Remarks
This function can be used to return a specific level from a hierarchy returned by a PATH function. For
example, you could return just the skip-level managers for all employees.
If you specify a number for position that is less than one (1) or greater than the number of elements in
path, the PATHITEM function returns BLANK
If type is not a valid enumeration element an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns the third tier manager of the current employee; it takes the employee and
manager IDs as the input to a PATH function that returns a string with the hierarchy of parents to current
employee. From that string PATHITEM returns the third entry as an integer.
= PATHITEM(PATH(Employee[EmployeeKey], Employee[ParentEmployeeKey]), 3, 1)
PATHITEMREVERSE
8/25/2021 • 2 minutes to read
Returns the item at the specified position from a string resulting from evaluation of a PATH function. Positions
are counted backwards from right to left.
Syntax
PATHITEMREVERSE(<path>, <position>[, <type>])
Parameters
T ERM DEF IN IT IO N
type enumeration
Return value
The n-position ascendant in the given path, counting from current to the oldest.
Remarks
This function can be used to get an individual item from a hierarchy resulting from a PATH function.
This function reverses the standard order of the hierarchy, so that closest items are listed first, For
example, if the PATh function returns a list of managers above an employee in a hierarchy, the
PATHITEMREVERSE function returns the employee's immediate manager in position 2 because position 1
contains the employee's id.
If the number specified for position is less than one (1) or greater than the number of elements in path,
the PATHITEM function returns BLANK.
If type is not a valid enumeration element an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example takes an employee ID column as the input to a PATH function, and reverses the list of
grandparent elements that are returned. The position specified is 3 and the return type is 1; therefore, the
PATHITEMREVERSE function returns an integer representing the manager two levels up from the employee.
= PATHITEMREVERSE(PATH(Employee[EmployeeKey], Employee[ParentEmployeeKey]), 3, 1)
PATHLENGTH
8/25/2021 • 2 minutes to read
Returns the number of parents to the specified item in a given PATH result, including self.
Syntax
PATHLENGTH(<path>)
Parameters
T ERM DEF IN IT IO N
Return value
The number of items that are parents to the specified item in a given PATH result, including the specified item.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following example takes an employee ID as input to a PATH function and returns a list of the managers
above that employee in the hierarchy, The PATHLENGTH function takes that result and counts the different levels
of employees and managers, including the employee you started with.
= PATHLENGTH(PATH(Employee[EmployeeKey], Employee[ParentEmployeeKey]))
Relationship functions
8/25/2021 • 2 minutes to read
Functions in this category are for managing and utilizing relationships between tables.
In this category
F UN C T IO N DESC RIP T IO N
Specifies the cross-filtering direction to be used in a calculation for a relationship that exists between two
columns.
Syntax
CROSSFILTER(<columnName1>, <columnName2>, <direction>)
Parameters
T ERM DEF IN IT IO N
Return value
The function returns no value; the function only sets the cross-filtering direction for the indicated relationship,
for the duration of the query.
Remarks
In the case of a 1:1 relationship, there is no difference between the one and both direction.
CROSSFILTER can only be used in functions that take a filter as an argument, for example: CALCULATE,
CALCULATETABLE, CLOSINGBALANCEMONTH, CLOSINGBALANCEQUARTER, CLOSINGBALANCEYEAR,
OPENINGBALANCEMONTH, OPENINGBALANCEQUARTER, OPENINGBALANCEYEAR, TOTALMTD,
TOTALQTD and TOTALYTD functions.
CROSSFILTER uses existing relationships in the model, identifying relationships by their ending point
columns.
In CROSSFILTER, the cross-filtering setting of a relationship is not important; that is, whether the
relationship is set to filter one, or both directions in the model does not affect the usage of the function.
CROSSFILTER will override any existing cross-filtering setting.
An error is returned if any of the columns named as an argument is not part of a relationship or the
arguments belong to different relationships.
If CALCULATE expressions are nested, and more than one CALCULATE expression contains a
CROSSFILTER function, then the innermost CROSSFILTER is the one that prevails in case of a conflict or
ambiguity.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the following model diagram, both DimProduct and DimDate have a single direction relationship with
FactOnlineSales.
By using the CROSSFILTER function in our measure expression, we get the expected results:
RELATED
8/25/2021 • 2 minutes to read
Syntax
RELATED(<column>)
Parameters
T ERM DEF IN IT IO N
column The column that contains the values you want to retrieve.
Return value
A single value that is related to the current row.
Remarks
The RELATED function requires that a relationship exists between the current table and the table with
related information. You specify the column that contains the data that you want, and the function follows
an existing many-to-one relationship to fetch the value from the specified column in the related table. If a
relationship does not exist, you must create a relationship.
When the RELATED function performs a lookup, it examines all values in the specified table regardless of
any filters that may have been applied.
The RELATED function needs a row context; therefore, it can only be used in calculated column
expression, where the current row context is unambiguous, or as a nested function in an expression that
uses a table scanning function. A table scanning function, such as SUMX, gets the value of the current row
value and then scans another table for instances of that value.
The RELATED function cannot be used to fetch a column across a limited relationship.
Example
In the following example, the measure Non USA Internet Sales is created to produce a sales report that excludes
sales in the United States. In order to create the measure, the InternetSales_USD table must be filtered to exclude
all sales that belong to the United States in the SalesTerritory table. The United States, as a country, appears 5
times in the SalesTerritory table; once for each of the following regions: Northwest, Northeast, Central,
Southwest, and Southeast.
The first approach to filter the Internet Sales, in order to create the measure, could be to add a filter expression
like the following:
FILTER('InternetSales_USD'
, 'InternetSales_USD'[SalesTerritoryKey]<>1 && 'InternetSales_USD'[SalesTerritoryKey]<>2 &&
'InternetSales_USD'[SalesTerritoryKey]<>3 && 'InternetSales_USD'[SalesTerritoryKey]<>4 &&
'InternetSales_USD'[SalesTerritoryKey]<>5)
However, this approach is counterintuitive, prone to typing errors, and might not work if any of the existing
regions is split in the future.
A better approach would be to use the existing relationship between InternetSales_USD and SalesTerritory and
explicitly state that the country must be different from the United States. To do so, create a filter expression like
the following:
This expression uses the RELATED function to lookup the country value in the SalesTerritory table, starting with
the value of the key column, SalesTerritoryKey, in the InternetSales_USD table. The result of the lookup is used
by the filter function to determine if the InternetSales_USD row is filtered or not.
NOTE
If the example does not work, you might need to create a relationship between the tables.
= SUMX(FILTER( 'InternetSales_USD'
, RELATED('SalesTerritory'[SalesTerritoryCountry])
<>"United States"
)
,'InternetSales_USD'[SalesAmount_USD])
The following table shows only totals for each region, to prove that the filter expression in the measure, Non
USA Internet Sales, works as intended.
The following shows what that you might get if you used this measure in a report table visual:
See also
RELATEDTABLE
Filter functions
RELATEDTABLE
8/25/2021 • 2 minutes to read
Syntax
RELATEDTABLE(<tableName>)
Parameters
T ERM DEF IN IT IO N
Return value
A table of values.
Remarks
The RELATEDTETABLE function changes the context in which the data is filtered, and evaluates the
expression in the new context that you specify.
This function is a shortcut for CALCULATETABLE function with no logical expression.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example uses the RELATEDTABLE function to create a calculated column with the Internet Sales in
the Product Category table:
= SUMX( RELATEDTABLE('InternetSales_USD')
, [SalesAmount_USD])
1 1 Bikes $28,318,144.65
2 2 Components
3 3 Clothing $339,772.61
P RO DUC T C AT EGO RY P RO DUC T C AT EGO RY
P RO DUC T C AT EGO RY K EY A LT ERN AT EK EY NAME IN T ERN ET SA L ES
4 4 Accessories $700,759.96
See also
CALCULATETABLE
Filter functions
USERELATIONSHIP
8/25/2021 • 2 minutes to read
Specifies the relationship to be used in a specific calculation as the one that exists between columnName1 and
columnName2.
Syntax
USERELATIONSHIP(<columnName1>,<columnName2>)
Parameters
T ERM DEF IN IT IO N
Return value
The function returns no value; the function only enables the indicated relationship for the duration of the
calculation.
Remarks
USERELATIONSHIP can only be used in functions that take a filter as an argument, for example:
CALCULATE, CALCULATETABLE, CLOSINGBALANCEMONTH, CLOSINGBALANCEQUARTER,
CLOSINGBALANCEYEAR, OPENINGBALANCEMONTH, OPENINGBALANCEQUARTER,
OPENINGBALANCEYEAR, TOTALMTD, TOTALQTD and TOTALYTD functions.
USERELATIONSHIP cannot be used when row level security is defined for the table in which the measure
is included. For example,
CALCULATE(SUM([SalesAmount]), USERELATIONSHIP(FactInternetSales[CustomerKey],
DimCustomer[CustomerKey]))
will return an error if row level security is defined for DimCustomer.
USERELATIONSHIP uses existing relationships in the model, identifying relationships by their ending
point columns.
In USERELATIONSHIP, the status of a relationship is not important; that is, whether the relationship is
active or not does not affect the usage of the function. Even if the relationship is inactive, it will be used
and overrides any other active relationships that might be present in the model but not mentioned in the
function arguments.
An error is returned if any of the columns named as an argument is not part of a relationship or the
arguments belong to different relationships.
If multiple relationships are needed to join table A to table B in a calculation, each relationship must be
indicated in a different USERELATIONSHIP function.
If CALCULATE expressions are nested, and more than one CALCULATE expression contains a
USERELATIONSHIP function, then the innermost USERELATIONSHIP is the one that prevails in case of a
conflict or ambiguity.
Up to 10 USERELATIONSHIP functions can be nested; however, your expression might have a deeper level
of nesting, ie. the following sample expression is nested 3 levels deep but only 2 for USEREALTIONSHIP:
=CALCULATE(CALCULATE( CALCULATE( <anyExpression>, USERELATIONSHIP( t1[colA], t2[colB])),
t99[colZ]=999), USERELATIONSHIP( t1[colA], t2[colA]))
.
Example
The following sample shows how to override the default, active, relationship between InternetSales and
DateTime tables. The default relationship exists between the OrderDate column, in the InternetSales table, and
the Date column, in the DateTime table.
To calculate the sum of internet sales and allow slicing by ShippingDate instead of the traditional OrderDate,
create measure, [InternetSales by ShippingDate] using the following expression:
Relationships between InternetSales[ShipmentDate] and DateTime[Date] must exist and should not be the active
relationship; also, the relationship between InternetSales[OrderDate] and DateTime[Date] should exist and
should be the active relationship.
Statistical functions
8/25/2021 • 2 minutes to read
Statistical functions calculate values related to statistical distributions and probability, such as standard deviation
and number of permutations.
In this category
F UN C T IO N DESC RIP T IO N
NORM.DIST Returns the normal distribution for the specified mean and
standard deviation.
Returns the beta distribution. The beta distribution is commonly used to study variation in the percentage of
something across samples, such as the fraction of the day people spend watching television.
Syntax
BETA.DIST(x,alpha,beta,cumulative,[A],[B])
Parameters
T ERM DEF IN IT IO N
Return value
Returns the beta distribution.
Remarks
If any argument is nonnumeric, BETA.DIST returns the #VALUE! error value.
If any argument is not an integer, it is rounded.
If alpha ≤ 0 or beta ≤ 0, BETA.DIST returns the #NUM! error value.
If x < A, x > B, or A = B, BETA.DIST returns the #NUM! error value.
If you omit values for A and B, BETA.DIST uses the standard cumulative beta distribution, so that A = 0
and B = 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
BETA.INV
8/25/2021 • 2 minutes to read
Returns the inverse of the beta cumulative probability density function (BETA.DIST).
If probability = BETA.DIST(x,...TRUE), then BETA.INV(probability,...) = x. The beta distribution can be used in project
planning to model probable completion times given an expected completion time and variability.
Syntax
BETA.INV(probability,alpha,beta,[A],[B])
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse of the beta cumulative probability density function (BETA.DIST).
Remarks
If any argument is nonnumeric, BETA.INV returns the #VALUE! error value.
If any argument is not an integer, it is rounded.
If alpha ≤ 0 or beta ≤ 0, BETA.INV returns the #NUM! error value.
If probability ≤ 0 or probability > 1, BETA.INV returns the #NUM! error value.
If you omit values for A and B, BETA.INV uses the standard cumulative beta distribution, so that A = 0 and
B = 1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
CHISQ.DIST
8/25/2021 • 2 minutes to read
Syntax
CHISQ.DIST(<x>, <deg_freedom>, <cumulative>)
Parameters
T ERM DEF IN IT IO N
Return value
The chi-squared distribution.
Remarks
If x or deg_freedom is nonnumeric, an error is returned.
If deg_freedom is not an integer, it is rounded.
If x < 0, an error is returned.
If deg_freedom < 1 or deg_freedom > 10^10, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query,
Returns
[ VA L UE]
0.632120558828558
CHISQ.DIST.RT
8/25/2021 • 2 minutes to read
Syntax
CHISQ.DIST.RT(<x>, <deg_freedom>)
Parameters
T ERM DEF IN IT IO N
Return value
The right-tailed probability of the chi-squared distribution.
Remarks
If x or deg_freedom is nonnumeric, an error is returned.
If deg_freedom is not an integer, it is rounded.
If x < 0, an error is returned.
If deg_freedom < 1 or deg_freedom > 10^10, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query,
EVALUATE { CHISQ.DIST.RT(2, 5) }
Returns
[ VA L UE]
0.84914503608461
CHISQ.INV
8/25/2021 • 2 minutes to read
Syntax
CHISQ.INV(probability,deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse of the left-tailed probability of the chi-squared distribution.
Remarks
If argument is nonnumeric, CHISQ.INV returns the #VALUE! error value.
If probability < 0 or probability > 1, CHISQ.INV returns the #NUM! error value.
If deg_freedom is not an integer, it is rounded.
If deg_freedom < 0 or deg_freedom > 10^10, CHISQ.INV returns the #NUM! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Syntax
CHISQ.INV.RT(probability,deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse of the right-tailed probability of the chi-squared distribution.
Remarks
If either argument is nonnumeric, CHISQ.INV.RT returns the #VALUE! error value.
If probability < 0 or probability > 1, CHISQ.INV.RT returns the #NUM! error value.
If deg_freedom is not an integer, it is rounded.
If deg_freedom < 1, CHISQ.INV.RT returns the #NUM! error value.
Given a value for probability, CHISQ.INV.RT seeks that value x such that CHISQ.DIST.RT(x, deg_freedom) =
probability. Thus, precision of CHISQ.INV.RT depends on precision of CHISQ.DIST.RT. CHISQ.INV.RT uses an
iterative search technique. If the search has not converged after 64 iterations, the function returns the
#N/A error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
COMBIN
8/25/2021 • 2 minutes to read
Returns the number of combinations for a given number of items. Use COMBIN to determine the total possible
number of groups for a given number of items.
Syntax
COMBIN(number, number_chosen)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the number of combinations for a given number of items.
Remarks
Numeric arguments are truncated to integers.
If either argument is nonnumeric, COMBIN returns the #VALUE! error value.
If number < 0, number_chosen < 0, or number < number_chosen, COMBIN returns the #NUM! error
value.
A combination is any set or subset of items, regardless of their internal order. Combinations are distinct
from permutations, for which the internal order is significant.
The number of combinations is as follows, where number = $n$ and number_chosen = $k$:
$${n \choose k} = \frac{P_{k,n}}{k!} = \frac{n!}{k!(n-k)!}$$
Where
$$P_{k,n} = \frac{n!}{(n-k)!}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the number of combinations (with repetitions) for a given number of items.
Syntax
COMBINA(number, number_chosen)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the number of combinations (with repetitions) for a given number of items.
Remarks
If the value of either argument is outside of its constraints, COMBINA returns the #NUM! error value.
If either argument is a non-numeric value, COMBINA returns the #VALUE! error value.
The following equation is used, where $N$ is Number and $M$ is Number_chosen:
$${N+M-1 \choose N-1}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
The confidence interval is a range of values. Your sample mean, x, is at the center of this range and the range is x
± CONFIDENCE.NORM. For example, if x is the sample mean of delivery times for products ordered through the
mail, x ± CONFIDENCE.NORM is a range of population means. For any population mean, μ0, in this range, the
probability of obtaining a sample mean further from μ0 than x is greater than alpha; for any population mean,
μ0, not in this range, the probability of obtaining a sample mean further from μ0 than x is less than alpha. In
other words, assume that we use x, standard_dev, and size to construct a two-tailed test at significance level
alpha of the hypothesis that the population mean is μ0. Then we will not reject that hypothesis if μ0 is in the
confidence interval and will reject that hypothesis if μ0 is not in the confidence interval. The confidence interval
does not allow us to infer that there is probability 1 – alpha that our next package will take a delivery time that is
in the confidence interval.
Syntax
CONFIDENCE.NORM(alpha,standard_dev,size)
Parameters
T ERM DEF IN IT IO N
standard_dev The population standard deviation for the data range and is
assumed to be known.
Return value
A range of values
Remarks
If any argument is nonnumeric, CONFIDENCE.NORM returns the #VALUE! error value.
If alpha ≤ 0 or alpha ≥ 1, CONFIDENCE.NORM returns the #NUM! error value.
If standard_dev ≤ 0, CONFIDENCE.NORM returns the #NUM! error value.
If size is not an integer, it is rounded.
If size < 1, CONFIDENCE.NORM returns the #NUM! error value.
If we assume alpha equals 0.05, we need to calculate the area under the standard normal curve that
equals (1 - alpha), or 95 percent. This value is ± 1.96. The confidence interval is therefore:
$$\overline{x} \pm 1.96 \bigg( \frac{\sigma}{\sqrt{n}} \bigg) $$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
CONFIDENCE.T
8/25/2021 • 2 minutes to read
Returns the confidence interval for a population mean, using a Student's t distribution.
Syntax
CONFIDENCE.T(alpha,standard_dev,size)
Parameters
T ERM DEF IN IT IO N
standard_dev The population standard deviation for the data range and is
assumed to be known.
Return value
Returns the confidence interval for a population mean, using a Student's t distribution.
Remarks
If any argument is nonnumeric, CONFIDENCE.T returns the #VALUE! error value.
If alpha ≤ 0 or alpha ≥ 1, CONFIDENCE.T returns the #NUM! error value.
If standard_dev ≤ 0, CONFIDENCE.T returns the #NUM! error value.
If size is not an integer, it is rounded.
If size equals 1, CONFIDENCE.T returns #DIV/0! error value.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
F O RM UL A DESC RIP T IO N RESULT
Returns the exponential distribution. Use EXPON.DIST to model the time between events, such as how long an
automated bank teller takes to deliver cash. For example, you can use EXPON.DIST to determine the probability
that the process takes at most 1 minute.
Syntax
EXPON.DIST(x,lambda,cumulative)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the exponential distribution.
Remarks
If x or lambda is nonnumeric, EXPON.DIST returns the #VALUE! error value.
If x or lambda is not an integer, it is rounded.
If x < 0, EXPON.DIST returns the #NUM! error value.
If lambda ≤ 0, EXPON.DIST returns the #NUM! error value.
The equation for the probability density function is:
$$f(x; \lambda) = \lambda e^{-\lambda x}$$
The equation for the cumulative distribution function is:
$$F(x; \lambda) = 1 - e^{-\lambda x}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
GEOMEAN
8/25/2021 • 2 minutes to read
Syntax
GEOMEAN(<column>)
Parameters
T ERM DEF IN IT IO N
column The column that contains the numbers for which the
geometric mean is to be computed.
Return value
A decimal number.
Remarks
Only the numbers in the column are counted. Blanks, logical values, and text are ignored.
GEOMEAN( Table[Column] ) is equivalent to GEOMEANX( Table, Table[Column] )
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the geometric mean of the Return column in the Investment table:
= GEOMEAN( Investment[Return] )
See also
GEOMEANX function
GEOMEANX
8/25/2021 • 2 minutes to read
Returns the geometric mean of an expression evaluated for each row in a table.
To return the geometric mean of the numbers in a column, use GEOMEAN function.
Syntax
GEOMEANX(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A decimal number.
Remarks
The GEOMEANX function takes as its first argument a table, or an expression that returns a table. The
second argument is a column that contains the numbers for which you want to compute the geometric
mean, or an expression that evaluates to a column.
Only the numbers in the column are counted. Blanks, logical values, and text are ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the geometric mean of the ReturnPct column in the Investments table:
See also
GEOMEAN function
MEDIAN
8/25/2021 • 2 minutes to read
Syntax
MEDIAN(<column>)
Parameters
T ERM DEF IN IT IO N
column The column that contains the numbers for which the median
is to be computed.
Return value
A decimal number.
Remarks
Only the numbers in the column are counted. Blanks, logical values, and text are ignored.
MEDIAN( Table[Column] ) is equivalent to MEDIANX( Table, Table[Column] ).
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the median of a column named Age in a table named Customers:
= MEDIAN( Customers[Age] )
See also
MEDIANX function
MEDIANX)
8/25/2021 • 2 minutes to read
Returns the median number of an expression evaluated for each row in a table.
To return the median of numbers in a column, use MEDIAN function.
Syntax
MEDIANX(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A decimal number.
Remarks
The MEDIANX function takes as its first argument a table, or an expression that returns a table. The
second argument is a column that contains the numbers for which you want to compute the median, or
an expression that evaluates to a column.
Only the numbers in the column are counted.
Logical values and text are ignored.
MEDIANX does not ignore blanks; however, MEDIAN does ignore blanks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following computes the median age of customers who live in the USA.
See also
MEDIAN function
NORM.DIST
8/25/2021 • 2 minutes to read
Returns the normal distribution for the specified mean and standard deviation.
Syntax
NORM.DIST(X, Mean, Standard_dev, Cumulative)
Parameters
T ERM DEF IN IT IO N
Return value
The normal distribution for the specified mean and standard deviation.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { NORM.DIST(42, 40, 1.5, TRUE) }
Returns
[ VA L UE]
0.908788780274132
See also
NORM.S.DIST function
NORM.INV function
NORM.S.INV
NORM.INV
8/25/2021 • 2 minutes to read
The inverse of the normal cumulative distribution for the specified mean and standard deviation.
Syntax
NORM.INV(Probability, Mean, Standard_dev)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the inverse of the normal cumulative distribution for the specified mean and standard deviation.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { NORM.INV(0.908789, 40, 1.5) }
Returns
[ VA L UE]
42.00000200956628780274132
See also
NORM.S.INV
NORM.S.DIST function
NORM.DIST function
NORM.S.DIST
8/25/2021 • 2 minutes to read
Returns the standard normal distribution (has a mean of zero and a standard deviation of one).
Syntax
NORM.S.DIST(Z, Cumulative)
Parameters
T ERM DEF IN IT IO N
Return value
The standard normal distribution (has a mean of zero and a standard deviation of one.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { NORM.S.DIST(1.333333, TRUE) }
Returns
[ VA L UE]
0.908788725604095
See also
NORM.INV function
NORM.DIST function
NORM.S.INV
NORM.S.INV
8/25/2021 • 2 minutes to read
Returns the inverse of the standard normal cumulative distribution. The distribution has a mean of zero and a
standard deviation of one.
Syntax
NORM.S.INV(Probability)
Parameters
T ERM DEF IN IT IO N
Return value
The inverse of the standard normal cumulative distribution. The distribution has a mean of zero and a standard
deviation of one.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { NORM.S.INV(0.908789) }
Returns
[ VA L UE]
1.33333467304411
See also
NORM.INV
NORM.S.DIST function
NORM.DIST function
PERCENTILE.EXC
8/25/2021 • 2 minutes to read
Returns the k-th percentile of values in a range, where k is in the range 0..1, exclusive.
To return the percentile number of an expression evaluated for each row in a table, use PERCENTILEX.EXC
function.
Syntax
PERCENTILE.EXC(<column>, <k>)
Parameters
T ERM DEF IN IT IO N
Return value
The k-th percentile of values in a range, where k is in the range 0..1, exclusive.
Remarks
If column is empty, BLANK() is returned.
If k is zero or blank, percentile rank of 1/(n+1) returns the smallest value. If zero, it is out of range and an
error is returned.
If k is nonnumeric or outside the range 0 to 1, an error is returned.
If k is not a multiple of 1/(n + 1), PERCENTILE.EXC will interpolate to determine the value at the k-th
percentile.
PERCENTILE.EXC will interpolate when the value for the specified percentile is between two values in the
array. If it cannot interpolate for the k percentile specified, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
PERCENTILEX.EXC
PERCENTILE.INC
8/25/2021 • 2 minutes to read
Returns the k-th percentile of values in a range, where k is in the range 0..1, inclusive.
To return the percentile number of an expression evaluated for each row in a table, use PERCENTILEX.INC.
Syntax
PERCENTILE.INC(<column>, <k>)
Parameters
T ERM DEF IN IT IO N
Return value
The k-th percentile of values in a range, where k is in the range 0..1, inclusive.
Remarks
If column is empty, BLANK() is returned.
If k is zero or blank, percentile rank of 1/(n+1) returns the smallest value. If zero, it is out of range and an
error is returned.
If k is nonnumeric or outside the range 0 to 1, an error is returned.
If k is not a multiple of 1/(n + 1), PERCENTILE.INC will interpolate to determine the value at the k-th
percentile.
PERCENTILE.INC will interpolate when the value for the specified percentile is between two values in the
array. If it cannot interpolate for the k percentile specified, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
PERCENTILEX.INC
PERCENTILEX.EXC
8/25/2021 • 2 minutes to read
Returns the percentile number of an expression evaluated for each row in a table.
To return the percentile of numbers in a column, use PERCENTILE.EXC function.
Syntax
PERCENTILEX.EXC(<table>, <expression>, k)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
The percentile number of an expression evaluated for each row in a table.
Remarks
If k is zero or blank, percentile rank of 1/(n+1) returns the smallest value. If zero, it is out of range and an
error is returned.
If k is nonnumeric or outside the range 0 to 1, an error is returned.
If k is not a multiple of 1/(n + 1), PERCENTILEX.EXC will interpolate to determine the value at the k-th
percentile.
PERCENTILEX.EXC will interpolate when the value for the specified percentile is between two values in the
array. If it cannot interpolate for the k percentile specified, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
PERCENTILE.EXC
PERCENTILEX.INC
8/25/2021 • 2 minutes to read
Returns the percentile number of an expression evaluated for each row in a table.
To return the percentile of numbers in a column, use PERCENTILE.INC.
Syntax
PERCENTILEX.INC(<table>, <expression>;, k)
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
The percentile number of an expression evaluated for each row in a table.
Remarks
If k is zero or blank, percentile rank of 1/(n - 1) returns the smallest value. If zero, it is out of range and an
error is returned.
If k is nonnumeric or outside the range 0 to 1, an error is returned.
If k is not a multiple of 1/(n - 1), PERCENTILEX.EXC will interpolate to determine the value at the k-th
percentile.
PERCENTILEX.INC will interpolate when the value for the specified percentile is between two values in the
array. If it cannot interpolate for the k percentile specified, an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
PERCENTILE.INC
PERMUT
8/25/2021 • 2 minutes to read
Returns the number of permutations for a given number of objects that can be selected from number objects. A
permutation is any set or subset of objects or events where internal order is significant. Permutations are
different from combinations, for which the internal order is not significant. Use this function for lottery-style
probability calculations.
Syntax
PERMUT(number, number_chosen)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the number of permutations for a given number of objects that can be selected from number objects
Remarks
Both arguments are truncated to integers.
If number or number_chosen is nonnumeric, PERMUT returns the #VALUE! error value.
If number ≤ 0 or if number_chosen < 0, PERMUT returns the #NUM! error value.
If number < number_chosen, PERMUT returns the #NUM! error value.
The equation for the number of permutations is:
$$P_{k,n} = \frac{n!}{(n-k)!}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the following formula, permutations possible for a group of 3 objects where 2 are chosen:
= PERMUT(3,2)
Result,
6
POISSON.DIST
8/25/2021 • 2 minutes to read
Returns the Poisson distribution. A common application of the Poisson distribution is predicting the number of
events over a specific time, such as the number of cars arriving at a toll plaza in 1 minute.
Syntax
POISSON.DIST(x,mean,cumulative)
Parameters
T ERM DEF IN IT IO N
Return value
Returns the Poisson distribution.
Remarks
If x is not an integer, it is rounded.
If x or mean is nonnumeric, POISSON.DIST returns the #VALUE! error value.
If x < 0, POISSON.DIST returns the #NUM! error value.
If mean < 0, POISSON.DIST returns the #NUM! error value.
POISSON.DIST is calculated as follows.
For cumulative = FALSE:
$$\text{POISSON} = \frac{e^{-\lambda} \lambda^{x}}{x!}$$
For cumulative = TRUE:
$$\text{CUMPOISSON} = \sum^{x}_{k=0} \frac{e^{-\lambda} \lambda^{x}}{k!}$$
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
RANK.EQ
8/25/2021 • 2 minutes to read
Syntax
RANK.EQ(<value>, <columnName>[, <order>])
Parameters
T ERM DEF IN IT IO N
value Any DAX expression that returns a single scalar value whose
rank is to be found. The expression is to be evaluated exactly
once, before the function is evaluated, and it's value passed
to the argument list.
order values
Return value
A number indicating the rank of value among the numbers in columnName.
Remarks
columnName cannot refer to any column created using these functions: ADDCOLUMNS, ROW or
SUMMARIZE.I
If value is not in columnName or value is a blank, then RANK.EQ returns a blank value.
Duplicate values of value receive the same rank value; the next rank value assigned will be the rank value
plus the number of duplicate values. For example if five (5) values are tied with a rank of 11 then the next
value will receive a rank of 16 (11 + 5).
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following example creates a calculated column that ranks the values in SalesAmount_USD, from the
InternetSales_USD table, against all numbers in the same column.
= RANK.EQ(InternetSales_USD[SalesAmount_USD], InternetSales_USD[SalesAmount_USD])
Example 2
The following example ranks a subset of values against a given sample. Assume that you have a table of local
students with their performance in a specific national test and, also, you have the entire set of scores in that
national test. The following calculated column will give you the national ranking for each of the local students.
= RANK.EQ(Students[Test_Score], NationalScores[Test_Score])
RANKX
8/25/2021 • 2 minutes to read
Returns the ranking of a number in a list of numbers for each row in the table argument.
Syntax
RANKX(<table>, <expression>[, <value>[, <order>[, <ties>]]])
Parameters
table
Any DAX expression that returns a table of data over which the expression is evaluated.
expression
Any DAX expression that returns a single scalar value. The expression is evaluated for each row of table, to
generate all possible values for ranking. See the remarks section to understand the function behavior when
expression evaluates to BLANK.
value
(Optional) Any DAX expression that returns a single scalar value whose rank is to be found. See the remarks
section to understand the function's behavior when value is not found in the expression.
When the value parameter is omitted, the value of expression at the current row is used instead.
order
(Optional) A value that specifies how to rank value, low to high or high to low:
ties
(Optional) An enumeration that defines how to determine ranking when there are ties.
Skip The next rank value, after a tie, is the rank value of the tie
plus the count of tied values. For example if five (5) values
are tied with a rank of 11 then the next value will receive a
rank of 16 (11 + 5).
Dense The next rank value, after a tie, is the next rank value. For
example if five (5) values are tied with a rank of 11 then the
next value will receive a rank of 12.
Return value
The rank number of value among all possible values of expression evaluated for all rows of table numbers.
Remarks
If expression or value evaluates to BLANK it is treated as a 0 (zero) for all expressions that result in a
number, or as an empty text for all text expressions.
If value is not among all possible values of expression then RANKX temporarily adds value to the values
from expression and re-evaluates RANKX to determine the proper rank of value.
Optional arguments might be skipped by placing an empty comma (,) in the argument list, i.e.
RANKX(Inventory, [InventoryCost],,,"Dense")
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following calculated column in the Products table calculates the sales ranking for each product in the
Internet channel.
Syntax
SAMPLE(<n_value>, <table>, <orderBy_expression>, [<order>[, <orderBy_expression>, [<order>]]…])
Parameters
T ERM DEF IN IT IO N
table Any DAX expression that returns a table of data from where
to extract the 'n' sample rows.
orderBy_expression (Optional) Any scalar DAX expression where the result value
is evaluated for each row of table.
Return value
A table consisting of a sample of N rows of table or an empty table if n_value is 0 (zero) or less. If OrderBy
arguments are provided, the sample will be stable and deterministic, returning the first row, the last row, and
evenly distributed rows between them. If no ordering is specified, the sample will be random, not stable, and not
deterministic.
Remarks
If n_value is 0 (zero) or less then SAMPLE returns an empty table.
In order to avoid duplicate values in the sample, the table provided as the second argument should be
grouped by the column used for sorting.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
STDEV.S
8/25/2021 • 2 minutes to read
Syntax
STDEV.S(<ColumnName>)
Parameters
T ERM DEF IN IT IO N
Return value
A number that represents the standard deviation of a sample population.
Exceptions
Remarks
STDEV.S assumes that the column refers to a sample of the population. If your data represents the entire
population, then compute the standard deviation by using STDEV.P.
STDEV.S uses the following formula:
Ã[∑(x - x̃)2/(n-1)]
where x̃ is the average value of x for the sample population and n is the population size.
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a measure that calculates the standard deviation of the column,
SalesAmount_USD, when the table InternetSales_USD is the sample population.
= STDEV.S(InternetSales_USD[SalesAmount_USD])
STDEV.P
8/25/2021 • 2 minutes to read
Syntax
STDEV.P(<ColumnName>)
Parameters
T ERM DEF IN IT IO N
Return value
A number representing the standard deviation of the entire population.
Remarks
STDEV.P assumes that the column refers to the entire population. If your data represents a sample of the
population, then compute the standard deviation by using STDEV.S.
STDEV.P uses the following formula:
Ã[∑(x - x̃)2/n]
where x̃ is the average value of x for the entire population and n is the population size.
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a measure that calculates the standard deviation of the column,
SalesAmount_USD, when the table InternetSales_USD is the entire population.
= STDEV.P(InternetSales_USD[SalesAmount_USD])
STDEVX.S
8/25/2021 • 2 minutes to read
Syntax
STDEVX.S(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A number with the standard deviation of a sample population.
Exceptions
Remarks
STDEVX.S evaluates expression for each row of table and returns the standard deviation of expression
assuming that table refers to a sample of the population. If table represents the entire population, then
compute the standard deviation by using STDEVX.P.
STDEVX.S uses the following formula:
Ã[∑(x - x̃)2/(n-1)]
where x̃ is the average value of x for the entire population and n is the population size.
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a calculated column that estimates the standard deviation of the
unit price per product for a sample population, when the formula is used in the Product table.
= STDEVX.S(RELATEDTABLE(InternetSales_USD), InternetSales_USD[UnitPrice_USD] –
(InternetSales_USD[DiscountAmount_USD]/InternetSales_USD[OrderQuantity]))
STDEVX.P
8/25/2021 • 2 minutes to read
Syntax
STDEVX.P(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
table Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A number that represents the standard deviation of the entire population.
Remarks
STDEVX.P evaluates expression for each row of table and returns the standard deviation of expression
assuming that table refers to the entire population. If the data in table represents a sample of the
population, you should compute the standard deviation by using STDEVX.S instead.
STDEVX.P uses the following formula:
Ã[∑(x - x̃)2/n]
where x̃ is the average value of x for the entire population and n is the population size.
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a calculated column that calculates the standard deviation of the
unit price per product, when the formula is used in the Product table.
= STDEVX.P(RELATEDTABLE(InternetSales_USD), InternetSales_USD[UnitPrice_USD] –
(InternetSales_USD[DiscountAmount_USD]/InternetSales_USD[OrderQuantity]))
T.DIST
8/25/2021 • 2 minutes to read
Syntax
T.DIST(X,Deg_freedom,Cumulative)
Parameters
T ERM DEF IN IT IO N
Return value
The Student's left-tailed t-distribution.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { T.DIST(60, 1, TRUE) }
Returns,
[ VA L UE]
0.994695326367377
See also
T.DIST.2T
T.DIST.RT
T.INV
T.INV.2t
T.DIST.2T
8/25/2021 • 2 minutes to read
Syntax
T.DIST.2T(X,Deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
The two-tailed Student's t-distribution.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { T.DIST.2T(1.959999998, 60) }
Returns
[ VA L UE]
0.054644929975921
See also
T.DIST
T.DIST.RT
T.INV
T.INV.2t
T.DIST.RT
8/25/2021 • 2 minutes to read
Syntax
T.DIST.RT(X,Deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
The right-tailed Student's t-distribution.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { T.DIST.RT(1.959999998, 60) }
Returns
[ VA L UE]
0.0273224649879605
See also
T.DIST
T.DIST.2T
T.INV
T.INV.2t
T.INV
8/25/2021 • 2 minutes to read
Syntax
T.INV(Probability,Deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
The left-tailed inverse of the Student's t-distribution.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { T.INV(0.75, 2) }
Returns
[ VA L UE]
0.816496580927726
See also
T.INV.2T
T.DIST
T.DIST.2T
T.DIST.RT
T.INV.2T
8/25/2021 • 2 minutes to read
Syntax
T.INV.2T(Probability,Deg_freedom)
Parameters
T ERM DEF IN IT IO N
Return value
The two-tailed inverse of the Student's t-distribution.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
EVALUATE { T.INV.2T(0.546449, 60) }
Returns
[ VA L UE]
0.606533075825759
See also
T.INV
T.DIST
T.DIST.2T
T.DIST.RT
VAR.S
8/25/2021 • 2 minutes to read
Syntax
VAR.S(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
A number with the variance of a sample population.
Remarks
VAR.S assumes that the column refers to a sample of the population. If your data represents the entire
population, then compute the variance by using VAR.P.
VAR.S uses the following formula:
∑(x - x̃)2/(n-1)
where x̃ is the average value of x for the sample population
and n is the population size
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a measure that calculates the variance of the SalesAmount_USD
column from the InternetSales_USD for a sample population.
= VAR.S(InternetSales_USD[SalesAmount_USD])
VAR.P
8/25/2021 • 2 minutes to read
Syntax
VAR.P(<columnName>)
Parameters
T ERM DEF IN IT IO N
Return value
A number with the variance of the entire population.
Remarks
VAR.P assumes that the column refers the entire population. If your data represents a sample of the
population, then compute the variance by using VAR.S.
VAR.P uses the following formula:
∑(x - x̃)2/n
where x̃ is the average value of x for the entire population
and n is the population size
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a measure that estimates the variance of the SalesAmount_USD
column from the InternetSales_USD table, for the entire population.
= VAR.P(InternetSales_USD[SalesAmount_USD])
VARX.S
8/25/2021 • 2 minutes to read
Syntax
VARX.S(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A number that represents the variance of a sample population.
Remarks
VARX.S evaluates expression for each row of table and returns the variance of expression; on the
assumption that table refers to a sample of the population. If table represents the entire population, then
you should compute the variance by using VARX.P.
VAR.S uses the following formula:
∑(x - x̃)2/(n-1)
where x̃ is the average value of x for the sample population
and n is the population size
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a calculated column that estimates the variance of the unit price
per product for a sample population, when the formula is used in the Product table.
= VARX.S(InternetSales_USD, InternetSales_USD[UnitPrice_USD] –
(InternetSales_USD[DiscountAmount_USD]/InternetSales_USD[OrderQuantity]))
VARX.P
8/25/2021 • 2 minutes to read
Syntax
VARX.P(<table>, <expression>)
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A number with the variance of the entire population.
Remarks
VARX.P evaluates <expression> for each row of <table> and returns the variance of <expression>
assuming that <table> refers to the entire population.. If <table> represents a sample of the population,
then compute the variance by using VARX.S.
VARX.P uses the following formula:
∑(x - x̃)2/n
where x̃ is the average value of x for the entire population
and n is the population size
Blank rows are filtered out from columnName and not considered in the calculations.
An error is returned if columnName contains less than 2 non-blank rows
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the formula for a calculated column that calculates the variance of the unit price
per product, when the formula is used in the Product table
= VARX.P(InternetSales_USD, InternetSales_USD[UnitPrice_USD] –
(InternetSales_USD[DiscountAmount_USD]/InternetSales_USD[OrderQuantity]))
Table manipulation functions
8/25/2021 • 2 minutes to read
In this category
F UN C T IO N DESC RIP T IO N
DISTINCT column Returns a one-column table that contains the distinct values
from the specified column.
SUMMARIZE Returns a summary table for the requested totals over a set
of groups.
Syntax
ADDCOLUMNS(<table>, <name>, <expression>[, <name>, <expression>]…)
Parameters
T ERM DEF IN IT IO N
Return value
A table with all its original columns and the added ones.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following example returns an extended version of the Product Category table that includes total sales values
from the reseller channel and the internet sales.
ADDCOLUMNS(ProductCategory,
, "Internet Sales", SUMX(RELATEDTABLE(InternetSales_USD), InternetSales_USD[SalesAmount_USD])
, "Reseller Sales", SUMX(RELATEDTABLE(ResellerSales_USD),
ResellerSales_USD[SalesAmount_USD]))
The following table shows a preview of the data as it would be received by any function expecting to receive a
table:
Components 2 2 11205837.96
P RO DUC TC AT EGO RY [ P RO DUC TC AT EGO RY [ P RO DUC TC AT EGO RY [
P RO DUC TC AT EGO RY P RO DUC TC AT EGO RY P RO DUC TC AT EGO RY
N A M E] A LT ERN AT EK EY ] K EY ] [ IN T ERN ET SA L ES] [ RESEL L ER SA L ES]
Syntax
ADDMISSINGITEMS ( [<showAll_columnName> [, <showAll_columnName> [, … ] ] ], <table> [, <groupBy_columnName>
[, [<filterTable>] [, <groupBy_columnName> [, [<filterTable>] [, … ] ] ] ] ] ] )
Parameters
T ERM DEF IN IT IO N
Return value
A table with one or more columns.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
With SUMMARIZECOLUMNS
A table returned by SUMMARIZECOLUMNS will include only rows with values. By wrapping a
SUMMARIZECOLUMNS expression within an ADDMISSINGITEMS expression, rows containing no values are
also returned.
Example
Without ADDMISSINGITEMS, the following query:
SUMMARIZECOLUMNS(
'Sales'[CustomerId],
"Total Qty", SUM ( Sales[TotalQty] )
)
Returns,
C USTO M ERID TOTA LQT Y
A 5
B 3
C 3
E 2
EVALUATE
ADMISSINGITEMS (
'Sales'[CustomerId],
SUMMARIZECOLUMNS(
'Sales'[CustomerId],
"Total Qty", SUM ( Sales[TotalQty] )
),
'Sales'[CustomerId]
)
Returns,
A 5
B 3
C 3
E 2
F
CROSSJOIN
8/25/2021 • 2 minutes to read
Returns a table that contains the Cartesian product of all rows from all tables in the arguments. The columns in
the new table are all the columns in all the argument tables.
Syntax
CROSSJOIN(<table>, <table>[, <table>]…)
Parameters
T ERM DEF IN IT IO N
Return value
A table that contains the Cartesian product of all rows from all tables in the arguments.
Remarks
Column names from table arguments must all be different in all tables or an error is returned.
The total number of rows returned by CROSSJOIN() is equal to the product of the number of rows from
all tables in the arguments; also, the total number of columns in the result table is the sum of the number
of columns in all tables. For example, if TableA has rA rows and cA columns, and TableB has rB rows
and cB columns, and TableC has rC rows and cC column; then, the resulting table has rA × rb × rC
rows and cA + cB + cC columns.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example shows the results of applying CROSSJOIN() to two tables: Colors and Stationer y .
The table Colors contains colors and patterns:
C O LO R PAT T ERN
Blue Crosshatch
serif embossed
sans-serif engraved
When the above expression is used wherever a table expression is expected, the results of the expression would
be as follows:
Returns a set of rows from the table argument of a GROUPBY expression that belong to the current row of the
GROUPBY result.
Syntax
CURRENTGROUP ( )
Parameters
None
Return value
The rows in the table argument of the GROUPBY function corresponding to one group of values of the
groupBy_columnName arguments.
Remarks
This function can only be used within a GROUPBY expression.
This function takes no arguments and is only supported as the first argument to one of the following
aggregation functions: AVERAGEX, COUNTAX, COUNTX, GEOMEANX, MAXX, MINX, PRODUCTX,
STDEVX.S, STDEVX.P, SUMX, VARX.S, VARX.P.
Example
See GROUPBY.
DATATABLE
8/25/2021 • 2 minutes to read
Syntax
DATATABLE (ColumnName1, DataType1, ColumnName2, DataType2..., {{Value1, Value2...}, {ValueN,
ValueN+1...}...})
Parameters
T ERM DEF IN IT IO N
For example,
{ {values in row1}, {values in row2}, {values in row3}, etc. }
Where {values in row1} is a comma delimited set of constant
expressions, namely a combination of constants, combined
with a handful of basic functions including DATE, TIME, and
BLANK, as well as a plus operator between DATE and TIME
and a unary minus operator so that negative values can be
expressed.
Return value
A table declaring an inline set of values.
Remarks
Unlike DATATABLE, Table Constructor allows any scalar expressions as input values.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
= DataTable("Name", STRING,
"Region", STRING
,{
{" User1","East"},
{" User2","East"},
{" User3","West"},
{" User4","West"},
{" User4","East"}
}
)
DETAILROWS
8/25/2021 • 2 minutes to read
Evaluates a Detail Rows Expression defined for a measure and returns the data.
Syntax
DETAILROWS([Measure])
Parameters
T ERM DEF IN IT IO N
Return value
A table with the data returned by the Detail Rows Expression. If no Detail Rows Expression is defined, the data for
the table containing the measure is returned.
DISTINCT (column)
8/25/2021 • 2 minutes to read
Returns a one-column table that contains the distinct values from the specified column. In other words, duplicate
values are removed and only unique values are returned.
NOTE
This function cannot be used to Return values into a cell or column on a worksheet; rather, you nest the DISTINCT
function within a formula, to get a list of distinct values that can be passed to another function and then counted,
summed, or used for other operations.
Syntax
DISTINCT(<column>)
Parameters
T ERM DEF IN IT IO N
column The column from which unique values are to be returned. Or,
an expression that returns a column.
Return value
A column of unique values.
Remarks
The results of DISTINCT are affected by the current filter context. For example, if you use the formula in
the following example to create a measure, the results would change whenever the table was filtered to
show only a particular region or a time period.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Related functions
There is another version of the DISTINCT function, DISTINCT (table), that returns a table by removing duplicate
rows from another table or expression..
The VALUES function is similar to DISTINCT; it can also be used to return a list of unique values, and generally
will return exactly the same results as DISTINCT. However, in some context VALUES will return one additional
special value. For more information, see VALUES function.
Example
The following formula counts the number of unique customers who have generated orders over the internet
channel. The table that follows illustrates the possible results when the formula is added to a report.
= COUNTROWS(DISTINCT(InternetSales_USD[CustomerKey]))
You cannot paste the list of values that DISTINCT returns directly into a column. Instead, you pass the results of
the DISTINCT function to another function that counts, filters, or aggregates values by using the list. To make the
example as simple as possible, here the table of distinct values has been passed to the COUNTROWS function.
Also, note that the results are not additive. That is to say, the total number of unique customers in 2007 is not
the sum of unique customers of Accessories, Bikes and Clothing for that year. The reason is that a customer can
be counted in multiple groups.
See also
Filter functions
FILTER function
RELATED function
VALUES function
DISTINCT (table)
8/25/2021 • 2 minutes to read
Syntax
DISTINCT(<table>)
Parameters
T ERM DEF IN IT IO N
table The table from which unique rows are to be returned. The
table can also be an expression that results in a table.
Return value
A table containing only distinct rows.
Related functions
There is another version of the DISTINCT function, DISTINCT (column), that takes a column name as input
parameter.
Example
The following query:
Returns table:
[ VA L UE1] [ VA L UE2]
1 A
2 B
See also
Filter functions
DISTINCT (column)
FILTER function
RELATED function
VALUES function
EXCEPT
8/25/2021 • 2 minutes to read
Returns the rows of one table which do not appear in another table.
Syntax
EXCEPT(<table_expression1>, <table_expression2>
Parameters
T ERM DEF IN IT IO N
Return value
A table that contains the rows of one table minus all the rows of another table.
Remarks
If a row appears at all in both tables, it and its duplicates are not present in the result set. If a row appears
in only table_expression1, it and its duplicates will appear in the result set.
The column names will match the column names in table_expression1.
The returned table has lineage based on the columns in table_expression1 , regardless of the lineage of
the columns in the second table. For example, if the first column of first table_expression has lineage to
the base column C1 in the model, the Except will reduce the rows based on the availability of values in the
first column of second table_expression and keep the lineage on base column C1 intact.
The two tables must have the same number of columns.
Columns are compared based on positioning, and data comparison with no type coercion.
The set of rows returned depends on the order of the two expressions.
The returned table does not include columns from tables related to table_expression1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
States1
STAT E
B
STAT E
States2
STAT E
Except(States1, States2)
STAT E
Except(States2, States1)
STAT E
E
FILTERS
8/25/2021 • 2 minutes to read
Syntax
FILTERS(<columnName>)
Parameters
T ERM DESC RIP T IO N
Return value
The values that are directly applied as filters to columnName.
Remarks
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
The following example shows how to determine the number of direct filters a column has.
= COUNTROWS(FILTERS(ResellerSales_USD[ProductKey]))
This example lets you know how many direct filters on ResellerSales_USD[ProductKey] have been applied to the
context where the expression is being evaluated.
GENERATE
8/25/2021 • 2 minutes to read
Returns a table with the Cartesian product between each row in table1 and the table that results from evaluating
table2 in the context of the current row from table1.
Syntax
GENERATE(<table1>, <table2>)
Parameters
T ERM DEF IN IT IO N
Return value
A table with the Cartesian product between each row in table1 and the table that results from evaluating table2
in the context of the current row from table1
Remarks
If the evaluation of table2 for the current row in table1 returns an empty table, then the result table will
not contain the current row from table1. This is different than GENERATEALL() where the current row
from table1 will be included in the results and columns corresponding to table2 will have null values for
that row.
All column names from table1 and table2 must be different or an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the following example the user wants a summary table of the sales by Region and Product Category for the
Resellers channel, like the following table:
GENERATE(
SUMMARIZE(SalesTerritory, SalesTerritory[SalesTerritoryGroup])
,SUMMARIZE(ProductCategory
, [ProductCategoryName]
, "Reseller Sales", SUMX(RELATEDTABLE(ResellerSales_USD), ResellerSales_USD[SalesAmount_USD])
)
)
North America
Europe
Pacific
NA
Bikes $ 63,084,675.04
Components $ 11,205,837.96
P RO DUC TC AT EGO RY [ P RO DUC TC AT EGO RY N A M E] [ RESEL L ER SA L ES]
Clothing $ 1,669,943.27
Accessories $ 534,301.99
3. However, when you take the above table and evaluate it under the context of each row from the territory
groups table, you obtain different results for each territory.
GENERATEALL
8/25/2021 • 2 minutes to read
Returns a table with the Cartesian product between each row in table1 and the table that results from evaluating
table2 in the context of the current row from table1.
Syntax
GENERATEALL(<table1>, <table2>)
Parameters
T ERM DEF IN IT IO N
Return value
A table with the Cartesian product between each row in table1 and the table that results from evaluating table2
in the context of the current row from table1
Remarks
If the evaluation of table2 for the current row in table1 returns an empty table, then the current row from
table1 will be included in the results and columns corresponding to table2 will have null values for that
row. This is different than GENERATE() where the current row from table1 will not be included in the
results.
All column names from table1 and table2 must be different or an error is returned.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the following example, the user wants a summary table of the sales by Region and Product Category for the
Resellers channel, like the following table:
NA Accessories
NA Bikes
NA Clothing
NA Components
GENERATEALL(
SUMMARIZE(SalesTerritory, SalesTerritory[SalesTerritoryGroup])
,SUMMARIZE(ProductCategory
, [ProductCategoryName]
, "Reseller Sales", SUMX(RELATEDTABLE(ResellerSales_USD), ResellerSales_USD[SalesAmount_USD])
)
)
1. The first SUMMARIZE produces a table of territory groups, where each row is a territory group, like those
listed below:
North America
Europe
Pacific
NA
2. The second SUMMARIZE produces a table of Product Category groups with the Reseller sales for each
group, as shown below:
P RO DUC TC AT EGO RY [ P RO DUC TC AT EGO RY N A M E] [ RESEL L ER SA L ES]
Bikes $ 63,084,675.04
Components $ 11,205,837.96
Clothing $ 1,669,943.27
Accessories $ 534,301.99
3. However, when you take the above table and evaluate the table under the context of each row from the
territory groups table, you obtain different results for each territory.
GENERATESERIES
8/25/2021 • 2 minutes to read
Returns a single column table containing the values of an arithmetic series, that is, a sequence of values in which
each differs from the preceding by a constant quantity. The name of the column returned is Value.
Syntax
GENERATESERIES(<startValue>, <endValue>[, <incrementValue>])
Parameters
T ERM DEF IN IT IO N
Return value
A single column table containing the values of an arithmetic series. The name of the column is Value.
Remarks
When startValue is less than endValue, an empty table is returned.
incrementValue must be a positive value.
The sequence stops at the last value that is less than or equal to endValue.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example 1
The following DAX query:
EVALUATE GENERATESERIES(1, 5)
[ VA L UE]
2
[ VA L UE]
Example 2
The following DAX query:
[ VA L UE]
1.2
1.6
2.4
Example 3
The following DAX query:
[ VA L UE]
10
10.5
11
11.5
12
GROUPBY
8/25/2021 • 2 minutes to read
The GROUPBY function is similar to the SUMMARIZE function. However, GROUPBY does not do an implicit
CALCULATE for any extension columns that it adds. GROUPBY permits a new function, CURRENTGROUP, to be
used inside aggregation functions in the extension columns that it adds. GROUPBY is used to perform multiple
aggregations in a single table scan.
Syntax
GROUPBY (<table> [, <groupBy_columnName> [, <groupBy_columnName> [, …]]] [, <name>, <expression> [, <name>,
<expression> [, …]]])
Parameters
T ERM DEF IN IT IO N
name The name given to a new column that is being added to the
list of GroupBy columns, enclosed in double quotes.
Return value
A table with the selected columns for the groupBy_columnName arguments and the extension columns
designated by the name arguments.
Remarks
The GROUPBY function does the following:
1. Start with the specified table (and all related tables in the "to-one" direction).
2. Create a grouping using all of the GroupBy columns (which are required to exist in the table from
step #1.).
3. Each group is one row in the result, but represents a set of rows in the original table.
4. For each group, evaluate the extension columns being added. Unlike the SUMMARIZE function, an
implied CALCULATE is not performed, and the group isn't placed into the filter context.
Each column for which you define a name must have a corresponding expression; otherwise, an error is
returned. The first argument, name, defines the name of the column in the results. The second argument,
expression, defines the calculation performed to obtain the value for each row in that column.
groupBy_columnName must be either in table or in a related table.
Each name must be enclosed in double quotation marks.
The function groups a selected set of rows into a set of summary rows by the values of one or more
groupBy_columnName columns. One row is returned for each group.
GROUPBY is primarily used to perform aggregations over intermediate results from DAX table
expressions. For efficient aggregations over physical tables in the model, consider using
SUMMARIZECOLUMNS or SUMMARIZE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
With CURRENTGROUP
CURRENTGROUP can only be used in an expression that defines an extension column within the GROUPBY
function. In-effect, CURRENTGROUP returns a set of rows from the table argument of GROUPBY that belong to
the current row of the GROUPBY result. The CURRENTGROUP function takes no arguments and is only
supported as the first argument to one of the following aggregation functions: AVERAGEX, COUNTAX, COUNTX,
GEOMEANX, MAXX, MINX, PRODUCTX, STDEVX.S, STDEVX.P, SUMX, VARX.S, VARX.P.
Example
The following example first calculates the total sales grouped by country and product category over physical
tables by using the SUMMARIZECOLUMNS function. It then uses the GROUPBY function to scan the
intermediate result from the first step to find the maximum sales in each country across the product categories.
DEFINE
VAR SalesByCountryAndCategory =
SUMMARIZECOLUMNS(
Geography[Country],
Product[Category],
"Total Sales", SUMX(Sales, Sales[Price] * Sales[Qty])
)
EVALUATE
GROUPBY(
SalesByCountryAndCategory,
Geography[Country],
"Max Sales", MAXX(CURRENTGROUP(), [Total Sales])
)
See also
SUMMARIZE function
SUMMARIZECOLUMNS function
IGNORE
8/25/2021 • 2 minutes to read
Modifies the behavior of the SUMMARIZECOLUMNS function by omitting specific expressions from the
BLANK/NULL evaluation. Rows for which all expressions not using IGNORE return BLANK/NULL will be
excluded independent of whether the expressions which do use IGNORE evaluate to BLANK/NULL or not. This
function can only be used within a SUMMARIZECOLUMNS expression.
Syntax
IGNORE(<expression>)
With SUMMARIZECOLUMNS,
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single value (not a table).
Return value
The function does not return a value.
Remarks
IGNORE can only be used as an expression argument to SUMMARIZECOLUMNS.
Example
See SUMMARIZECOLUMNS.
INTERSECT
8/25/2021 • 2 minutes to read
Syntax
INTERSECT(<table_expression1>, <table_expression2>)
Parameters
T ERM DEF IN IT IO N
Return value
A table that contains all the rows in table_expression1 that are also in table_expression2
Exceptions
Remarks
Intersect is not commutative. In general, Intersect(T1, T2) will have a different result set than Intersect(T2,
T1).
Duplicate rows are retained. If a row appears in table_expression1 and table_expression2, it and all
duplicates in table_expression_1 are included in the result set.
The column names will match the column names in table_expression1.
The returned table has lineage based on the columns in table_expression1 , regardless of the lineage of
the columns in the second table. For example, if the first column of first table_expression has lineage to
the base column C1 in the model, the intersect will reduce the rows based on the intersect on first column
of second table_expression and keep the lineage on base column C1 intact.
Columns are compared based on positioning, and data comparison with no type coercion.
The returned table does not include columns from tables related to table_expression1.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
States1
STAT E
A
STAT E
States2
STAT E
Intersect(States1, States2)
STAT E
Intersect(States2, States1)
STAT E
STAT E
D
NATURALINNERJOIN
8/25/2021 • 2 minutes to read
Performs an inner join of a table with another table. The tables are joined on common columns (by name) in the
two tables. If the two tables have no common column names, an error is returned.
Syntax
NATURALINNERJOIN(<leftJoinTable>, <rightJoinTable>)
Parameters
T ERM DEF IN IT IO N
leftJoinTable A table expression defining the table on the left side of the
join.
rightJoinTable A table expression defining the table on the right side of the
join.
Return value
A table which includes only rows for which the values in the common columns specified are present in both
tables. The table returned will have the common columns from the left table and other columns from both the
tables.
Remarks
There is no sort order guarantee for the results.
Columns being joined on must have the same data type in both tables.
Only columns from the same source table (have the same lineage) are joined on. For example,
Products[ProductID], WebSales[ProductdID], StoreSales[ProductdID] with many-to-one relationships
between WebSales and StoreSales and the Products table based on the ProductID column, WebSales and
StoreSales tables are joined on [ProductID].
Strict comparison semantics are used during join. There is no type coercion; for example, 1 does not equal
1.0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
NATURALLEFTOUTERJOIN
8/25/2021 • 2 minutes to read
Performs an inner join of a table with another table. The tables are joined on common columns (by name) in the
two tables. If the two tables have no common column names, an error is returned.
Syntax
NATURALLEFTOUTERJOIN(<leftJoinTable>, <rightJoinTable>)
Parameters
T ERM DEF IN IT IO N
leftJoinTable A table expression defining the table on the left side of the
join.
rightJoinTable A table expression defining the table on the right side of the
join.
Return value
A table which includes only rows from rightJoinTable for which the values in the common columns specified are
also present in leftJoinTable. The table returned will have the common columns from the left table and the other
columns from both the tables.
Remarks
There is no sort order guarantee for the results.
Columns being joined on must have the same data type in both tables.
Only columns from the same source table (have the same lineage) are joined on. For example,
Products[ProductID], WebSales[ProductdID], StoreSales[ProductdID] with many-to-one relationships
between WebSales and StoreSales and the Products table based on the ProductID column, WebSales and
StoreSales tables are joined on [ProductID].
Strict comparison semantics are used during join. There is no type coercion; for example, 1 does not equal
1.0.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
ROLLUP
8/25/2021 • 2 minutes to read
Modifies the behavior of the SUMMARIZE function by adding rollup rows to the result on columns defined by
the groupBy_columnName parameter. This function can only be used within a SUMMARIZE expression.
Syntax
ROLLUP ( <groupBy_columnName> [, <groupBy_columnName> [, … ] ] )
With SUMMARIZE,
Parameters
T ERM DEF IN IT IO N
Return value
This function does not return a value. It only specifies the set of columns to be subtotaled.
Remarks
This function can only be used within a SUMMARIZE expression.
Example
See SUMMARIZE.
ROLLUPADDISSUBTOTAL
8/25/2021 • 2 minutes to read
Modifies the behavior of the SUMMARIZECOLUMNS function by adding rollup/subtotal rows to the result based
on the groupBy_columnName columns. This function can only be used within a SUMMARIZECOLUMNS
expression.
Syntax
ROLLUPADDISSUBTOTAL ( [<grandtotalFilter>], <groupBy_columnName>, <name> [, [<groupLevelFilter>] [,
<groupBy_columnName>, <name> [, [<groupLevelFilter>] [, … ] ] ] ] )
Parameters
T ERM DEF IN IT IO N
Return value
The function does not return a value.
Remarks
None
Example
See SUMMARIZECOLUMNS.
ROLLUPGROUP
8/25/2021 • 2 minutes to read
Modifies the behavior of the SUMMARIZE and SUMMARIZECOLUMNS functions by adding rollup rows to the
result on columns defined by the the groupBy_columnName parameter. This function can only be used within a
SUMMARIZE or SUMMARIZECOLUMNS expression.
Syntax
ROLLUPGROUP ( <groupBy_columnName> [, <groupBy_columnName> [, … ] ] )
Parameters
T ERM DEF IN IT IO N
Return value
This function does not return a value. It marks a set of columns to be treated as a single group during
subtotaling by ROLLUP or ROLLUPADDISSUBTOTAL.
Remarks
ROLLUPGROUP can only be used as a groupBy_columnName argument to ROLLUP, ROLLUPADDISSUBTOTAL,
or ROLLUPISSUBTOTAL.
Example
See SUMMARIZE and SUMMARIZECOLUMNS.
ROLLUPISSUBTOTAL
8/25/2021 • 2 minutes to read
Pairs rollup groups with the column added by ROLLUPADDISSUBTOTAL. This function can only be used within an
ADDMISSINGITEMS expression.
Syntax
ROLLUPISSUBTOTAL ( [<grandTotalFilter>], <groupBy_columnName>, <isSubtotal_columnName> [,
[<groupLevelFilter>] [, <groupBy_columnName>, <isSubtotal_columnName> [, [<groupLevelFilter>] [, … ] ] ] ] )
Parameters
T ERM DEF IN IT IO N
Return value
None
Remarks
This function can only be used within an ADDMISSINGITEMS expression.
ROW function
8/25/2021 • 2 minutes to read
Returns a table with a single row containing values that result from the expressions given to each column.
Syntax
ROW(<name>, <expression>[[,<name>, <expression>]…])
Parameters
T ERM DEF IN IT IO N
Return value
A single row table
Remarks
Arguments must always come in pairs of name and expression.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns a single row table with the total sales for internet and resellers channels.
Syntax
SELECTCOLUMNS(<table>, <name>, <scalar_expression> [, <name>, <scalar_expression>]…)
Parameters
T ERM DEF IN IT IO N
Return value
A table with the same number of rows as the table specified as the first argument. The returned table has one
column for each pair of <name>, <scalar_expression> arguments, and each expression is evaluated in the
context of a row from the specified <table> argument.
Remarks
SELECTCOLUMNS has the same signature as ADDCOLUMNS, and has the same behavior except that instead of
starting with the <table> specified, SELECTCOLUMNS starts with an empty table before adding columns.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-level
security (RLS) rules.
Example
For the following table named Info :
C O UN T RY STAT E C O UN T TOTA L
IND JK 20 800
IND MH 25 1000
IND WB 10 900
USA CA 5 500
USA WA 10 900
SELECTCOLUMNS(Info, "StateCountry", [State]&", "&[Country])
Returns,
STAT EC O UN T RY
IND, JK
IND, MH
IND, WB
USA, CA
USA, WA
SUBSTITUTEWITHINDEX
8/25/2021 • 2 minutes to read
Returns a table which represents a left semijoin of the two tables supplied as arguments. The semijoin is
performed by using common columns, determined by common column names and common data type . The
columns being joined on are replaced with a single column in the returned table which is of type integer and
contains an index. The index is a reference into the right join table given a specified sort order.
Columns in the right/second table supplied which do not exist in the left/first table supplied are not included in
the returned table and are not used to join on.
The index starts at 0 (0-based) and is incremented by one for each additional row in the right/second join table
supplied. The index is based on the sort order specified for the right/second join table.
Syntax
SUBSTITUTEWITHINDEX(<table>, <indexColumnName>, <indexColumnsTable>, [<orderBy_expression>, [<order>][,
<orderBy_expression>, [<order>]]…])
Parameters
T ERM DEF IN IT IO N
indexColumnName A string which specifies the name of the index column which
is replacing all the common columns in the two tables
supplied as arguments to this function.
indexColumnsTable The second table for the left semijoin. This is the table on the
right side of the left semijoin. Only values present in this
table will be returned by the function. Also, the columns of
this table (based on column names) will be replaced with a
single index column in the table returned by this function.
orderBy_expression Any DAX expression where the result value is used to specify
the desired sort order of the indexColumnsTable table for
generating correct index values. The sort order specified for
the indexColumnsTable table defines the index of each row in
the table and that index is used in the table returned to
represent combinations of values in the indexColumnsTable
as they appear in the table supplied as the first argument to
this function.
T ERM DEF IN IT IO N
Return value
A table which includes only those values present in the indexColumnsTable table and which has an index column
instead of all columns present (by name) in the indexColumnsTable table.
Remarks
This function does not guarantee any result sort order.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
SUMMARIZE
8/25/2021 • 4 minutes to read
Returns a summary table for the requested totals over a set of groups.
Syntax
SUMMARIZE (<table>, <groupBy_columnName>[, <groupBy_columnName>]…[, <name>, <expression>]…)
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
Return value
A table with the selected columns for the groupBy_columnName arguments and the summarized columns
designed by the name arguments.
Remarks
Each column for which you define a name must have a corresponding expression; otherwise, an error is
returned. The first argument, name, defines the name of the column in the results. The second argument,
expression, defines the calculation performed to obtain the value for each row in that column.
groupBy_columnName must be either in table or in a related table to table.
Each name must be enclosed in double quotation marks.
The function groups a selected set of rows into a set of summary rows by the values of one or more
groupBy_columnName columns. One row is returned for each group.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns a summary of the reseller sales grouped around the calendar year and the
product category name, this result table allows you to do analysis over the reseller sales by year and product
category.
SUMMARIZE(ResellerSales_USD
, DateTime[CalendarYear]
, ProductCategory[ProductCategoryName]
, "Sales Amount (USD)", SUM(ResellerSales_USD[SalesAmount_USD])
, "Discount Amount (USD)", SUM(ResellerSales_USD[DiscountAmount])
)
The following table shows a preview of the data as it would be received by any function expecting to receive a
table:
With ROLLUP
The addition of the ROLLUP syntax modifies the behavior of the SUMMARIZE function by adding rollup rows to
the result on the groupBy_columnName columns. ROLLUP can only be used within a SUMMARIZE expression.
Example
The following example adds rollup rows to the Group-By columns of the SUMMARIZE function call:
SUMMARIZE(ResellerSales_USD
, ROLLUP( DateTime[CalendarYear], ProductCategory[ProductCategoryName])
, "Sales Amount (USD)", SUM(ResellerSales_USD[SalesAmount_USD])
, "Discount Amount (USD)", SUM(ResellerSales_USD[DiscountAmount])
)
76494758.25 527507.9262
With ROLLUPGROUP
The addition of ROLLUPGROUP inside a ROLLUP syntax can be used to prevent partial subtotals in rollup rows.
ROLLUPGROUP can only be used within a ROLLUP, ROLLUPADDISSUBTOTAL, or ROLLUPISSUBTOTAL
expression.
Example
The following example shows only the grand total of all years and categories without the subtotal of each year
with all categories:
SUMMARIZE(ResellerSales_USD
, ROLLUP(ROLLUPGROUP( DateTime[CalendarYear], ProductCategory[ProductCategoryName]))
, "Sales Amount (USD)", SUM(ResellerSales_USD[SalesAmount_USD])
, "Discount Amount (USD)", SUM(ResellerSales_USD[DiscountAmount])
)
76494758.25 527507.9262
DAT ET IM E[ C A L EN DA RY EA R P RO DUC TC AT EGO RY [ P RO D [ DISC O UN T A M O UN T
] UC TC AT EGO RY N A M E] [ SA L ES A M O UN T ( USD) ] ( USD) ]
With ISSUBTOTAL
With ISSUBTOTAL, you can create another column in the SUMMARIZE expression that returns True if the row
contains subtotal values for the column given as argument to ISSUBTOTAL, otherwise returns False. ISSUBTOTAL
can only be used within a SUMMARIZE expression.
Example
The following sample generates an ISSUBTOTAL column for each of the ROLLUP columns in the given
SUMMARIZE function call:
SUMMARIZE(ResellerSales_USD
, ROLLUP( DateTime[CalendarYear], ProductCategory[ProductCategoryName])
, "Sales Amount (USD)", SUM(ResellerSales_USD[SalesAmount_USD])
, "Discount Amount (USD)", SUM(ResellerSales_USD[DiscountAmount])
, "Is Sub Total for DateTimeCalendarYear", ISSUBTOTAL(DateTime[CalendarYear])
, "Is Sub Total for ProductCategoryName", ISSUBTOTAL(ProductCategory[ProductCategoryName])
)
FALSE FALSE
FALSE TRUE
See also
SUMMARIZECOLUMNS
SUMMARIZECOLUMNS
8/25/2021 • 5 minutes to read
Syntax
SUMMARIZECOLUMNS( <groupBy_columnName> [, < groupBy_columnName >]…, [<filterTable>]…[, <name>, <expression>]
…)
Parameters
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single value (not a table).
Return value
A table which includes combinations of values from the supplied columns based on the grouping specified. Only
rows for which at least one of the supplied expressions return a non-blank value are included in the table
returned. If all expressions evaluate to BLANK/NULL for a row, that row is not included in the table returned.
Remarks
This function does not guarantee any sort order for the results.
A column cannot be specified more than once in the groupBy_columnName parameter. For example, the
following formula is invalid.
SUMMARIZECOLUMNS( Sales[StoreId], Sales[StoreId] )
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Filter context
Consider the following query:
SUMMARIZECOLUMNS (
'Sales Territory'[Category],
FILTER('Customer', 'Customer' [First Name] = "Alicia")
)
In this query, without a measure the groupBy columns do not contain any columns from the FILTER expression
(for example, from Customer table). The filter is not applied to the groupBy columns. The Sales Territory and
Customer tables may be indirectly related through the Reseller sales fact table. Since they're not directly related,
the filter expression is a no-op and the groupBy columns are not impacted.
However, with this query:
SUMMARIZECOLUMNS (
'Sales Territory'[Category], 'Customer' [Education],
FILTER('Customer', 'Customer'[First Name] = "Alicia")
)
The groupBy columns contain a column which is impacted by the filter and that filter is applied to the groupBy
results.
With IGNORE
The IGNORE syntax can be used to modify the behavior of the SUMMARIZECOLUMNS function by omitting
specific expressions from the BLANK/NULL evaluation. Rows for which all expressions not using IGNORE return
BLANK/NULL will be excluded independent of whether the expressions which do use IGNORE evaluate to
BLANK/NULL or not. IGNORE can only be used within a SUMMARIZECOLUMNS expression.
Example
SUMMARIZECOLUMNS(
Sales[CustomerId], "Total Qty",
IGNORE( SUM( Sales[Qty] ) ),
"BlankIfTotalQtyIsNot3", IF( SUM( Sales[Qty] )=3, 3 )
)
This rolls up the Sales[CustomerId] column, creating a subtotal for all customers in the given grouping. Without
IGNORE, the result is:
A 5
B 3 3
C 3 3
With IGNORE,
B 3 3
C 3 3
Even though both expressions return blank for some rows, they're included since there are no unignored
expressions which return blank.
A 5
With NONVISUAL
The NONVISUAL function marks a value filter in SUMMARIZECOLUMNS function as not affecting measure
values, but only applying to groupBy columns. NONVISUAL can only be used within a SUMMARIZECOLUMNS
expression.
Example
DEFINE
MEASURE FactInternetSales[Sales] = SUM(FactInternetSales[Sales Amount])
EVALUATE
SUMMARIZECOLUMNS
(
DimDate[CalendarYear],
NONVISUAL(TREATAS({2007, 2008}, DimDate[CalendarYear])),
"Sales", [Sales],
"Visual Total Sales", CALCULATE([Sales], ALLSELECTED(DimDate[CalendarYear]))
)
ORDER BY [CalendarYear]
Returns the result where [Visual Total Sales] is the total across all years:
Returns the result where [Visual Total Sales] is the total across the two selected years:
With ROLLUPADDISSUBTOTAL
The addition of the ROLLUPADDISSUBTOTAL syntax modifies the behavior of the SUMMARIZECOLUMNS
function by adding rollup/subtotal rows to the result based on the groupBy_columnName columns.
ROLLUPADDISSUBTOTAL can only be used within a SUMMARIZECOLUMNS expression.
Example with single subtotal
DEFINE
VAR vCategoryFilter =
TREATAS({"Accessories", "Clothing"}, Product[Category])
VAR vSubcategoryFilter =
TREATAS({"Bike Racks", "Mountain Bikes"}, Product[Subcategory])
EVALUATE
SUMMARIZECOLUMNS
(
ROLLUPADDISSUBTOTAL
(
Product[Category], "IsCategorySubtotal", vCategoryFilter,
Product[Subcategory], "IsSubcategorySubtotal", vSubcategoryFilter
),
"Total Qty", SUM(Sales[Qty])
)
ORDER BY
[IsCategorySubtotal] DESC, [Category],
[IsSubcategorySubtotal] DESC, [Subcategory]
SUMMARIZECOUMNS (
Regions[State], ROLLUPADDISSUBTOTAL ( Sales[CustomerId], "IsCustomerSubtotal" ),
ROLLUPADDISSUBTOTAL ( Sales[Date], "IsDateSubtotal"), "Total Qty", SUM( Sales[Qty] )
)
Sales is grouped by state, by customer, by date, with subtotals for 1. Sales by state, by date 2. Sales by State, by
Customer 3. Rolled up on both customer and date leading to sales by state.
Returns the following table,
A FALSE WA 5 7/10/2014
B FALSE WA 1 7/10/2014
B FALSE WA 2 7/11/2014
C FALSE OR 2 7/10/2014
C FALSE OR 1 7/11/2014
TRUE WA 6 7/10/2014
TRUE WA 2 7/11/2014
TRUE OR 2 7/10/2014
TRUE OR 1 7/11/2014
A FALSE WA 5 TRUE
B FALSE WA 3 TRUE
C FALSE OR 3 TRUE
TRUE WA 8 TRUE
TRUE OR 3 TRUE
With ROLLUPGROUP
Like with the SUMMARIZE function, ROLLUPGROUP can be used together with ROLLUPADDISSUBTOTAL to
specify which summary groups/granularities (subtotals) to include, reducing the number of subtotal rows
returned. ROLLUPGROUP can only be used within a SUMMARIZECOLUMNS or SUMMARIZE expression.
Example with multiple subtotals
SUMMARIZECOLUMNS(
ROLLUPADDISSUBTOTAL( Sales[CustomerId], "IsCustomerSubtotal" ),
ROLLUPADDISSUBTOTAL(ROLLUPGROUP(Regions[City], Regions[State]), "IsCityStateSubtotal"),"Total Qty", SUM(
Sales[Qty] )
)
Still grouped by City and State, but rolled together when reporting a subtotal returns the following table,
A FALSE 5 FALSE
B FALSE 3 TRUE
C FALSE 3 TRUE
TRUE 11 TRUE
See also
SUMMARIZE
Table constructor
8/25/2021 • 2 minutes to read
Syntax
{ <scalarExpr1>, <scalarExpr2>, … }
{ ( <scalarExpr1>, <scalarExpr2>, … ), ( <scalarExpr1>, <scalarExpr2>, … ), … }
Parameters
T ERM DEF IN IT IO N
Return value
A table of one or more columns. When there is only one column, the name of the column is Value. When there
are N columns where N > 1, the names of the columns from left to right are Value1, Value2, …, ValueN.
Remarks
The first syntax returns a table of a single column. The second syntax returns a table of one or more
columns.
The number of scalar expressions must be the same for all rows.
When the data types of the values for a column are different in different rows, all values are converted to
a common data type.
Example 1
The following DAX queries:
EVALUATE { 1, 2, 3 }
and
[ VA L UE]
2
[ VA L UE]
Example 2
The following DAX query:
EVALUATE
{
(1.5, DATE(2017, 1, 1), CURRENCY(199.99), "A"),
(2.5, DATE(2017, 1, 2), CURRENCY(249.99), "B"),
(3.5, DATE(2017, 1, 3), CURRENCY(299.99), "C")
}
Returns,
Example 3
The following DAX query:
[ VA L UE]
1/1/2017
TRUE
A
TOPN
8/25/2021 • 2 minutes to read
Syntax
TOPN(<n_value>, <table>, <orderBy_expression>, [<order>[, <orderBy_expression>, [<order>]]…])
Parameters
The number of rows to return. It is any DAX expression that returns a single scalar value, where the expression is
to be evaluated multiple times (for each row/context).
See the remarks section to understand when the number of rows returned could possible be larger than
n_value.
See the remarks section to understand when an empty table is returned.
table Any DAX expression that returns a table of data from where to extract the top 'n' rows.
orderBy_expression
Any DAX expression where the result value is used to sort the table and it is evaluated for each row of table.
order (Optional) A value that specifies how to sort orderBy_expression values, ascending or descending:
Return value
A table with the top N rows of table or an empty table if n_value is 0 (zero) or less. Rows are not necessarily
sorted in any particular order.
Remarks
If there is a tie, in order_by values, at the N-th row of the table, then all tied rows are returned. Then, when
there are ties at the N-th row the function might return more than n rows.
If n_value is 0 (zero) or less then TOPN returns an empty table.
TOPN does not guarantee any sort order for the results.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample creates a measure with the sales of the top 10 sold products.
Applies the result of a table expression as filters to columns from an unrelated table.
Syntax
TREATAS(table_expression, <column>[, <column>[, <column>[,…]]]} )
Parameters
T ERM DEF IN IT IO N
Return value
A table that contains all the rows in column(s) that are also in table_expression.
Remarks
The number of columns specified must match the number of columns in the table expression and be in
the same order.
If a value returned in the table expression does not exist in the column, it is ignored. For example,
TREATAS({"Red", "Green", "Yellow"}, DimProduct[Color]) sets a filter on column DimProduct[Color] with
three values "Red", "Green", and "Yellow". If "Yellow" does not exist in DimProduct[Color], the effective
filter values would are "Red" and "Green".
Best for use when a relationship does not exist between the tables. If you have multiple relationships
between the tables involved, consider using USERELATIONSHIP instead.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
In the following example, the model contains two unrelated product tables. If a user applies a filter to
DimProduct1[ProductCategory] selecting Bikes, Seats, Tires, the same filter, Bikes, Seats, Tires is applied to
DimProduct2[ProductCategory].
CALCULATE(
SUM(Sales[Amount]),
TREATAS(VALUES(DimProduct1[ProductCategory]), DimProduct2[ProductCategory])
)
See also
INTERSECT
FILTER
USERELATIONSHIP
UNION
8/25/2021 • 2 minutes to read
Syntax
UNION(<table_expression1>, <table_expression2> [,<table_expression>]…)
Parameters
T ERM DEF IN IT IO N
Return value
A table that contains all the rows from each of the two table expressions.
Remarks
The two tables must have the same number of columns.
Columns are combined by position in their respective tables.
The column names in the return table will match the column names in table_expression1.
Duplicate rows are retained.
The returned table has lineage where possible. For example, if the first column of each table_expression
has lineage to the same base column C1 in the model, the first column in the UNION result will have
lineage to C1. However, if combined columns have lineage to different base columns, or if there is an
extension column, the resulting column in UNION will have no lineage.
When data types differ, the resulting data type is determined based on the rules for data type coercion.
The returned table will not contain columns from related tables.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following expression creates a union by combining the USAInventory table and the INDInventory table into
a single table:
UNION(UsaInventory, IndInventory)
USAInventor y
C O UN T RY STAT E C O UN T TOTA L
USA CA 5 500
USA WA 10 900
INDInventor y
C O UN T RY STAT E C O UN T TOTA L
IND JK 20 800
IND MH 25 1000
IND WB 10 900
Return table,
C O UN T RY STAT E C O UN T TOTA L
USA CA 5 500
USA WA 10 900
IND JK 20 800
IND MH 25 1000
IND WB 10 900
VALUES
8/25/2021 • 3 minutes to read
When the input parameter is a column name, returns a one-column table that contains the distinct values from
the specified column. Duplicate values are removed and only unique values are returned. A BLANK value can be
added. When the input parameter is a table name, returns the rows from the specified table. Duplicate rows are
preserved. A BLANK row can be added.
NOTE
This function cannot be used to Return values into a cell or column on a worksheet; rather, you use it as an intermediate
function, nested in a formula, to get a list of distinct values that can be counted or used to filter or sum other values.
Syntax
VALUES(<TableNameOrColumnName>)
Parameters
T ERM DEF IN IT IO N
Return value
When the input parameter is a column name, a single column table. When the input parameter is a table name,
a table of the same columns is returned.
Remarks
When you use the VALUES function in a context that has been filtered, the unique values returned by
VALUES are affected by the filter. For example, if you filter by Region, and return a list of the values for
City, the list will include only those cities in the regions permitted by the filter. To return all of the cities,
regardless of existing filters, you must use the ALL function to remove filters from the table. The second
example demonstrates use of ALL with VALUES.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
For best practices when using VALUES, see Use SELECTEDVALUE instead of VALUES.
Related functions
In most scenarios, when the argument is a column name, the results of the VALUES function are identical to
those of the DISTINCT function. Both functions remove duplicates and return a list of the possible values in the
specified column. However, the VALUES function can also return a blank value. This blank value is useful in cases
where you are looking up distinct values from a related table, but a value used in the relationship is missing
from one table. In database terminology, this is termed a violation of referential integrity. Such mismatches in
data can occur when one table is being updated and the related table is not.
When the argument is a table name, the result of the VALUES function returns all rows in the specified table plus
a blank row, if there is a violation of referential integrity. The DISTINCT function removes duplicate rows and
returns unique rows in the specified table.
NOTE
The DISTINCT function allows a column name or any valid table expression to be its argument but the VALUES function
only accepts a column name or a table name as the argument.
The following table summarizes the mismatch between data that can occur in two related tables when
referential integrity is not preserved.
M Y O RDERS TA B L E M Y SA L ES TA B L E
If you use the DISTINCT function to return a list of dates, only two dates would be returned. However, if you use
the VALUES function, the function returns the two dates plus an additional blank member. Also, any row from
the MySales table that does not have a matching date in the MyOrders table will be "matched" to this unknown
member.
Example
The following formula counts the number of unique invoices (sales orders), and produces the following results
when used in a report that includes the Product Category Names:
= COUNTROWS(VALUES('InternetSales_USD'[SalesOrderNumber]))
Returns
RO W L A B EL S C O UN T IN VO IC ES
Accessories 18,208
Bikes 15,205
Clothing 7,461
See also
FILTER function
COUNTROWS function
Filter functions
Text functions
8/25/2021 • 2 minutes to read
Data Analysis Expressions (DAX) includes a set of text functions based on the library of string functions in Excel,
but which have been modified to work with tables and columns in tabular models. This section describes text
functions available in the DAX language.
In this category
F UN C T IO N DESC RIP T IO N
COMBINEVALUES Joins two or more text strings into one text string.
EXACT Compares two text strings and returns TRUE if they are
exactly the same, FALSE otherwise.
TRIM Removes all spaces from text except for single spaces
between words.
Joins two or more text strings into one text string. The primary purpose of this function is to support multi-
column relationships in DirectQuery models. See Remarks for details.
Syntax
COMBINEVALUES(<delimiter>, <expression>, <expression>[, <expression>]…)
Parameters
T ERM DEF IN IT IO N
Return value
The concatenated string.
Remarks
The COMBINEVALUES function assumes, but does not validate, that when the input values are different,
the output strings are also different. Based on this assumption, when COMBINEVALUES is used to create
calculated columns in order to build a relationship that joins multiple columns from two DirectQuery
tables, an optimized join condition is generated at query time. For example, if users want to create a
relationship between Table1(Column1, Column2) and Table2(Column1, Column2), they can create two
calculated columns, one on each table, as:
Table1[CalcColumn] = COMBINEVALUES(",", Table1[Column1], Table1[Column2])
and
Table2[CalcColumn] = COMBINEVALUES(",", Table2[Column1], Table2[Column2]) ,
And then create a relationship between Table1[CalcColumn] and Table2[CalcColumn] . Unlike other DAX
functions and operators, which are translated literally to the corresponding SQL operators and functions,
the above relationship generates a SQL join predicate as:
(Table1.Column1 = Table2.Column1 OR Table1.Column1 IS NULL AND Table2.Column1 IS NULL)
and
(Table1.Column2 = Table2.Column2 OR Table1.Column2 IS NULL AND Table2.Column2 IS NULL) .
The join predicate can potentially deliver much better query performance than one that involves complex
SQL operators and functions.
The COMBINEVALUES function relies on users to choose the appropriate delimiter to ensure that unique
combinations of input values produce distinct output strings but it does not validate that the assumption
is true. For example, if users choose "| " as the delimiter, but one row in Table1 has
Table1[Column1] = "| " and Table2 [Column2] = " " , while one row in Table2 has Table2[Column1] = " "
and Table2[Column2] = "| " , the two concatenated outputs will be the same "|| " , which seem to
indicate that the two rows are a match in the join operation. The two rows are not joined together if both
tables are from the same DirectQuery source although they are joined together if both tables are
imported.
Example
The following DAX query:
EVALUATE DISTINCT(SELECTCOLUMNS(DimDate, "Month", COMBINEVALUES(",", [MonthName], [CalendarYear])))
[MONT H ]
January,2007
February,2007
March,2007
April,2007
May,2007
June,2007
July,2007
August,2007
September,2007
October,2007
November,2007
December,2007
January,2008
January,2008
February,2008
March,2008
April,2008
[MONT H ]
May,2008
June,2008
July,2008
August,2008
September,2008
October,2008
November,2008
December,2008
CONCATENATE
8/25/2021 • 2 minutes to read
Syntax
CONCATENATE(<text1>, <text2>)
Parameters
T ERM DEF IN IT IO N
text1, text2 The text strings to be joined into a single text string. Strings
can include text or numbers.
Return value
The concatenated string.
Remarks
The CONCATENATE function joins two text strings into one text string. The joined items can be text,
numbers or Boolean values represented as text, or a combination of those items. You can also use a
column reference if the column contains appropriate values.
The CONCATENATE function in DAX accepts only two arguments, whereas the Excel CONCATENATE
function accepts up to 255 arguments. If you need to concatenate multiple columns, you can create a
series of calculations or, better, use the concatenation operator (& ) to join all of them in a simpler
expression.
If you want to use text strings directly, rather than using a column reference, you must enclose each string
in double quotation marks.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
This formula uses nested CONCATENATE and IF functions, together with the ampersand (& ) operator, to
conditionally concatenate three string values and add spaces as separators.
The CONCATENATE function in DAX accepts only two arguments, whereas the Excel CONCATENATE function
accepts up to 255 arguments. If you need to add more arguments, you can use the ampersand (&) operator. For
example, the following formula produces the results, MTN-40 and MTN-42.
See also
Text functions
CONCATENATEX
8/25/2021 • 2 minutes to read
Syntax
CONCATENATEX(<table>, <expression>[, <delimiter> [, <orderBy_expression> [, <order>]]...])
Parameters
T ERM DEF IN IT IO N
table The table containing the rows for which the expression will
be evaluated.
Return value
A text string.
Remarks
This function takes as its first argument a table or an expression that returns a table. The second
argument is a column that contains the values you want to concatenate, or an expression that returns a
value.
Concatenated values are not necessarily sorted in any particular order, unless orderBy_expression is
specified.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
Employees table
F IRST N A M E L A ST N A M E
Alan Brewer
Michael Blythe
Returns:
"Alan Brewer, Michael Blythe"
EXACT
8/25/2021 • 2 minutes to read
Compares two text strings and returns TRUE if they are exactly the same, FALSE otherwise. EXACT is case-
sensitive but ignores formatting differences. You can use EXACT to test text being entered into a document.
Syntax
EXACT(<text1>,<text2>)
Parameters
T ERM DEF IN IT IO N
Return value
True or false. (Boolean)
Example
The following formula checks the value of Column1 for the current row against the value of Column2 for the
current row, and returns TRUE if they are the same, and returns FALSE if they are different.
= EXACT([Column1],[Column2])
See also
Text functions
FIND
8/25/2021 • 2 minutes to read
Returns the starting position of one text string within another text string. FIND is case-sensitive.
Syntax
FIND(<find_text>, <within_text>[, [<start_num>][, <NotFoundValue>]])
Parameters
T ERM DEF IN IT IO N
find_text The text you want to find. Use double quotes (empty text) to
match the first character in within_text .
Return value
Number that shows the starting point of the text string you want to find.
Remarks
Whereas Microsoft Excel has multiple versions of the FIND function to accommodate single-byte
character set (SBCS) and double-byte character set (DBCS) languages, DAX uses Unicode and counts each
character the same way; therefore, you do not need to use a different version depending on the character
type.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
FIND does not support wildcards. To use wildcards, use SEARCH.
Example
The following formula finds the position of the first letter of the product designation, BMX, in the string that
contains the product description.
Rounds a number to the specified number of decimals and returns the result as text. You can specify that the
result be returned with or without commas.
Syntax
FIXED(<number>, <decimals>, <no_commas>)
Parameters
T ERM DEF IN IT IO N
Return value
A number represented as text.
Remarks
If the value used for the decimals parameter is negative, number is rounded to the left of the decimal
point.
If you omit decimals , it is assumed to be 2.
If no_commas is 0 or is omitted, then the returned text includes commas as usual.
The major difference between formatting a cell containing a number by using a command and formatting
a number directly with the FIXED function is that FIXED converts its result to text. A number formatted
with a command from the formatting menu is still a number.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example gets the numeric value for the current row in column, PctCost, and returns it as text with
4 decimal places and no commas.
= FIXED([PctCost],3,1)
Numbers can never have more than 15 significant digits, but decimals can be as large as 127.
See also
Text functions
Math and Trig functions
FORMAT
9/15/2021 • 13 minutes to read
Syntax
FORMAT(<value>, <format_string>[, <locale_name>])
Parameters
T ERM DEF IN IT IO N
Return value
A string containing value formatted as defined by format_string .
NOTE
If value is BLANK, the function returns an empty string.
If format_string is BLANK, the value is formatted with a "General Number" or "General Date" format (according to value
data type).
Remarks
Predefined format strings use the model culture property when formatting the result. By default, the
model culture property is set according to the user locale of the computer. For new Power BI Desktop
models, the model culture property can be changed in Options > Regional Settings > Model language.
For Analysis Services, model culture is set according to the Language property initially defined by the
instance.
The format strings supported as an argument to the DAX FORMAT function are based on the format
strings used by Visual Basic (OLE Automation), not on the format strings used by the .NET Framework.
Therefore, you might get unexpected results or an error if the argument doesn't match any defined
format strings. For example, "p" as an abbreviation for "Percent" isn't supported. Strings that you provide
as an argument to the FORMAT function that aren't included in the list of predefined format strings are
handled as part of a custom format string, or as a string literal.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Examples
Format strings
Returns:
12345.67 "General Number" displays the number with no formatting.
$12,345.67 "Currency" displays the number with your currency locale formatting. The sample here shows the
default United States currency formatting.
12345.67 "Fixed" displays at least one digit to the left of the decimal separator and two digits to the right of the
decimal separator.
12,345.67 "Standard" displays at least one digit to the left of the decimal separator and two digits to the right
of the decimal separator, and includes thousand separators. The sample here shows the default United States
number formatting.
1,234,567.00 % "Percent" displays the number as a percentage (multiplied by 100) with formatting and the
percent sign at the right of the number separated by a single space.
1.23E+04 "Scientific" displays the number in scientific notation with two decimal digits.
Datetime with optional locale_name
Returns:
12/15/2020 12:30:59 PM Where month precedes day and time is 12-hour format.
15/12/2020 12:30:59 Where day precedes month and time is 24-hour format.
12/15/2020 12:30:59 Where month precedes day and time is 24-hour format. Because a non-locale
dependent format string is specified, the locale is not applied and the non-locale format is returned.
F O RM AT DESC RIP T IO N
"Fixed" Displays at least one digit to the left and two digits to the
right of the decimal separator.
F O RM AT DESC RIP T IO N
IF Y O U USE T H E RESULT IS
Two sections The first section applies to positive values and zeros, the
second to negative values.
Three sections The first section applies to positive values, the second to
negative values, and the third to zeros.
"$#,##0;($#,##0)"
If you include semicolons with nothing between them, the missing section is defined using the format of the
positive value. For example, the following format displays positive and negative values using the format in the
first section and displays "Zero" if the value is zero.
"$#,##0"
If you include semicolons with nothing between them, the missing section is shown using the format of the
positive value.
Custom numeric format characters
The following custom numeric format characters can be specified in the format_string argument:
C H A RA C T ER DESC RIP T IO N
("ABC") Display the string inside the double quotation marks (" ").
F O RM AT DESC RIP T IO N
"Long Date" or "Medium Date" Displays a date according to your current culture's long date
format. For example, Wednesday, March 12, 2008.
F O RM AT DESC RIP T IO N
"Short Date" Displays a date using your current culture's short date
format. For example, 3/12/2008.
"Long Time" or Displays a time using your current culture's long time format;
typically includes hours, minutes, seconds. For example,
11:07:31 AM.
"Medium Time" Displays a time in 12 hour format. For example, 11:07 AM.
C H A RA C T ER DESC RIP T IO N
am/pm Use the 12-hour clock and display a lowercase AM with any
hour before noon; display a lowercase PM with any hour
between noon and 11:59 P.M.
A/P Use the 12-hour clock and display an uppercase A with any
hour before noon; display an uppercase P with any hour
between noon and 11:59 P.M.
a/p Use the 12-hour clock and display a lowercase A with any
hour before noon; display a lowercase P with any hour
between noon and 11:59 P.M.
AMPM Use the 12-hour clock and display the AM string literal as
defined by your system with any hour before noon; display
the PM string literal as defined by your system with any
hour between noon and 11:59 P.M. AMPM can be either
uppercase or lowercase, but the case of the string displayed
matches the string as defined by your system settings. The
default format is AM/PM. If your system is set to 24-hour
clock, the string is typical set to an empty string.
Date/time formatting uses the current user locale to format the string. For example, consider the date June 25,
2020. When it's formatted using format string "m/d/yyyy" it will be:
User locale is United States of America (en-US): "6/25/2020"
User locale is Germany (de-DE): "6.25.2020"
Custom date/time format examples
The following examples use the date/time Thursday, June 25, 2020, at 1:23:45 PM. Germany (de-DE) uses a 24-
hour system. There's no equivalent of AM/PM.
"d" 25 25
"dd" 25 25
"ddd" Thu Do
"w" 5 5
F O RM AT RESULT ( EN - US) RESULT ( DE- DE)
"ww" 26 26
"m" 6 6
"mm" 06 06
"q" 2 2
"yy" 20 20
Returns the specified number of characters from the start of a text string.
Syntax
LEFT(<text>, <num_chars>)
Parameters
T ERM DEF IN IT IO N
text The text string containing the characters you want to extract,
or a reference to a column that contains text.
Return value
A text string.
Remarks
Whereas Microsoft Excel contains different functions for working with text in single-byte and double-byte
character languages, DAX works with Unicode and stores all characters as the same length; therefore, a
single function is enough.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following example returns the first five characters of the company name in the column [ResellerName] and
the first five letters of the geographical code in the column [GeographyKey] and concatenates them, to create an
identifier.
= CONCATENATE(LEFT('Reseller'[ResellerName],LEFT(GeographyKey,3))
If the num_chars argument is a number that is larger than the number of characters available, the function
returns the maximum characters available and does not raise an error. For example, the column [GeographyKey]
contains numbers such as 1, 12 and 311; therefore the result also has variable length.
See also
Text functions
LEN
8/25/2021 • 2 minutes to read
Syntax
LEN(<text>)
Parameters
T ERM DEF IN IT IO N
text The text whose length you want to find, or a column that
contains text. Spaces count as characters.
Return value
A whole number indicating the number of characters in the text string.
Remarks
Whereas Microsoft Excel has different functions for working with single-byte and double-byte character
languages, DAX uses Unicode and stores all characters with the same length.
LEN always counts each character as 1, no matter what the default language setting is.
If you use LEN with a column that contains non-text values, such as dates or Booleans, the function
implicitly casts the value to text, using the current column format.
Example
The following formula sums the lengths of addresses in the columns, [AddressLine1] and [AddressLine2].
= LEN([AddressLine1])+LEN([AddressLin2])
LOWER
8/25/2021 • 2 minutes to read
Syntax
LOWER(<text>)
Parameters
T ERM DEF IN IT IO N
Return value
Text in lowercase.
Remarks
Characters that are not letters are not changed. For example, the formula = LOWER("123ABC") returns 123abc .
Example
The following formula gets each row in the column, [ProductCode], and converts the value to all lowercase.
Numbers in the column are not affected.
= LOWER('New Products'[ProductCode])
See also
Text functions
MID
8/25/2021 • 2 minutes to read
Returns a string of characters from the middle of a text string, given a starting position and length.
Syntax
MID(<text>, <start_num>, <num_chars>)
Parameters
T ERM DEF IN IT IO N
text The text string from which you want to extract the
characters, or a column that contains text.
Return value
A string of text of the specified length.
Remarks
Whereas Microsoft Excel has different functions for working with single-byte and double-byte characters
languages, DAX uses Unicode and stores all characters with the same length.
Examples
The following expression,
MID("abcde",2,3))
Returns "bcd" .
The following expression,
MID('Reseller'[ResellerName],1,5))
Returns the same result as LEFT([ResellerName],5) . Both expressions return the first 5 letters of column,
[ResellerName] .
See also
Text functions
REPLACE
8/25/2021 • 2 minutes to read
REPLACE replaces part of a text string, based on the number of characters you specify, with a different text
string.
Syntax
REPLACE(<old_text>, <start_num>, <num_chars>, <new_text>)
Parameters
T ERM DEF IN IT IO N
old_text The string of text that contains the characters you want to
replace, or a reference to a column that contains text.
Return value
A text string.
Remarks
Whereas Microsoft Excel has different functions for use with single-byte and double-byte character
languages, DAX uses Unicode and therefore stores all characters as the same length.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following formula creates a new calculated column that replaces the first two characters of the product code
in column, [ProductCode], with a new two-letter code, OB.
Repeats text a given number of times. Use REPT to fill a cell with a number of instances of a text string.
Syntax
REPT(<text>, <num_times>)
Parameters
T ERM DEF IN IT IO N
Return value
A string containing the changes.
Remarks
If number_times is 0 (zero), REPT returns a blank.
If number_times is not an integer, it is truncated.
The result of the REPT function cannot be longer than 32,767 characters, or REPT returns an error.
= REPT("85",3)
= REPT([MyText],[MyNumber])
M Y T EXT M Y N UM B ER C A L C UL AT EDC O L UM N 1
Text 2 TextText
M Y T EXT M Y N UM B ER C A L C UL AT EDC O L UM N 1
Number 0
85 3 858585
See also
Text functions
RIGHT
8/25/2021 • 2 minutes to read
RIGHT returns the last character or characters in a text string, based on the number of characters you specify.
Syntax
RIGHT(<text>, <num_chars>)
Parameters
T ERM DEF IN IT IO N
text The text string that contains the characters you want to
extract, or a reference to a column that contains text.
If the column reference does not contain text, it is implicitly cast as text.
Return value
A text string containing the specified right-most characters.
Remarks
RIGHT always counts each character, whether single-byte or double-byte, as 1, no matter what the default
language setting is.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
= RIGHT('New Products'[ProductCode],2)
= RIGHT('New Products'[ProductCode],[MyCount])
See also
Text functions
LEFT
MID
SEARCH
8/25/2021 • 2 minutes to read
Returns the number of the character at which a specific character or text string is first found, reading left to right.
Search is case-insensitive and accent sensitive.
Syntax
SEARCH(<find_text>, <within_text>[, [<start_num>][, <NotFoundValue>]])
Parameters
T ERM DEF IN IT IO N
You can use wildcard characters — the question mark (?) and
asterisk (*) — in find_text . A question mark matches any
single character; an asterisk matches any sequence of
characters. If you want to find an actual question mark or
asterisk, type a tilde (~) before the character.
Return value
The number of the starting position of the first text string from the first character of the second text string.
Remarks
The search function is case insensitive. Searching for "N" will find the first occurrence of 'N' or 'n'.
The search function is accent sensitive. Searching for "á" will find the first occurrence of 'á' but no
occurrences of 'a', 'à', or the capitalized versions 'A', 'Á'.
By using this function, you can locate one text string within a second text string, and return the position
where the first string starts.
You can use the SEARCH function to determine the location of a character or text string within another
text string, and then use the MID function to return the text, or use the REPLACE function to change the
text.
If the find_text cannot be found in within_text , the formula returns an error. This behavior is like Excel,
which returns #VALUE if the substring is not found. Nulls in within_text will be interpreted as an empty
string in this context.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
= SEARCH("n","printer")
The formula returns 4 because "n" is the fourth character in the word "printer."
= SEARCH("-",[PostalCode])
The return result is a column of numbers, indicating the index position of the hyphen.
= IFERROR(SEARCH("-",[PostalCode]),-1)
The data type of the value that you use as an error output must match the data type of the non-error output
type. In this case, you provide a numeric value to be output in case of an error because SEARCH returns an
integer value. However, you could also return a blank (empty string) by using BLANK() as the second argument
to IFERROR.
See also
MID
REPLACE
Text functions
SUBSTITUTE
8/25/2021 • 2 minutes to read
Syntax
SUBSTITUTE(<text>, <old_text>, <new_text>, <instance_num>)
Parameters
T ERM DEF IN IT IO N
Return value
A string of text.
Remarks
Use the SUBSTITUTE function when you want to replace specific text in a text string; use the REPLACE
function when you want to replace any text of variable length that occurs in a specific location in a text
string.
The SUBSTITUTE function is case-sensitive. If case does not match between text and old_text ,
SUBSTITUTE will not replace the text.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
Text functions
REPLACE
TRIM
8/25/2021 • 2 minutes to read
Removes all spaces from text except for single spaces between words.
Syntax
TRIM(<text>)
Parameters
T ERM DEF IN IT IO N
text The text from which you want spaces removed, or a column
that contains text.
Return value
The string with spaces removed.
Remarks
Use TRIM on text that you have received from another application that may have irregular spacing.
The TRIM function was originally designed to trim the 7-bit ASCII space character (value 32) from text. In
the Unicode character set, there is an additional space character called the nonbreaking space character
that has a decimal value of 160. This character is commonly used in Web pages as the HTML entity,
. By itself, the TRIM function does not remove this nonbreaking space character. For an example of
how to trim both space characters from text, see Remove spaces and nonprinting characters from text.
Example
The following formula creates a new string that does not have trailing white space.
When you create the formula, the formula is propagated through the row just as you typed it, so that you see
the original string in each formula and the results are not apparent. However, when the formula is evaluated the
string is trimmed.
You can verify that the formula produces the correct result by checking the length of the calculated column
created by the previous formula, as follows:
See also
Text functions
UNICHAR
8/25/2021 • 2 minutes to read
Syntax
UNICHAR(number)
Parameters
T ERM DEF IN IT IO N
Return value
A character represented by the Unicode number.
Remarks
If XML characters are not invalid, UNICHAR returns an error.
If Unicode numbers are partial surrogates and data types are not valid, UNICHAR returns an error.
If numbers are numeric values that fall outside the allowable range, UNICHAR returns an error.
If number is zero (0), UNICHAR returns an error.
The Unicode character returned can be a string of characters, for example in UTF-8 or UTF-16 codes.
Example
The following example returns the character represented by the Unicode number 66 (uppercase A).
= UNICHAR(65)
The following example returns the character represented by the Unicode number 32 (space character).
= UNICHAR(32)
The following example returns the character represented by the Unicode number 9733 (★ character).
= UNICHAR(9733)
UNICODE
8/25/2021 • 2 minutes to read
Returns the number (code point) corresponding to the first character of the text.
Syntax
UNICODE( <Text> )
Parameters
T ERM DEF IN IT IO N
Text Text is the character for which you want the Unicode value.
Return value
A numeric code for the first character in a text string.
UPPER
8/25/2021 • 2 minutes to read
Syntax
UPPER (<text>)
Parameters
T ERM DEF IN IT IO N
Return value
Same text, in uppercase.
Example
The following formula converts the string in the column, [ProductCode], to all uppercase. Non-alphabetic
characters are not affected.
See also
Text functions
LOWER function
VALUE
8/25/2021 • 2 minutes to read
Syntax
VALUE(<text>)
Parameters
T ERM DEF IN IT IO N
Return value
The converted number in decimal data type.
Remarks
The value passed as the text parameter can be in any of the constant, number, date, or time formats
recognized by the application or services you are using. If text is not in one of these formats, an error is
returned.
You do not generally need to use the VALUE function in a formula because the engine implicitly converts
text to numbers as necessary.
You can also use column references. For example, if you have a column that contains mixed number
types, VALUE can be used to convert all values to a single numeric data type. However, if you use the
VALUE function with a column that contains mixed numbers and text, the entire column is flagged with an
error, because not all values in all rows can be converted to numbers.
Example
The following formula converts the typed string, "3", into the numeric value 3.
= VALUE("3")
See also
Text functions
Time intelligence functions
8/25/2021 • 3 minutes to read
Data Analysis Expressions (DAX) includes time-intelligence functions that enable you to manipulate data using
time periods, including days, months, quarters, and years, and then build and compare calculations over those
periods.
In this category
F UN C T IO N DESC RIP T IO N
CLOSINGBALANCEMONTH Evaluates the expression at the last date of the month in the
current context.
CLOSINGBALANCEYEAR Evaluates the expression at the last date of the year in the
current context.
DATESMTD Returns a table that contains a column of the dates for the
month to date, in the current context.
DATESQTD Returns a table that contains a column of the dates for the
quarter to date, in the current context.
DATESYTD Returns a table that contains a column of the dates for the
year to date, in the current context.
ENDOFMONTH Returns the last date of the month in the current context for
the specified column of dates.
ENDOFQUARTER Returns the last date of the quarter in the current context
for the specified column of dates.
ENDOFYEAR Returns the last date of the year in the current context for
the specified column of dates.
F UN C T IO N DESC RIP T IO N
FIRSTDATE Returns the first date in the current context for the specified
column of dates.
FIRSTNONBLANK Returns the first value in the column, column, filtered by the
current context, where the expression is not blank
LASTDATE Returns the last date in the current context for the specified
column of dates.
LASTNONBLANK Returns the last value in the column, column, filtered by the
current context, where the expression is not blank.
NEXTDAY Returns a table that contains a column of all dates from the
next day, based on the first date specified in the dates
column in the current context.
NEXTMONTH Returns a table that contains a column of all dates from the
next month, based on the first date in the dates column in
the current context.
OPENINGBALANCEMONTH Evaluates the expression at the first date of the month in the
current context.
OPENINGBALANCEYEAR Evaluates the expression at the first date of the year in the
current context.
PREVIOUSMONTH Returns a table that contains a column of all dates from the
previous month, based on the first date in the dates column,
in the current context.
PREVIOUSQUARTER Returns a table that contains a column of all dates from the
previous quarter, based on the first date in the dates
column, in the current context.
F UN C T IO N DESC RIP T IO N
PREVIOUSYEAR Returns a table that contains a column of all dates from the
previous year, given the last date in the dates column, in the
current context.
STARTOFMONTH Returns the first date of the month in the current context for
the specified column of dates.
STARTOFQUARTER Returns the first date of the quarter in the current context
for the specified column of dates.
STARTOFYEAR Returns the first date of the year in the current context for
the specified column of dates.
TOTALMTD Evaluates the value of the expression for the month to date,
in the current context.
TOTALQTD Evaluates the value of the expression for the dates in the
quarter to date, in the current context.
Evaluates the expression at the last date of the month in the current context.
Syntax
CLOSINGBALANCEMONTH(<expression>,<dates>[,<filter>])
Parameters
PA RA M ET ER DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated at the last date of the month in the current context.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in CALCULATE function.
NOTE
The filter expression has restrictions described in CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Month End Inventory Value' of the product
inventory.
=
CLOSINGBALANCEMONTH(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateTim
e[DateKey])
See also
Time intelligence functions
CLOSINGBALANCEYEAR function
CLOSINGBALANCEQUARTER function
CLOSINGBALANCEQUARTER
8/25/2021 • 2 minutes to read
Evaluates the expression at the last date of the quarter in the current context.
Syntax
CLOSINGBALANCEQUARTER(<expression>,<dates>[,<filter>])
Parameters
T ERM DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated at the last date of the quarter in the current context.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in CALCULATE function.
NOTE
The filter expression has restrictions described in CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Quarter End Inventory Value' of the product
inventory.
=
CLOSINGBALANCEQUARTER(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateT
ime[DateKey])
See also
Time intelligence functions
CLOSINGBALANCEYEAR function
CLOSINGBALANCEMONTH function
CLOSINGBALANCEYEAR
8/25/2021 • 2 minutes to read
Evaluates the expression at the last date of the year in the current context.
Syntax
CLOSINGBALANCEYEAR(<expression>,<dates>[,<filter>][,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A scalar value that represents the expression evaluated at the last date of the year in the current context.
Remarks
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in CALCULATE function.
NOTE
The filter expression has restrictions described in CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Year End Inventory Value' of the product
inventory.
=
CLOSINGBALANCEYEAR(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateTime
[DateKey])
See also
Time intelligence functions
CLOSINGBALANCEYEAR function
CLOSINGBALANCEQUARTER function
CLOSINGBALANCEMONTH function
DATEADD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of dates, shifted either forward or backward in time by the specified
number of intervals from the dates in the current context.
Syntax
DATEADD(<dates>,<number_of_intervals>,<interval>)
Parameters
T ERM DEF IN IT IO N
interval The interval by which to shift the dates. The value for
interval can be one of the following: year , quarter ,
month , day
Return value
A table containing a single column of date values.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in the topic, CALCULATE function.
If the number specified for number_of_inter vals is positive, the dates in dates are moved forward in
time; if the number is negative, the dates in dates are shifted back in time.
The inter val parameter is an enumeration, not a set of strings; therefore values should not be enclosed
in quotation marks. Also, the values: year , quarter , month , day should be spelled in full when using
them.
The result table includes only dates that exist in the dates column.
If the dates in the current context do not form a contiguous interval, the function returns an error.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
= DATEADD(DateTime[DateKey],-1,year)
See also
Time intelligence functions
Date and time functions
DATESBETWEEN
8/25/2021 • 2 minutes to read
Returns a table that contains a column of dates that begins with a specified start date and continues until a
specified end date.
This function is suited to pass as a filter to the CALCULATE function. Use it to filter an expression by a custom
date range.
NOTE
If you're working with standard date intervals such as days, months, quarters, or years, it's recommended you use the
better suited DATESINPERIOD function.
Syntax
DATESBETWEEN(<dates>, <start_date>, <end_date>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
In the most common use case, dates is a reference to the date column of a marked date table.
If star t_date is BLANK, then star t_date will be the earliest value in the dates column.
If end_date is BLANK, then end_date will be the latest value in the dates column.
Dates used as the star t_date and end_date are inclusive. So, for example, if the star t_date value is July
1, 2019, then that date will be included in the returned table (providing the date exists in the dates
column).
The returned table can only contain dates stored in the dates column. So, for example, if the dates
column starts from July 1, 2017, and the star t_date value is July 1, 2016, the returned table will start
from July 1, 2017.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following Sales table measure definition uses the DATESBETWEEN function to produce a life-to-date (LTD)
calculation. Life-to-date represents the accumulation of a measure over time since the very beginning of time.
Notice that the formula uses the MAX function. This function returns the latest date that's in the filter context. So,
the DATESBETWEEN function returns a table of dates beginning from the earliest date until the latest date being
reported.
Examples in this article can be added to the Power BI Desktop sample model. To get the model, see DAX sample
model.
Customers LTD =
CALCULATE(
DISTINCTCOUNT(Sales[CustomerKey]),
DATESBETWEEN(
'Date'[Date],
BLANK(),
MAX('Date'[Date])
)
)
Consider that the earliest date stored in the Date table is July 1, 2017. So, when a report filters the measure by
the month of June 2020, the DATESBETWEEN function returns a date range from July 1, 2017 until June 30,
2020.
See also
Time intelligence functions (DAX)
Date and time functions (DAX)
DATESINPERIOD function (DAX)
DATESINPERIOD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of dates that begins with a specified start date and continues for the
specified number and type of date intervals.
This function is suited to pass as a filter to the CALCULATE function. Use it to filter an expression by standard
date intervals such as days, months, quarters, or years.
Syntax
DATESINPERIOD(<dates>, <start_date>, <number_of_intervals>, <interval>)
Parameters
T ERM DEF IN IT IO N
interval The interval by which to shift the dates. The value for
interval can be one of the following: DAY , MONTH ,
QUARTER , and YEAR
Return value
A table containing a single column of date values.
Remarks
In the most common use case, dates is a reference to the date column of a marked date table.
If the number specified for number_of_inter vals is positive, dates are moved forward in time; if the
number is negative, dates are shifted backward in time.
The inter val parameter is an enumeration. Valid values are DAY , MONTH , QUARTER , and YEAR . Because
it's an enumeration, values aren't passed in as strings. So don't enclose them within quotation marks.
The returned table can only contain dates stored in the dates column. So, for example, if the dates
column starts from July 1, 2017, and the star t_date value is July 1, 2016, the returned table will start
from July 1, 2017.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following Sales table measure definition uses the DATESINPERIOD function to calculate revenue for the
prior year (PY).
Notice the formula uses the MAX function. This function returns the latest date that's in the filter context. So, the
DATESINPERIOD function returns a table of dates beginning from the latest date for the last year.
Examples in this article can be added to the Power BI Desktop sample model. To get the model, see DAX sample
model.
Revenue PY =
CALCULATE(
SUM(Sales[Sales Amount]),
DATESINPERIOD(
'Date'[Date],
MAX('Date'[Date]),
-1,
YEAR
)
)
Consider that the report is filtered by the month of June 2020. The MAX function returns June 30, 2020. The
DATESINPERIOD function then returns a date range from July 1, 2019 until June 30, 2020. It's a year of date
values starting from June 30, 2020 for the last year.
See also
Time intelligence functions (DAX)
Date and time functions (DAX)
DATESBETWEEN function (DAX)
DATESMTD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of the dates for the month to date, in the current context.
Syntax
DATESMTD(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Month To Date Total' for Internet Sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), DATESMTD(DateTime[DateKey]))
See also
Time intelligence functions
Date and time functions
DATESYTD function
DATESQTD function
DATESQTD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of the dates for the quarter to date, in the current context.
Syntax
DATESQTD(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Quarterly Running Total' of Internet Sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), DATESQTD(DateTime[DateKey]))
See also
Time intelligence functions
Date and time functions
DATESYTD function
DATESMTD function
DATESYTD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of the dates for the year to date, in the current context.
Syntax
DATESYTD(<dates> [,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A table containing a single column of date values.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
NOTE
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Running Total' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), DATESYTD(DateTime[DateKey]))
See also
Time intelligence functions
Date and time functions
DATESMTD function
DATESQTD function
ENDOFMONTH
8/25/2021 • 2 minutes to read
Returns the last date of the month in the current context for the specified column of dates.
Syntax
ENDOFMONTH(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the end of the month, for the current context.
= ENDOFMONTH(DateTime[DateKey])
See also
Date and time functions
Time intelligence functions
ENDOFYEAR function
ENDOFQUARTER function
ENDOFQUARTER
8/25/2021 • 2 minutes to read
Returns the last date of the quarter in the current context for the specified column of dates.
Syntax
ENDOFQUARTER(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the end of the quarter, for the current context.
= ENDOFQUARTER(DateTime[DateKey])
See also
Date and time functions
Time intelligence functions
ENDOFYEAR function
ENDOFMONTH function
ENDOFYEAR
8/25/2021 • 2 minutes to read
Returns the last date of the year in the current context for the specified column of dates.
Syntax
ENDOFYEAR(<dates> [,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the end of the fiscal year that ends on June 30, for
the current context.
= ENDOFYEAR(DateTime[DateKey],"06/30/2004")
See also
Date and time functions
Time intelligence functions
ENDOFMONTH function
ENDOFQUARTER function
FIRSTDATE
8/25/2021 • 2 minutes to read
Returns the first date in the current context for the specified column of dates.
Syntax
FIRSTDATE(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
When the current context is a single date, the date returned by the FIRSTDATE and LASTDATE functions
will be equal.
The Return value is a table that contains a single column and single value. Therefore, this function can be
used as an argument to any function that requires a table in its arguments. Also, the returned value can
be used whenever a date value is required.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that obtains the first date when a sale was made in the Internet
sales channel for the current context.
= FIRSTDATE('InternetSales_USD'[SaleDateKey])
See also
Date and time functions
Time intelligence functions
LASTDATE function
FIRSTNONBLANK function
FIRSTNONBLANK
8/25/2021 • 2 minutes to read
Returns the first value in the column, column , filtered by the current context, where the expression is not blank.
Syntax
FIRSTNONBLANK(<column>,<expression>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with the computed first value.
Remarks
The column argument can be any of the following:
A reference to any column.
A table with a single column.
A Boolean expression that defines a single-column table .
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is typically used to return the first value of a column for which the expression is not blank.
For example, you could get the last value for which there were sales of a product.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
LASTNONBLANK function
Statistical functions
FIRSTNONBLANKVALUE
8/25/2021 • 2 minutes to read
Evaluates an expression filtered by the sorted values of a column and returns the first value of the expression
that is not blank.
Syntax
FIRSTNONBLANKVALUE(<column>, <expression>)
Parameters
T ERM DEF IN IT IO N
Return value
The first non-blank value of <expression> corresponding to the sorted values of <column>.
Remarks
The column argument can be any of the following:
A reference to any column.
A table with a single column.
This function is different from FIRSTNONBLANK in that the <column> is added to the filter context for
the evaluation of <expression>.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query,
EVALUATE
SUMMARIZECOLUMNS(
DimProduct[Class],
"FNBV",
FIRSTNONBLANKVALUE(
DimDate[Date],
SUM(FactInternetSales[SalesAmount])
)
)
Returns,
DIM P RO DUC T [ C L A SS] [ F N B V]
L 699.0982
H 13778.24
M 1000.4375
533.83
LASTDATE
8/25/2021 • 2 minutes to read
Returns the last date in the current context for the specified column of dates.
Syntax
LASTDATE(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
When the current context is a single date, the date returned by the FIRSTDATE and LASTDATE functions
will be equal.
Technically, the Return value is a table that contains a single column and single value. Therefore, this
function can be used as an argument to any function that requires a table in its arguments. Also, the
returned value can be used whenever a date value is required.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that obtains the last date, for the current context, when a sale
was made in the Internet sales channel.
= LASTDATE('InternetSales_USD'[SaleDateKey])
See also
Date and time functions
Time intelligence functions
FIRSTDATE function
LASTNONBLANK function
LASTNONBLANK
8/25/2021 • 2 minutes to read
Returns the last value in the column, column , filtered by the current context, where the expression is not blank.
Syntax
LASTNONBLANK(<column>,<expression>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with the computed last value.
Remarks
The column argument can be any of the following:
A reference to any column.
A table with a single column.
A Boolean expression that defines a single-column table
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is typically used to return the last value of a column for which the expression is not blank.
For example, you could get the last value for which there were sales of a product.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
See also
FIRSTNONBLANK function
Statistical functions
LASTNONBLANKVALUE
8/25/2021 • 2 minutes to read
Evaluates an expression filtered by the sorted values of a column and returns the last value of the expression
that is not blank.
Syntax
LASTNONBLANKVALUE(<column>, <expression>)
Parameters
T ERM DEF IN IT IO N
Return value
The last non-blank value of <expression> corresponding to the sorted values of <column>.
Remarks
The column argument can be any of the following:
A reference to any column.
A table with a single column.
This function is different from LASTNONBLANK in that the <column> is added to the filter context for the
evaluation of <expression>.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following DAX query,
EVALUATE
SUMMARIZECOLUMNS(
DimProduct[Class],
"LNBV",
LASTNONBLANKVALUE(
DimDate[Date],
SUM(FactInternetSales[SalesAmount])
)
)
Returns,
DIM P RO DUC T [ C L A SS] [ L N B V]
L 132.44
H 137.6
M 84.97
2288.6
NEXTDAY
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates from the next day, based on the first date specified in the
dates column in the current context.
Syntax
NEXTDAY(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function returns all dates from the next day to the first date in the input parameter. For example, if
the first date in the dates argument refers to June 10, 2009; then this function returns all dates equal to
June 11, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'next day sales' of Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), NEXTDAY('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
NEXTQUARTER function
NEXTMONTH function
NEXTYEAR function
NEXTMONTH
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates from the next month, based on the first date in the dates
column in the current context.
Syntax
NEXTMONTH(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function returns all dates from the next day to the first date in the input parameter. For example, if
the first date in the dates argument refers to June 10, 2009; then this function returns all dates for the
month of July, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'next month sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), NEXTMONTH('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
NEXTDAY function
NEXTQUARTER function
NEXTYEAR function
NEXTQUARTER
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates in the next quarter, based on the first date specified in the
dates column, in the current context.
Syntax
NEXTQUARTER(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function returns all dates in the next quarter, based on the first date in the input parameter. For
example, if the first date in the dates column refers to June 10, 2009, this function returns all dates for
the quarter July to September, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'next quarter sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), NEXTQUARTER('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
NEXTDAY function
NEXTMONTH function
NEXTYEAR function
NEXTYEAR
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates in the next year, based on the first date in the dates column,
in the current context.
Syntax
NEXTYEAR(<dates>[,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A table containing a single column of date values.
Remarks
This function returns all dates in the next year, based on the first date in the input column. For example, if
the first date in the dates column refers to the year 2007, this function returns all dates for the year
2008.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'next year sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), NEXTYEAR('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
NEXTDAY function
NEXTQUARTER function
NEXTMONTH function
OPENINGBALANCEMONTH
8/25/2021 • 2 minutes to read
Evaluates the expression at the first date of the month in the current context.
Syntax
OPENINGBALANCEMONTH(<expression>,<dates>[,<filter>])
Parameters
T ERM DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated at the first date of the month in the current context.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The filter expression has restrictions described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Month Start Inventory Value' of the product
inventory.
=
OPENINGBALANCEMONTH(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateTim
e[DateKey])
See also
OPENINGBALANCEYEAR function
OPENINGBALANCEQUARTER function
Time intelligence functions
CLOSINGBALANCEMONTH function
OPENINGBALANCEQUARTER
8/25/2021 • 2 minutes to read
Evaluates the expression at the first date of the quarter, in the current context.
Syntax
OPENINGBALANCEQUARTER(<expression>,<dates>[,<filter>])
Parameters
T ERM DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated at the first date of the quarter in the current context.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The filter expression has restrictions described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Quarter Start Inventory Value' of the
product inventory.
=
OPENINGBALANCEQUARTER(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateT
ime[DateKey])
See also
OPENINGBALANCEYEAR function
OPENINGBALANCEMONTH function
Time intelligence functions
CLOSINGBALANCEQUARTER function
OPENINGBALANCEYEAR
8/25/2021 • 2 minutes to read
Evaluates the expression at the first date of the year in the current context.
Syntax
OPENINGBALANCEYEAR(<expression>,<dates>[,<filter>][,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A scalar value that represents the expression evaluated at the first date of the year in the current context.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
The filter expression has restrictions described in the topic, CALCULATE function.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'Year Start Inventory Value' of the product
inventory.
=
OPENINGBALANCEYEAR(SUMX(ProductInventory,ProductInventory[UnitCost]*ProductInventory[UnitsBalance]),DateTime
[DateKey])
See also
OPENINGBALANCEQUARTER function
OPENINGBALANCEMONTH function
Time intelligence functions
CLOSINGBALANCEYEAR function
PARALLELPERIOD
8/25/2021 • 2 minutes to read
Returns a table that contains a column of dates that represents a period parallel to the dates in the specified
dates column, in the current context, with the dates shifted a number of intervals either forward in time or back
in time.
Syntax
PARALLELPERIOD(<dates>,<number_of_intervals>,<interval>)
Parameters
T ERM DEF IN IT IO N
interval The interval by which to shift the dates. The value for
interval can be one of the following: year , quarter ,
month .
Return value
A table containing a single column of date values.
Remarks
This function takes the current set of dates in the column specified by dates , shifts the first date and the
last date the specified number of intervals, and then returns all contiguous dates between the two shifted
dates. If the interval is a partial range of month, quarter, or year then any partial months in the result are
also filled out to complete the entire interval.
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
If the number specified for number_of_inter vals is positive, the dates in dates are moved forward in
time; if the number is negative, the dates in dates are shifted back in time.
The inter val parameter is an enumeration, not a set of strings; therefore values should not be enclosed
in quotation marks. Also, the values: year , quarter , month should be spelled in full when using them.
The result table includes only dates that appear in the values of the underlying table column.
The PARALLELPERIOD function is similar to the DATEADD function except that PARALLELPERIOD always
returns full periods at the given granularity level instead of the partial periods that DATEADD returns. For
example, if you have a selection of dates that starts at June 10 and finishes at June 21 of the same year,
and you want to shift that selection forward by one month then the PARALLELPERIOD function will return
all dates from the next month (July 1 to July 31); however, if DATEADD is used instead, then the result will
include only dates from July 10 to July 21.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the previous year sales for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), PARALLELPERIOD(DateTime[DateKey],-1,year))
See also
Time intelligence functions
Date and time functions
DATEADD function
PREVIOUSDAY
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates representing the day that is previous to the first date in the
dates column, in the current context.
Syntax
PREVIOUSDAY(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function determines the first date in the input parameter, and then returns all dates corresponding to
the day previous to that first date. For example, if the first date in the dates argument refers to June 10,
2009; this function returns all dates equal to June 9, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE function.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'previous day sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), PREVIOUSDAY('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
PREVIOUSMONTH function
PREVIOUSQUARTER function
PREVIOUSYEAR function
PREVIOUSMONTH
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates from the previous month, based on the first date in the dates
column, in the current context.
Syntax
PREVIOUSMONTH(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function returns all dates from the previous month, using the first date in the column used as input.
For example, if the first date in the dates argument refers to June 10, 2009, this function returns all dates
for the month of May, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'previous month sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), PREVIOUSMONTH('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
PREVIOUSDAY
PREVIOUSQUARTER
PREVIOUSYEAR
PREVIOUSQUARTER
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates from the previous quarter, based on the first date in the dates
column, in the current context.
Syntax
PREVIOUSQUARTER(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column of date values.
Remarks
This function returns all dates from the previous quarter, using the first date in the input column. For
example, if the first date in the dates argument refers to June 10, 2009, this function returns all dates for
the quarter January to March, 2009.
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'previous quarter sales' for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), PREVIOUSQUARTER('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
PREVIOUSMONTH
PREVIOUSDAY
PREVIOUSYEAR
PREVIOUSYEAR
8/25/2021 • 2 minutes to read
Returns a table that contains a column of all dates from the previous year, given the last date in the dates
column, in the current context.
Syntax
PREVIOUSYEAR(<dates>[,<year_end_date>])
Parameters
T ERM DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A table containing a single column of date values.
Remarks
This function returns all dates from the previous year given the latest date in the input parameter. For
example, if the latest date in the dates argument refers to the year 2009, then this function returns all
dates for the year of 2008, up to the specified year_end_date .
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is ignored.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the previous year sales for Internet sales.
= CALCULATE(SUM(InternetSales_USD[SalesAmount_USD]), PREVIOUSYEAR('DateTime'[DateKey]))
See also
Time intelligence functions
Date and time functions
PREVIOUSMONTH
PREVIOUSDAY
PREVIOUSQUARTER
SAMEPERIODLASTYEAR
8/25/2021 • 2 minutes to read
Returns a table that contains a column of dates shifted one year back in time from the dates in the specified
dates column, in the current context.
Syntax
SAMEPERIODLASTYEAR(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A single-column table of date values.
Remarks
The dates argument can be any of the following:
A reference to a date/time column,
A table expression that returns a single column of date/time values,
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
The dates returned are the same as the dates returned by this equivalent formula:
DATEADD(dates, -1, year)
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the previous year sales of Reseller sales.
= CALCULATE(SUM(ResellerSales_USD[SalesAmount_USD]), SAMEPERIODLASTYEAR(DateTime[DateKey]))
See also
Time intelligence functions
Date and time functions
PREVIOUSYEAR
PARALLELPERIOD
STARTOFMONTH
8/25/2021 • 2 minutes to read
Returns the first date of the month in the current context for the specified column of dates.
Syntax
STARTOFMONTH(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the start of the month, for the current context.
= STARTOFMONTH(DateTime[DateKey])
See also
Date and time functions
Time intelligence functions
STARTOFYEAR
STARTOFQUARTER
STARTOFQUARTER
8/25/2021 • 2 minutes to read
Returns the first date of the quarter in the current context for the specified column of dates.
Syntax
STARTOFQUARTER(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the start of the quarter, for the current context.
= STARTOFQUARTER(DateTime[DateKey])
See also
Date and time functions
Time intelligence functions
STARTOFYEAR
STARTOFMONTH
STARTOFYEAR
8/25/2021 • 2 minutes to read
Returns the first date of the year in the current context for the specified column of dates.
Syntax
STARTOFYEAR(<dates>)
Parameters
T ERM DEF IN IT IO N
Return value
A table containing a single column and single row with a date value.
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that returns the start of the year, for the current context.
= STARTOFYEAR(DateTime[DateKey])
See also
Date and time functions
Time intelligence functions
STARTOFQUARTER
STARTOFMONTH
TOTALMTD
8/25/2021 • 2 minutes to read
Evaluates the value of the expression for the month to date, in the current context.
Syntax
TOTALMTD(<expression>,<dates>[,<filter>])
Parameters
PA RA M ET ER DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated for the dates in the current month-to-date, given the
dates in dates .
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
The filter expression has restrictions described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'month running total' or 'month running
sum' for Internet sales.
= TOTALMTD(SUM(InternetSales_USD[SalesAmount_USD]),DateTime[DateKey])
See also
ALL
CALCULATE
TOTALYTD
TOTALQTD
TOTALQTD
8/25/2021 • 2 minutes to read
Evaluates the value of the expression for the dates in the quarter to date, in the current context.
Syntax
TOTALQTD(<expression>,<dates>[,<filter>])
Parameters
PA RA M ET ER DEF IN IT IO N
Return value
A scalar value that represents the expression evaluated for all dates in the current quarter to date, given the
dates in dates .
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
The filter expression has restrictions described in the topic, CALCULATE.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'quarter running total' or 'quarter running
sum' for Internet sales.
= TOTALQTD(SUM(InternetSales_USD[SalesAmount_USD]),DateTime[DateKey])
See also
ALL
CALCULATE
TOTALYTD
TOTALMTD
TOTALYTD
8/25/2021 • 2 minutes to read
Syntax
TOTALYTD(<expression>,<dates>[,<filter>][,<year_end_date>])
Parameters
PA RA M ET ER DEF IN IT IO N
year_end_date (optional) A literal string with a date that defines the year-
end date. The default is December 31.
Return value
A scalar value that represents the expression evaluated for the current year-to-date dates .
Remarks
The dates argument can be any of the following:
A reference to a date/time column.
A table expression that returns a single column of date/time values.
A Boolean expression that defines a single-column table of date/time values.
Constraints on Boolean expressions are described in the topic, CALCULATE.
The filter expression has restrictions described in the topic, CALCULATE.
The year_end_date parameter is a string literal of a date, in the same locale as the locale of the client
where the workbook was created. The year portion of the date is not required and is ignored. For
example, the following formula specifies a (fiscal) year_end_date of 6/30 in an EN-US locale workbook.
In this example, year_end_date can be specified as "6/30", "Jun 30", "30 June", or any string that resolves
to a month/day. However, it is recommended you specify year_end_date using "month/day" (as shown) to
ensure the string resolves to a date.
This function is not supported for use in DirectQuery mode when used in calculated columns or row-
level security (RLS) rules.
Example
The following sample formula creates a measure that calculates the 'year running total' or 'year running sum'
for Internet sales.
= TOTALYTD(SUM(InternetSales_USD[SalesAmount_USD]),DateTime[DateKey])
See also
ALL
CALCULATE
DATESYTD
TOTALMTD
TOTALQTD
Statements
8/25/2021 • 2 minutes to read
In this category
STAT EM EN T DESC RIP T IO N
DEFINE (Keyword) Defines entities that exist only for the duration of
a DAX query.
A keyword that defines entities that can be applied to one or more EVALUATE statements of a DAX query.
Syntax
DEFINE { <entity> [<name>] = <expression> }
Arguments
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value. The
expression can use any of the defined entities. The
expression must return a table. If a scalar value is required,
wrap the scalar inside a ROW() function to produce a table.
Remarks
Entities can be variables, measures, tables, and columns.
Definitions typically precede the EVALUATE statement and are valid for all EVALUATE statements.
Definitions can reference other definitions that appear before or after the current definition.
Definitions exist only for the duration of the query.
See also
DAX queries
ORDER BY
VAR
EVALUATE
8/25/2021 • 2 minutes to read
Syntax
EVALUATE <table>
Parameters
T ERM DEF IN IT IO N
Return value
The result of a table expression.
Remarks
A query can contain multiple EVALUATE statements.
Example
EVALUATE(
'Internet Sales'
)
Returns all rows and columns from the Internet Sales table, as a table.
See also
DAX queries
DEFINE
ORDER BY
ORDER BY
8/25/2021 • 2 minutes to read
Defines the sort order of query results returned by an EVALUATE statement in a DAX query.
Syntax
ORDER BY {<expression> [{ASC | DESC}]}
Arguments
T ERM DEF IN IT IO N
Return value
The result of an EVALUATE statement in ascending (ASC) or descending (DESC) order.
Example
EVALUATE(
'Internet Sales'
)
ORDER BY
'Internet Sales'[Order Date]
Returns all rows and columns from the Internet Sales table, ordered by Order Date, as a table.
See also
DAX queries
EVALUATE
VAR
8/25/2021 • 2 minutes to read
Stores the result of an expression as a named variable, which can then be passed as an argument to other
measure expressions. Once resultant values have been calculated for a variable expression, those values do not
change, even if the variable is referenced in another expression.
Syntax
VAR <name> = <expression>
Parameters
T ERM DEF IN IT IO N
Return value
A named variable containing the result of the expression argument.
Remarks
An expression passed as an argument to VAR can contain another VAR declaration.
When referencing a variable:
Measures cannot refer to variables defined outside the measure expression, but can refer to functional
scope variables defined within the expression.
Variables can refer to measures.
Variables can refer to previously defined variables.
Columns in table variables cannot be referenced via TableName[ColumnName] syntax.
For best practices when using VAR, see Use variables to improve your DAX formulas.
Example
To calculate a percentage of year-over-year growth without using a variable, you could create three separate
measures. This first measure calculates Sum of Sales Amount:
Sum of SalesAmount = SUM(SalesTable[SalesAmount])
A second measure calculates the sales amount for the previous year:
SalesAmount PreviousYear =
CALCULATE([Sum of SalesAmount],
SAMEPERIODLASTYEAR(Calendar[Date])
)
You can then create a third measure that combines the other two measures to calculate a growth percentage.
Notice the Sum of SalesAmount measure is used in two places; first to determine if there is a sale, then again to
calculate a percentage.
By using a variable, you can create a single measure that calculates the same result:
VAR SalesLastYear =
CALCULATE ( SUM ( SalesTable[SalesAmount] ), SAMEPERIODLASTYEAR ( 'Calendar'[Date] ) )
By using a variable, you can get the same outcome, but in a more readable way. In addition, the result of the
expression is stored in the variable upon declaration. It doesn't have to be recalculated each time it is used, as it
would without using a variable. This can improve the measure's performance.
DAX glossary
9/15/2021 • 6 minutes to read
Analytic query
Power BI visuals query a data model by using an analytic query. An analytic query strives to reduce potentially
large data volumes and model complexities using three distinct phases: Filter, group and summarize. An analytic
query is created automatically when fields are assigned to the wells of report visuals. Report authors can control
the behavior of field assignments by renaming fields, modifying the summarization technique, or disabling
summarization to achieve grouping. At report design time, filters can be added to the report, a report page, or a
visual. In reading view, filters can be modified in the Filters pane, or by interactions with slicers and other
visuals (cross-filtering).
BLANK
DAX defines the absence of a value as BLANK. It's the equivalent of SQL NULL, but it doesn't behave exactly the
same. It's more closely aligned to Excel and how it defines an empty cell. BLANK is evaluated as zero or an
empty string when combined with other operations. For example, BLANK + 20 = 20. Always use capital letters;
the plural is BLANKs, with a lowercase "s".
Calculated column
A model calculation used to add a column to a tabular model by writing a DAX formula. The formula must
return a scalar value, and it's evaluated for each row in the table. A calculated column can be added to an Import
or DirectQuery storage mode table.
Calculated measure
In tabular modeling, there's no such concept as a calculated measure. Use measure instead. The word calculated
is used to describe calculated tables and calculated columns. It distinguishes them from tables and columns that
originate from Power Query. Power Query doesn't have the concept of a measure.
Calculated table
A model calculation used to add a table to a tabular model by writing a DAX formula. The formula must return a
table object. It results in a table that uses Import storage mode.
Calculation
A deliberate process that transforms one or more inputs into one or more results. In a tabular data model, a
calculation can be a model object; either a calculated table, calculated column, or measure.
Context
Describes the environment in which a DAX formula is evaluated. There are two types of context: Row context and
filter context. Row context represents the "current row", and is used to evaluate calculated column formulas and
expressions used by table iterators. Filter context is used to evaluate measures, and it represents filters applied
directly to model columns and filters propagated by model relationships.
DAX
Data Analysis Expressions (DAX) language is a formula language for Power Pivot in Excel, Power BI, Azure
Analysis Services, and tabular modeling in SQL Server Analysis Services. You can also use DAX to add data
model calculations and define row-level security (RLS) rules.
Dynamic security
When row-level security (RLS) rules are enforced by using the identity of the report user. Rules filter model
tables by using the user's account name, which can be done with the USERNAME or USERPRINCIPALNAME
functions. See Row-level security.
Expression
A unit of DAX logic that's evaluated and returns a result. Expressions can declare variables in which case they're
assigned a sub-expression and must include a RETURN statement that outputs a final expression. Expressions
are constructed by using model objects (tables, columns, or measures), functions, operators, or constants.
Field
Data model resource presented in the Fields pane. Fields are used to configure report filters and visuals. Fields
consist of model columns, hierarchy levels, and measures.
Formula
One or more DAX expressions used to define a model calculation. Inner expressions are called sub-expressions.
Plural is formulas.
Function
DAX functions have arguments that allow passing in parameters. Formulas can use many function calls, possibly
nesting functions within other functions. In a formula, function names must be followed by parentheses. Within
the parentheses, parameters are passed in.
Implicit measure
An automatically generated calculation achieved by configuring a Power BI visual to summarize column values.
Numeric columns support the greatest range of summarization, including: Sum, Average, Minimum, Maximum,
Count (Distinct), Count, Standard deviation, Variance, or Median. Columns of other data types can be
summarized, too. Text columns can be summarized by using: First (alphabetically), Last (alphabetically), Count
(Distinct), or Count. Date columns can be summarized by using: Earliest, Latest, Count (Distinct), or Count.
Boolean columns can be summarized by using: Count (Distinct), or Count.
Iterator function
A DAX function that enumerates all rows of a given table and evaluate a given expression for each row. It
provides flexibility and control over how model calculations summarize data.
MDX
Multidimensional Expressions (MDX) language is a formula language for SQL Server Analysis Services
multidimensional models (also known as cubes). MDX can be used to query tabular models, however it can't
define implicit measures. It can only query measures that are already defined in the model.
Measure
A calculation that achieves summarization. Measures are either implicit or explicit. An explicit measure is a
calculation added to a tabular data model by writing a DAX formula. A measure formula must return a scalar
value. In the Fields pane, explicit measures are adorned with a calculator icon. Explicit measures are required
when the model is queried by using Multidimensional Expressions (MDX), as is the case when using Analyze in
Excel. An explicit measure is commonly just called a measure.
Measure group
A model table that contains at least one measure, and has no hierarchies or visible columns. In the Fields pane,
each measure group is adorned with a multi-calculator icon. Measure groups are listed together at the top of the
Fields pane, and sorted alphabetically by name.
Model calculation
A named formula that's used to add a calculated table, calculated column, or measure to a tabular data model.
Its structure is <NAME> = <FORMULA>. Most calculations are added by data modelers in Power BI Desktop,
but measures can also be added to a live connection report. See Report measures.
Quick measures
A feature in Power BI Desktop that eliminates the need to write DAX formulas for commonly defined measures.
Quick measures include average per category, rank, and difference from baseline.
Report measures
Also called report-level measures. They're added to a live connection report in Power BI Desktop by writing a
DAX formula, but only for connections to Power BI models or Analysis Services tabular models.
Row-level security
Also called RLS . Design technique to restrict access to subsets of data for specific users. In a tabular model, it's
achieved by creating model roles. Roles have rules, which are DAX expressions to filter table rows.
Scalar
In DAX, a scalar is a single value. A scalar can be of any data type: Decimal, Integer, DateTime, String, Currency,
Boolean. A scalar value can be the result of an expression calculated from multiple values. For example, an
aggregation function such as MAX() returns a single maximum value from a set of values from which to
evaluate.
Summarization
An operation applied to the values of a column. See measure.
Time intelligence
Time intelligence relates to calculations over time, like year-to-date (YTD).
What-if parameter
A Power BI Desktop feature that provides the ability to accept user input through slicers. Each parameter creates
a single-column calculated table and a measure that returns a single-selected value. The measure can be used in
model calculations to respond to the user's input.
DAX operators
8/25/2021 • 6 minutes to read
The Data Analysis Expression (DAX) language uses operators to create expressions that compare values, perform
arithmetic calculations, or work with strings.
Types of operators
There are four different types of calculation operators: arithmetic, comparison, text concatenation, and logical.
Arithmetic operators
To perform basic mathematical operations such as addition, subtraction, or multiplication; combine numbers;
and produce numeric results, use the following arithmetic operators.
NOTE
The plus sign can function both as a binary operator and as a unary operator. A binary operator requires numbers on
both sides of the operator and performs addition. When you use values in a DAX formula on both sides of the binary
operator, DAX tries to cast the values to numeric data types if they are not already numbers. In contrast, the unary
operator can be applied to any type of argument. The plus symbol does not affect the type or value and is simply ignored,
whereas the minus operator creates a negative value, if applied to a numeric value.
Comparison operators
You can compare two values with the following operators. When two values are compared by using these
operators, the result is a logical value, either TRUE or FALSE.
All comparison operators except == treat BLANK as equal to number 0, empty string "", DATE(1899, 12, 30), or
FALSE. As a result, [Column] = 0 will be true when the value of [Column] is either 0 or BLANK. In contrast,
[Column] == 0 is true only when the value of [Column] is 0.
Text concatenation operator
Use the ampersand (& ) to join, or concatenate, two or more text strings to produce a single piece of text.
& (ampersand) Connects, or concatenates, two values [Region] & ", " & [City]
to produce one continuous text value
Logical operators
Use logical operators (&&) and (||) to combine expressions to produce a single result.
&& (double ampersand) Creates an AND condition between ([Region] = "France") && ([BikeBuyer]
two expressions that each have a = "yes"))
Boolean result. If both expressions
return TRUE, the combination of the
expressions also returns TRUE;
otherwise the combination returns
FALSE.
|| (double pipe symbol) Creates an OR condition between two (([Region] = "France") || ([BikeBuyer] =
logical expressions. If either expression "yes"))
returns TRUE, the result is TRUE; only
when both expressions are FALSE is
the result FALSE.
^ Exponentiation
=,==,<,>,<=,>=,<> Comparison
=5+2*3
In contrast, if you use parentheses to change the syntax, the order is changed so that 5 and 2 are added together,
and the result multiplied by 3 to produce 21.
=(5+2)*3
In the following example, the parentheses around the first part of the formula force the calculation to evaluate
the expression (3 + 0.25) first and then divide the result by the result of the expression, ( 3 - 0.25) .
In the following example, the exponentiation operator is applied first, according to the rules of precedence for
operators, and then the sign operator is applied. The result for this expression is -4.
=-2^2
To ensure that the sign operator is applied to the numeric value first, you can use parentheses to control
operators, as shown in the following example. The result for this expression is 4.
= (-2)^2
Compatibility
DAX easily handles and compares various data types, much like Microsoft Excel. However, the underlying
computation engine is based on SQL Server Analysis Services and provides additional advanced features of a
relational data store, including richer support for date and time types. Therefore, in some cases the results of
calculations or the behavior of functions may not be the same as in Excel. Moreover, DAX supports more data
types than does Excel. This section describes the key differences.
Coercing data types of operands
In general, the two operands on the left and right sides of any operator should be the same data type. However,
if the data types are different, DAX will convert them to a common data type to apply the operator in some
cases:
1. Both operands are converted to the largest possible common data type.
2. The operator is applied, if possible.
For example, suppose you have two numbers that you want to combine. One number results from a formula,
such as = [Price] * .20 , and the result may contain many decimal places. The other number is an integer that
has been provided as a string value.
In this case, DAX will convert both numbers to real numbers in a numeric format, using the largest numeric
format that can store both kinds of numbers. Then DAX will apply the multiplication.
Depending on the data-type combination, type coercion may not be applied for comparison operations. For a
complete list of data types supported by DAX, see Data types supported in tabular models and Data types in
Power BI Desktop.
Integer, Real Number, Currency, Date/time and Blank are considered numeric for comparison purposes. Blank
evaluates to zero when performing a comparison. The following data-type combinations are supported for
comparison operations.
Numeric Numeric
Boolean Boolean
String String
Other mixed data-type comparisons will return an error. For example, a formula such as ="1" > 0 returns an
error stating that DAX comparison operations do not support comparing values of type Text with values of type
Integer.
String String
Boolean Boolean
DateTime Variant
Currency Currency
See also
DAX syntax
DAX parameter-naming
DAX queries
8/25/2021 • 4 minutes to read
With DAX queries, you can query and return data defined by a table expression. Reporting clients construct DAX
queries whenever a field is placed on a report surface, or a whenever a filter or calculation is applied. DAX
queries can also be created and run in SQL Server Management Studio (SSMS) and open-source tools like DAX
Studio. DAX queries run in SSMS and DAX Studio return results as a table.
Before learning about queries, it's important you have a solid understanding of DAX basics. If you haven't
already, be sure to checkout DAX overview.
Syntax
[DEFINE { MEASURE <tableName>[<name>] = <expression> }
{ VAR <name> = <expression>}]
EVALUATE <table>
[ORDER BY {<expression> [{ASC | DESC}]}[, …]
[START AT {<value>|<parameter>} [, …]]]
Keywords
EVALUATE (Required)
At the most basic level, a DAX query is an EVALUATE statement containing a table expression. However, a query
can contain multiple EVALUATE statements.
Syntax
EVALUATE <table>
Arguments
T ERM DEF IN IT IO N
Example
EVALUATE(
'Internet Sales'
)
Returns all rows and columns from the Internet Sales table, as a table.
ORDER BY (Optional)
The optional ORDER BY keyword defines one or more expressions used to sort query results. Any expression
that can be evaluated for each row of the result is valid.
Syntax
EVALUATE <table>
[ORDER BY {<expression> [{ASC | DESC}]}[, …]
Arguments
T ERM DEF IN IT IO N
Example
EVALUATE(
'Internet Sales'
)
ORDER BY
'Internet Sales'[Order Date]
Returns all rows and columns from the Internet Sales table, ordered by Order Date, as a table.
START AT (Optional)
The optional START AT keyword is used inside an ORDER BY clause. It defines the value at which the query
results begin.
Syntax
EVALUATE <table>
[ORDER BY {<expression> [{ASC | DESC}]}[, …]
[START AT {<value>|<parameter>} [, …]]]
Arguments
T ERM DEF IN IT IO N
START AT arguments have a one-to-one correspondence with the columns in the ORDER BY clause. There can be
as many arguments in the START AT clause as there are in the ORDER BY clause, but not more. The first
argument in the START AT defines the starting value in column 1 of the ORDER BY columns. The second
argument in the START AT defines the starting value in column 2 of the ORDER BY columns within the rows that
meet the first value for column 1.
Example
EVALUATE(
'Internet Sales'
)
ORDER BY
'Internet Sales'[Sales Order Number]
START AT "SO7000"
Returns all rows and columns from the Internet Sales table, ordered by Sales Order Number, beginning at
SO7000.
Multiple EVALUATE /ORDER BY /START AT clauses can be specified in a single query.
DEFINE (Optional)
The optional DEFINE keyword defines entities that exist only for the duration of the query. Definitions are valid
for all EVALUATE statements. Entities can be variables, measures, tables, and columns. Definitions can reference
other definitions that appear before or after the current definition. Definitions typically precede the EVALUATE
statement.
Syntax
Arguments
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value. The
expression can use any of the defined measures. The
expression must return a table. If a scalar value is required,
wrap the scalar inside a ROW() function to produce a table.
Example
DEFINE
MEASURE 'Internet Sales'[Internet Total Sales] = SUM('Internet Sales'[Sales Amount])
EVALUATE
SUMMARIZECOLUMNS
(
'Date'[Calendar Year],
TREATAS({2013, 2014}, 'Date'[Calendar Year]),
"Total Sales", [Internet Total Sales],
"Combined Years Total Sales", CALCULATE([Internet Total Sales], ALLSELECTED('Date'[Calendar Year]))
)
ORDER BY [Calendar Year]
Returns the calculated total sales for years 2013 and 2014, and combined calculated total sales for years 2013
and 2014, as a table. The measure in the DEFINE statement, Internet Total Sales, is used in both Total Sales and
Combined Years Total Sales expressions.
IMPORTANT
Parameters defined in the parameters section and not used in the <STATEMENT> element generate an error response in
XMLA. Parameters used and not defined in the <Parameters> element generate an error response in XMLA.
See also
FILTER
SUMMARIZECOLUMNS
TREATAS
VAR
DAX parameter-naming conventions
8/25/2021 • 2 minutes to read
Parameter names are standardized in DAX reference to facilitate the usage and understanding of the functions.
Parameter names
T ERM DEF IN IT IO N
expression Any DAX expression that returns a single scalar value, where
the expression is to be evaluated multiple times (for each
row/context).
value Any DAX expression that returns a single scalar value where
the expression is to be evaluated exactly once before all
other operations.
This article describes syntax and requirements for the DAX formula expression language.
Syntax requirements
A DAX formula always starts with an equal sign (=). After the equals sign, you can provide any expression that
evaluates to a scalar, or an expression that can be converted to a scalar. These include the following:
A scalar constant, or expression that uses a scalar operator (+,-,*,/,>=,...,&&, ...)
References to columns or tables. The DAX language always uses tables and columns as inputs to
functions, never an array or arbitrary set of values.
Operators, constants, and values provided as part of an expression.
The result of a function and its required arguments. Some DAX functions return a table instead of a scalar,
and must be wrapped in a function that evaluates the table and returns a scalar; unless the table is a
single column, single row table, then it is treated as a scalar value.
Most DAX functions require one or more arguments, which can include tables, columns, expressions, and
values. However, some functions, such as PI, do not require any arguments, but always require
parentheses to indicate the null argument. For example, you must always type PI(), not PI. You can also
nest functions within other functions.
Expressions. An expression can contain any or all of the following: operators, constants, or references to
columns.
For example, the following are all valid formulas.
F O RM UL A RESULT
=3 3
= 'Sales'[Amount] If you use this formula within the Sales table, you will get the
value of the column Amount in the Sales table for the
current row.
= (0.03 *[Amount]) Three percent of the value in the Amount column of the
current table.
=0.03 * [Amount]
Although this formula can be used to calculate a percentage,
the result is not shown as a percentage unless you apply
formatting in the table.
Formulas can behave differently depending on how they are used. You must always be aware of the context and
how the data that you use in the formula is related to other data that might be used in the calculation.
Naming requirements
A data model often contains multiple tables. Together the tables and their columns comprise a database stored
in the in-memory analytics engine (VertiPaq). Within that database, all tables must have unique names. The
names of columns must also be unique within each table. All object names are case-insensitive; for example, the
names SALES and Sales would represent the same table.
Each column and measure you add to an existing data model must belong to a specific table. You specify the
table that contains the column either implicitly, when you create a calculated column within a table, or explicitly,
when you create a measure and specify the name of the table where the measure definition should be stored.
When you use a table or column as an input to a function, you must generally qualify the column name. The
fully qualified name of a column is the table name, followed by the column name in square brackets: for
examples, 'U.S. Sales'[Products]. A fully qualified name is always required when you reference a column in the
following contexts:
As an argument to the function, VALUES
As an argument to the functions, ALL or ALLEXCEPT
In a filter argument for the functions, CALCULATE or CALCULATETABLE
As an argument to the function, RELATEDTABLE
As an argument to any time intelligence function
An unqualified column name is just the name of the column, enclosed in brackets: for example, [Sales Amount].
For example, when you are referencing a scalar value from the same row of the current table, you can use the
unqualified column name.
If the name of a table contains spaces, reserved keywords, or disallowed characters, you must enclose the table
name in single quotation marks. You must also enclose table names in quotation marks if the name contains any
characters outside the ANSI alphanumeric character range, regardless of whether your locale supports the
character set or not. For example, if you open a workbook that contains table names written in Cyrillic
characters, such as 'Таблица', the table name must be enclosed in quotation marks, even though it does not
contain spaces.
NOTE
To make it easier to enter the fully qualified names of columns, use the AutoComplete feature in the formula editor.
Tables
Table names are required whenever the column is from a different table than the current table. Table
names must be unique within the database.
Table names must be enclosed in single quotation marks if they contain spaces, other special characters
or any non-English alphanumeric characters.
Measures
Measure names must always be in brackets.
Measure names can contain spaces.
Each measure name must be unique within a model. Therefore, the table name is optional in front of a
measure name when referencing an existing measure. However, when you create a measure you must
always specify a table where the measure definition will be stored.
Columns
Column names must be unique in the context of a table; however, multiple tables can have columns with the
same names (disambiguation comes with the table name).
In general, columns can be referenced without referencing the base table that they belong to, except when there
might be a name conflict to resolve or with certain functions that require column names to be fully qualified.
Reserved keywords
If the name that you use for a table is the same as an Analysis Services reserved keyword, an error is raised, and
you must rename the table. However, you can use keywords in object names if the object name is enclosed in
brackets (for columns) or quotation marks (for tables).
NOTE
Quotation marks can be represented by several different characters, depending on the application. If you paste formulas
from an external document or Web page, make sure to check the ASCII code of the character that is used for opening and
closing quotes, to ensure that they are the same. Otherwise DAX may be unable to recognize the symbols as quotation
marks, making the reference invalid.
Special characters
The following characters and character types are not valid in the names of tables, columns, or measures:
Leading or trailing spaces; unless the spaces are enclosed by name delimiters, brackets, or single
apostrophes.
Control characters
The following characters that are not valid in the names of objects:
.,;':/\*|?&%$!+=()[]{}<>
Examples of object names
The following table shows examples of some object names:
O B JEC T T Y P ES EXA M P L ES C O M M EN T
Fully qualified column name Sales[Amount] The table name precedes the column
name, and the column name is
enclosed in brackets.
Fully qualified measure name Sales[Profit] The table name precedes the measure
name, and the measure name is
enclosed in brackets. In certain
contexts, a fully qualified name is
always required.
O B JEC T T Y P ES EXA M P L ES C O M M EN T
Fully qualified column in table with 'Canada Sales'[Qty] The table name contains spaces, so it
spaces must be surrounded by single quotes.
Other restrictions
The syntax required for each function, and the type of operation it can perform, varies greatly depending on the
function. In general, however, the following rules apply to all formulas and expressions:
DAX formulas and expressions cannot modify or insert individual values in tables.
You cannot create calculated rows by using DAX. You can create only calculated columns and measures.
When defining calculated columns, you can nest functions to any level.
DAX has several functions that return a table. Typically, you use the values returned by these functions as
input to other functions, which require a table as input.
O P ERATO R T Y P E SY M B O L A N D USE
- (subtraction/
sign)
* (multiplication)
/ (division)
^ (exponentiation)
|| (or)
Data types
You do not need to cast, convert, or otherwise specify the data type of a column or value that you use in a DAX
formula. When you use data in a DAX formula, DAX automatically identifies the data types in referenced
columns and of the values that you type in, and performs implicit conversions where necessary to complete the
specified operation.
For example, if you try to add a number to a date value, the engine will interpret the operation in the context of
the function, and convert the numbers to a common data type, and then present the result in the intended
format, a date.
However, there are some limitations on the values that can be successfully converted. If a value or a column has
a data type that is incompatible with the current operation, DAX returns an error. Also, DAX does not provide
functions that let you explicitly change, convert, or cast the data type of existing data that you have imported
into a data model.
IMPORTANT
DAX does not support use of the variant data type. Therefore, when you load or import data into a data model, it's
expected the data in each column is generally of a consistent data type.
Some functions return scalar values, including strings, whereas other functions work with numbers, both
integers and real numbers, or dates and times. The data type required for each function is described in the
section, DAX functions.
You can use tables containing multiple columns and multiple rows of data as the argument to a function. Some
functions also return tables, which are stored in memory and can be used as arguments to other functions.
EVALUATE
FILTER (
FactInternetSales,
[OrderDate] > dt"2015-1-9T02:30:00" && [OrderDate] < dt"2015-12-31T11:59:59"
)
NOTE
The DAX date and datetime-typed literal format is not supported in all versions of Power BI Desktop, Analysis Services,
and Power Pivot in Excel. New and updated DAX functionality are typically first introduced in Power BI Desktop and then
later included in Analysis Services and Power Pivot in Excel.