The setting defines which day in January to set as reference day to define week 1. In other words, this setting prescribes how many days in week 1 must be dates within January.
Syntax:
ReferenceDay
ReferenceDay sets how many days are included in the first week of the year. ReferenceDay can be set to any value between 1 and 7. Any value outside of the 1-7 range is interpreted as the midpoint of the week (4), which is equivalent to ReferenceDay being set to 4.
If you do not select a value for the ReferenceDay setting, then the default value will show ReferenceDay=0 which will be interpreted as the midpoint of the week (4), as seen in the ReferenceDay values table below.
The ReferenceDay function is often used in combination with the following functions:
If the Qlik Senseapp is operating with unbroken weeks, the ReferenceDayvariable setting will be enforced. However, if broken weeks are being used, week 1 will begin on January 1 and terminate in conjunction with the FirstWeekDay variable setting and ignore the ReferenceDay flag.
Unless otherwise specified, the examples in this topic use the following date format: MM/DD/YYYY. The date format is specified in the SET DateFormat statement in your data load script. The default date formatting may be different in your system, due to your regional settings and other factors. You can change the formats in the examples below to suit your requirements. Or you can change the formats in your load script to match these examples. For more information, see Modifying regional settings for apps and scripts.
Default regional settings in apps are based on the user profile. These regional format settings are not related to the language displayed in the Qlik Cloud user interface. Qlik Cloud will be displayed in the same language as the browser you are using.
If you want ISO settings for weeks and week numbers, make sure to have the following in the script:
Set FirstWeekDay=0;
Set BrokenWeeks=0;
Set ReferenceDay=4; // Jan 4th is always in week 1
If you want US settings, make sure to have the following in the script:
Set FirstWeekDay=6;
Set BrokenWeeks=1;
Set ReferenceDay=1; // Jan 1st is always in week 1
Example 1 - Load script using the default value; ReferenceDay=0
Overview
Open the Data load editor and add the load script below to a new tab.
The load script contains:
The ReferenceDay variable that is set to 0.
The BrokenWeeks variable that is set to 0 which forces the app to use unbroken weeks.
A dataset of dates from the end of 2019 to the start of 2020.
Load script
SET BrokenWeeks = 0;
SET ReferenceDay = 0;
Sales:
LOAD
date,
sales,
week(date) as week,
weekday(date) as weekday
Inline [
date,sales
12/27/2019,5000
12/28/2019,6000
12/29/2019,7000
12/30/2019,4000
12/31/2019,3000
01/01/2020,6000
01/02/2020,3000
01/03/2020,6000
01/04/2020,8000
01/05/2020,5000
01/06/2020,7000
01/07/2020,3000
01/08/2020,5000
01/09/2020,9000
01/10/2020,5000
01/11/2020,7000
];
Results
Load the data and open a sheet. Create a new table and add these fields as dimensions:
date
week
weekday
Results table
date
week
weekday
12/27/2019
52
Fri
12/28/2019
52
Sat
12/29/2019
1
Sun
12/30/2019
1
Mon
12/31/2019
1
Tue
01/01/2020
1
Wed
01/02/2020
1
Thu
01/03/2020
1
Fri
01/04/2020
1
Sat
01/05/2020
2
Sun
01/06/2020
2
Mon
01/07/2020
2
Tue
01/08/2020
2
Wed
01/09/2020
2
Thu
01/10/2020
2
Fri
01/11/2020
2
Sat
Week 52 concludes on Saturday, December 28. Because ReferenceDay requires January 4 to be included in week 1, week 1 therefore begins on December 29 and concludes on Saturday, January 4.
Example - ReferenceDay variable set to 5
Overview
Open the Data load editor and add the load script below to a new tab.
The load script contains:
The ReferenceDay variable that is set to 5.
The BrokenWeeks variable that is set to 0 which forces the app to use unbroken weeks.
A dataset of dates from the end of 2019 to the start of 2020.
Load script
SET BrokenWeeks = 0;
SET ReferenceDay = 5;
Sales:
LOAD
date,
sales,
week(date) as week,
weekday(date) as weekday
Inline [
date,sales
12/27/2019,5000
12/28/2019,6000
12/29/2019,7000
12/30/2019,4000
12/31/2019,3000
01/01/2020,6000
01/02/2020,3000
01/03/2020,6000
01/04/2020,8000
01/05/2020,5000
01/06/2020,7000
01/07/2020,3000
01/08/2020,5000
01/09/2020,9000
01/10/2020,5000
01/11/2020,7000
];
Results
Load the data and open a sheet. Create a new table and add these fields as dimensions:
date
week
weekday
Results table
date
week
weekday
12/27/2019
52
Fri
12/28/2019
52
Sat
12/29/2019
53
Sun
12/30/2019
53
Mon
12/31/2019
53
Tue
01/01/2020
53
Wed
01/02/2020
53
Thu
01/03/2020
53
Fri
01/04/2020
53
Sat
01/05/2020
1
Sun
01/06/2020
1
Mon
01/07/2020
1
Tue
01/08/2020
1
Wed
01/09/2020
1
Thu
01/10/2020
1
Fri
01/11/2020
1
Sat
Week 52 concludes on Saturday, December 28. The BrokenWeeks variable forces the app to use unbroken weeks. The reference day value of 5 requires January 5 to be included in week 1.
However, this is eight days after the conclusion of week 52 of the previous year. Therefore, week 53 begins on December 29 and concludes on January 4. Week 1 begins on Sunday, January 5.
App
This term has several definitions:
A Qlik Sense or QlikView app: Apps are task-specific, purpose-built applications. Apps contain data loaded from data sources that is interpreted through visualizations.
The Qlik Sense Mobile app: A mobile app for iOS and Android devices. In the mobile app, you connect to and interact with your cloud data. You can work with your available apps.
The term dataset is sometimes synonymous with table. It can refer to the original source table, the table after undergoing transformations, or the fact and dimension tables in a data mart.
It can also refer to a logical table, where there are several instance tables and views:
Current data
History, which holds previous versions of the table
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. The information does not usually directly identify you, but it makes the site work as you expect it to and can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy & Cookie Notice
Manage Consent Preferences
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies, then some or all of these services may not function properly. These cookies do not typically store personal information enabling us to identify you, but are based on uniquely identifying your browser and internet device.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site and make it easier to navigate. For example, they help us to know which pages are the most and least popular and see how visitors move around the site. When analyzing this data it is typically done on an aggregated (anonymous) basis.
Advertising Cookies
These cookies may be set through our site by our advertising partners to build a profile of your interests and show you relevant advertisements on other sites. They do not typically store personal information enabling us to identify you, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less relevant advertising.