DateMember
EAZYBI Finds the Time dimension hierarchy level member from the date.
Syntax
Time_Level_Expression.DateMember(Date_Expression)
Arguments
Time_Level_Expression | MDX expression that returns a Time dimension level. |
---|---|
Date_Expression | MDX expression that returns a date that needs to be found in the selected Time level. |
Examples
This example will return Jan 2024 based on the provided calendar date. It will work with the Time dimension default hierarchy.
[Time].[Month].DateMember('Jan 10 2024')
The following example will return the month for the particular imported date value.
[Time].[Month].Datemember([Measures].[Imported cf date])
The following example will return Jan 15, 2024 based on the provided date.
[Time].[Day].Datemember('Jan 15 2024')
The following example will return Jan 15, 2024 based on the provided date. It will work with any hierarchy from the Time dimension, as long as it has a "Day" level.
[Time].Currenthierarchy.Levels("Day").Datemember('Jan 15 2024')
The following example will return 2024 based on the provided date.
[Time].[Year].Datemember('Jan 15 2024')
It can be used with another function when creating a measure (with the correct output format) to return the start date of the period (defined in the level) of the member that is found by the DateMember function:
[Time].[Month].DateMember('Jan 15 2024').StartDate
This example will return Jan 1, 2024.
You can check DateMember used in our demo reports:
- Cumulative flow diagram for selected period where DateMember is used in the calculated measure "Cumulative flow"
- Story points burn-down by sprints for epic - in calculated measure "Work resolved in sprint"
- Version releases - Datemember is used in calculated measures "Open issues in version at release date" and "Resolved issues in version at release date"
See also
- Function CurrentDateMember
- Function Startdate