If you are working with fields containing date or timestamp information in your app, you can define a number of related attributes of a date, for example, year or week, and use them in your visualization.
Creating date fields in Data manager
Date fields are created automatically for all data fields recognized as a date or a timestamp when you use Add data with data profiling enabled to build your data model in Data manager, or when you click Load data in Data manager.
Information note
Date fields created in Data manager are automatically added to autoCalendar.
If the date or timestamp field is not recognized automatically, you can adjust the input format in the Data manager table editor. You can also set the display format to use in visualizations.
Which date & time fields are automatically recognized?
Date & timestamp fields will be recognized automatically based on your system locale settings. Additionally, the following formats are recognized:
M/D/YYYY h:mm
D/M/YYYY h:mm TT
M/D/YYYY
D/MM/YYYY
YYYYMMDD
YYYYMMDDhhmmss
YYYYMMDDhhmmss.fff
YYYYMMDDhhmmssK
YYYY-MM-DD
YYYY-MM-DDThh:mm:ss
YYYY-MM-DD-Thh:mm:ss.fff
YYYY-MM-DD-Thh:mm:ssK
Date & time formats
Format specifier
Description
YYYY
Year
M, MM
Month
D, DD
Day
hh
Hour
mm
Minute
ss
Second
fff
Millisecond
TT
AM or PM
K
Timezone
T
Divider between date and time. T can not be replaced with another character.
Creating date & time fields in the data load script
If you use Data load editor to build your data model, you need to create a calendar template where you define which fields to derive in the data load script. The derived date & time fields will be generated when the script is run and data is reloaded.
All date or timestamp fields in the assets panel Fields tab are marked with , and you can expand them to use the generated date & time fields. You can use them in visualizations, just like any other data field.
Date & time fields in dimensions
You can also use date & time fields when you create a dimension. The date & time fields are listed under the field that they have been generated from.
Date & time fields in expressions
You can use date & time fields in all expressions, for example when you create a measure. The date & time fields are named according to:
[field name].autoCalendar.[date & time field].
[field name] is the name of the data field that was used to generate date & time fields.
[date & time field] is the date & time field you want to use, for example, Year.
Example:
Date.autoCalendar.Year
Date & time fields in calendar measures
Calendar measures use date & time fields created in autoCalendar. Each of these date & time fields is calculated by a set analysis expression that determines whether or not data falls within the time-to-date period, or if dates are within a defined relative position to the current date. These date & time fields are relative and return results based on the current date. You can use these fields independently of calendar measures.
Calendar field date & time fields are formatted as follows:
[field name].autoCalendar.[date & time field]={[value]}
[field name] is the name of the date field used to generate date & time fields.
[data & time field] is the name of the date & time field used, for example, InYTD.
[value] is the value for the date & time field’s set analysis expression and determines which dates are included.
Example:
Date.autoCalendar.YearsAgo={1}
The following are the available date & time fields with sample values:
This date & time field determines whether or not dates are within the year-to-date range or outside the year-to-date range.
InYTD
Example
Result
Date.autoCalendar.InYTD={0}
Returns all dates that
fall in the year-to-date time range.
For example, if the current date was the 54th day of the year, the dates within the first 54 days of every year in the date field would be included.
Date.autoCalendar.InYTD={1}
Returns all dates outside
the year-to-date time range.
For example, if the current date was the 54th day of the year, all the dates after the first 54 days of every year in the date field would be included.
This date & time field determines whether or not dates are from a specific year relative to the current date.
YearsAgo
Example
Result
Date.autoCalendar.YearsAgo={0}
Returns all dates from
this year.
Date.autoCalendar.YearsAgo={1}
Returns all dates from
last year.
Date.autoCalendar.YearsAgo={8}
Returns all dates from
eight years ago.
This date & time field determines whether or not dates are within the quarter-to-date range or outside the quarter-to-date range, relative to the current date.
InQTD
Example
Result
Date.autoCalendar.InQTD={0}
Returns all dates from all quarters that are within the quarter-to-date range.
For example, if the current date was the 14th day of Quarter 1, the first 14 days of every quarter in the date field would be included.
Date.autoCalendar.InQTD={1}
Returns all dates from all quarters that are outside the current quarter-to-date range.
For example, if the current date was the 14th day of Quarter 1, all dates after the first 14 days of every quarter in the date field would be included.
This date & time field determines whether or not dates are from a specific quarter relative to the current date.
QuartersAgo
Example
Result
Date.autoCalendar.QuartersAgo={0}
Returns all dates from the current quarter.
Date.autoCalendar.QuartersAgo={1}
Returns all dates from the last quarter.
Date.autoCalendar.QuartersAgo={8}
Returns all dates from eight quarters ago.
This date & time field determines whether or not dates are from a specific quarter relative to the current date.
QuarterRelNo
Example
Result
Date.autoCalendar.QuarterRelNo={0}
Returns all dates from each instance of the current quarter.
For example, if the current date was in Quarter 4, all dates from each Quarter 4 in the date field would be included.
Date.autoCalendar.QuarterRelNo={3}
Returns all dates from each instance of the quarter two quarters prior to the current quarter.
For example, if the current date was in Quarter 4, all dates from each Quarter 1 in the date field would be included
This date & time field determines whether or not dates are within the month-to-date range or outside the month-to-date range, relative to the current date.
InMTD
Example
Result
Date.autoCalendar.InMTD={0}
Returns all dates from all months that are within the current month-to-date range.
For example, if the date was November 15, 2016, dates from the first 15 days of every month in the date field would be included.
Date.autoCalendar.InMTD={1}
Returns all dates from all months that are outside the current month-to-date range.
For example, if the date was November 15, 2016, dates after the first 15 days to the end of the month of every month in the date field would be included.
This date & time field determines whether or not dates are from a specific month relative to the current date.
MonthsAgo
Example
Result
Date.autoCalendar.MonthAgo={0}
Returns all dates from the current month.
Date.autoCalendar.MonthAgo={1}
Returns all dates from the last month.
Date.autoCalendar.MonthAgo={8}
Returns all dates from eight months ago.
This date & time field determines whether or not dates are from a specific month relative to the current date.
MonthRelNo
Example
Result
Date.autoCalendar.MonthRelNo={0}
Returns all dates from each instance of the current month.
For example, if the current month was June, all dates in every instance of June in the date field would be included.
Date.autoCalendar.MonthRelNo={1}
Returns all dates from the each instance of the previous month.
For example, if the current month was June, all dates in every instance of May in the date field would be included.
This date & time field determines whether or not dates are within the week-to-date range or outside the week-to-date range, relative to the current date.
InWTD
Example
Result
Date.autoCalendar.InWTD={0}
Returns all dates from all weeks that are within the current week-to-date range.
For example, if the current date was the third day of a week, dates from the first three days of every week in the date field would be included.
Date.autoCalendar.InWTD={1}
Returns all dates from all months that are outside the current month-to-date range.
For example, if the current date was the third day of a week, dates from the last four days of the every week in the date field would be included.
This date & time field determines whether or not dates are from a specific week relative to the current week.
WeeksAgo
Example
Result
Date.autoCalendar.WeeksAgo={0}
Returns all dates from the current week.
Date.autoCalendar.WeeksAgo={8}
Returns all dates from eight weeks ago.
This date & time field determines whether or not dates are from a specific week relative to the current date.
WeekRelNo
Example
Result
Date.autoCalendar.WeekRelNo={0}
Returns all dates from each instance of the current week.
For example, if the current week was the second week of the year, dates from the second week of every year in the date field would be included.
Date.autoCalendar.WeekRelNo={1}
Returns all dates from each instance of the previous week.
For example, if the current week was the second week of the year, dates from the first week of every year in the date field would be included.
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.
Data manager is an app component that allows you to load and manage data sources in an app. You can also preview and associate the data and perform data transformations.
A field contains values, loaded from a data source. At a basic level, a field corresponds to a column in a table. Fields are used to create dimensions and measures in visualizations.
The load script is a sequence of statements that defines what data to load and how to link the different loaded tables. It can be generated with the Data manager, or with the Data load editor, where it also can be viewed and edited.
A dimension is an entity used to categorize data in a chart. For example, the slices in a pie chart or the bars of a bar chart represent individual values in a dimension. Dimensions are often a single field with discrete values, but can also be calculated in an expression.
A dimension is a dataset in a data mart that forms part of the star schema. Dimension datasets hold the descriptive information for all related fields that are included in the fact table’s records. A few common examples of dimension datasets are Customer and Product. Since the data in a dimension dataset is often denormalized, dimension datasets have a large number of columns.
A measure is a calculation base on one ore more aggregations. For example, the sum of sales is a single aggregation, while the sum of sales divided by the count of customers is a measure based on two aggregations.
Set analysis defines an alternative set of selections in a visualization different from those in the current selection. This allows for comparative analysis.
, and you can expand them to use the generated date & time fields. You can use them in visualizations, just like any other data field.