This function returns
a display value showing the year and lunar week number corresponding to a timestamp of the first millisecond of the first
day of the lunar week containing date. Lunar weeks in Qlik Sense are defined by counting 1 January as the first day of the week.
period_no
is an integer or expression resolving to an integer, where the value 0 indicates the lunar week which contains
date. Negative values in period_no indicate preceding lunar weeks
and positive values indicate succeeding lunar weeks.
first_week_day
An offset that may be greater than or less than zero. This changes the beginning of the year by the specified number of days and/or fractions of
a day.
Scripting examples
Example
Result
lunarweekname('12/01/2013')
Returns 2006/02.
lunarweekname('12/01/2013', -1)
Returns
2006/01.
lunarweekname('12/01/2013', 0, 1)
Returns 2006/02.
Example:
Add the example script to your app and run it. Then add the fields listed in the results column to a sheet in your app to see the result.
In this example, for each invoice date in the table, the lunar week name is created from the year in which the week lies and its associated lunar week number, shifted one week by specifying period_no as 1.
TempTable:
LOAD RecNo() as InvID, * Inline [
InvDate
28/03/2012
10/12/2012
5/2/2013
31/3/2013
19/5/2013
15/9/2013
11/12/2013
2/3/2014
14/5/2014
13/6/2014
7/7/2014
4/8/2014
];
InvoiceData:
LOAD *,
LunarWeekName(InvDate, 1) AS LWkName
Resident TempTable;
Drop table TempTable;
The resulting table contains the original dates and a column with the return value of the lunarweekname() function. You can display the full timestamp by specifying the formatting in the properties panel.
Results table
InvDate
LWkName
28/03/2012
2012/14
10/12/2012
2012/51
5/2/2013
2013/07
31/3/2013
2013/14
19/5/2013
2013/21
15/9/2013
2013/38
11/12/2013
2013/51
2/3/2014
2014/10
14/5/2014
2014/21
13/6/2014
2014/25
7/7/2014
2014/28
4/8/2014
2014/32
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!
