This function returns
a value corresponding to a timestamp of the first millisecond of the
quarter containing date. The
default output format will be the DateFormat set in the script.
period_no is an integer, where the value
0 indicates the quarter which contains date.
Negative values in period_no indicate
preceding quarters and positive values indicate succeeding quarters.
first_month_of_year
If you
want to work with (fiscal) years not starting in January, indicate
a value between 2 and 12 in first_month_of_year.
These examples use the date format DD/MM/YYYY. The date format is specified in the SET DateFormat statement at the top of your data load script. Change the format in the examples to suit your requirements.
Scripting examples
Example
Result
quarterstart('29/10/2005')
Returns 01/10/2005.
quarterstart('29/10/2005', -1 )
Returns
01/07/2005.
quarterstart('29/10/2005', 0, 3)
Returns 01/09/2005.
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.
This example finds the first day in the quarter of each invoice date in the table, where the first month in the year is specified as month 3.
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 *,
QuarterStart(InvDate, 0, 3) AS QtrStart
Resident TempTable;
Drop table TempTable;
The resulting table contains the original dates and a column with the return value of the quarterstart() function. You can display the full timestamp by specifying the formatting in the properties panel.
Results table
InvDate
QtrStart
28/03/2012
01/03/2012
10/12/2012
01/12/2012
5/2/2013
01/12/2012
31/3/2013
01/03/2013
19/5/2013
01/03/2013
15/9/2013
01/09/2013
11/12/2013
01/12/2013
2/3/2014
01/03/2014
14/5/2014
01/03/2014
13/6/2014
01/06/2014
7/7/2014
01/06/2014
4/8/2014
01/06/2014
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!