DATESYTD DAX Function (Time Intelligence) Context Transition
Returns a set of dates in the year up to the last date visible in the filter context.
Syntax
| Parameter | Attributes | Description |
|---|---|---|
| Dates |
The name of a column containing dates or a one column table containing dates. |
|
| YearEndDate | Optional |
End of year date. |
Return values
A table containing a single column of date values.
Notes
In order to use any time intelligence calculation, you need a well-formed date table. The Date table must satisfy the following requirements:
- All dates need to be present for the years required. The Date table must always start on January 1 and end on December 31, including all the days in this range. If the report only references fiscal years, then the date table must include all the dates from the first to the last day of a fiscal year. For example, if the fiscal year 2008 starts on July 1, 2007, then the Date table must include all the days from July 1, 2007 to June 30, 2008.
- There needs to be a column with a DateTime or Date data type containing unique values. This column is usually called Date. Even though the Date column is often used to define relationships with other tables, this is not required. Still, the Date column must contain unique values and should be referenced by the Mark as Date Table feature. In case the column also contains a time part, no time should be used – for example, the time should always be 12:00 am.
- The Date table must be marked as a date table in the model, in case the relationship between the Date table and any other table is not based on the Date.
Remarks
The dates argument can be any of the following:
- A reference to a date/time column. Only in this case a context transition applies because the column reference is replaced by
- CALCULATETABLE ( DISTINCT ( <Dates> ) )
- 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.
The result table includes only dates that exist in the dates column.
The syntax:
DATESYTD ( <Dates>[, <YearEndDate>] )
corresponds to:
DATESBETWEEN (
<Dates>,
STARTOFYEAR ( LASTDATE ( <Dates> )[, <YearEndDate>] ),
LASTDATE ( <Dates> )
)
» 2 related functions
Examples
-- DATESYTD returns the dates from the first of January of the currently selected date
EVALUATE
CALCULATETABLE (
DATESYTD ( 'Date'[Date] ),
'Date'[Date] = DATE ( 2007, 5, 12 )
)
ORDER BY [Date] ASC
| Date |
|---|
| 2007-01-01 |
| 2007-01-02 |
| … |
| 2007-05-11 |
| 2007-05-12 |
-- If the selection contains larger periods, it returns the YTD using
-- the end of the entire period.
-- The result is always a single-row table.
EVALUATE
CALCULATETABLE (
DATESYTD ( 'Date'[Date] ),
'Date'[Date] >= DATE ( 2007, 2, 5 )
&& 'Date'[Date] <= DATE ( 2007, 5, 12 )
)
ORDER BY [Date] ASC
| Date |
|---|
| 2007-01-01 |
| 2007-01-02 |
| … |
| 2007-05-11 |
| 2007-05-12 |
-- All time intelligence function are designed to return a table
-- to be easily used in CALCULATE as a filter.
EVALUATE
{
CALCULATE (
CALCULATE (
[Sales Amount],
DATESYTD ( 'Date'[Date] ) -- 2007-01-01 : 2007-05-12
),
'Date'[Date] = DATE ( 2007, 5, 12 )
)
}
| Value |
|---|
| 4,038,742.76 |
-- This example shows the sales in the current and both the
-- quarter-to-date and year-to-date sales.
DEFINE
MEASURE Sales[Sales QTD] =
CALCULATE (
[Sales Amount],
DATESQTD ( 'Date'[Date] )
)
MEASURE Sales[Sales YTD] =
CALCULATE (
[Sales Amount],
DATESYTD ( 'Date'[Date] )
)
EVALUATE
SUMMARIZECOLUMNS (
'Date'[Calendar Year Month Number],
'Date'[Calendar Year Month],
"Sales Amount", [Sales Amount],
"Sales QTD", [Sales QTD],
"Sales YTD", [Sales YTD]
)
ORDER BY [Calendar Year Month Number]
| Calendar Year Month Number | Calendar Year Month | Sales Amount | Sales QTD | Sales YTD |
|---|---|---|---|---|
| 200701 | 2007-01-01 | 794,248.24 | 794,248.24 | 794,248.24 |
| 200702 | 2007-02-01 | 891,135.91 | 1,685,384.15 | 1,685,384.15 |
| 200703 | 2007-03-01 | 961,289.24 | 2,646,673.39 | 2,646,673.39 |
| 200704 | 2007-04-01 | 1,128,104.82 | 1,128,104.82 | 3,774,778.20 |
| … | … | … | … | … |
| 200909 | 2009-09-01 | 709,610.40 | 2,613,714.44 | 6,931,979.13 |
| 200910 | 2009-10-01 | 806,738.22 | 806,738.22 | 7,738,717.35 |
| 200911 | 2009-11-01 | 868,164.01 | 1,674,902.23 | 8,606,881.36 |
| 200912 | 2009-12-01 | 746,933.50 | 2,421,835.73 | 9,353,814.87 |
Related articles
Learn more about DATESYTD in the following articles:
-
Time Intelligence in Power BI Desktop
In Power BI Desktop (as of February 2016) you have to use DAX to apply calculations over dates (such as year-to-date, year-over-year, and others), but you do not have the Mark as Date Table feature. This article describes which scenarios are impacted and the possible workarounds. » Read more
-
International year_end_date for YTD functions in DAX
If you used the DATESYTD and TOTALYTD functions in DAX, you might have noticed that the optional parameter year_end_date is a string defining the last day of the year. This article describes what are the formats allowed in that parameter. » Read more
-
Year-to-date filtering weekdays in DAX
Time intelligence functions oftentimes hide an automatic ALL statement meant to make time intelligence calculations easier. This article describes this behavior and what to do in case it ends up breaking your calculation. » Read more
-
Optimizing time intelligence in DirectQuery
This article describes how to optimize time intelligence calculations with DirectQuery over SQL in Power BI by avoiding time intelligence DAX functions. » Read more
Related functions
Other related functions are:
Last update: Dec 14, 2024 » Contribute » Show contributors
Contributors: Alberto Ferrari, Marco Russo
Microsoft documentation: https://docs.microsoft.com/en-us/dax/datesytd-function-dax