Qlik Community

Ask a Question

Qlik Design Blog

All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.

May 18th, Changes to the way you login: using email vs. username. READ DETAILS/WATCH VIDEO

QlikView has an intelligent algorithm to recognize dates independently of which region you are in. In most cases, you will have no problems loading them. It just works and you do not need to think about it. However, in some cases dates are not properly recognized and then you need to add some code in the script to make it work.


Dual dates.jpgFirst of all – there are no data types in QlikView. Instead QlikView uses dual data storage for all field values; every field value is represented by a string and – if applicable – a number. The task of the developer is to make sure that QlikView recognizes the date correctly so that both a textual and a numeric part of the date are created.


The numeric part of a date is a serial number (same as Excel), i.e. a number around 41000 for dates in the year 2012.


Here are some tips that will help you load dates correctly and hopefully help you better understand how the date handling works.


  1. Use the interpretation functions
    If you have the date as text you may need to use an interpretation function, e.g. Date#() or Timestamp#().

  2. Nest functions
    If you want to display the date a specific way, you may need to nest an interpretation function inside a formatting function, e.g. Date(Date#(DateField, 'YYYYMMDD'), 'M/D/YY').

  3. Use the MakeDate function
    If you have Year, Month and Day as separate fields, use the MakeDate() function to create a date serial number.

  4. Use the rounding functions
    If you have a timestamp and you want a date, you should probably use a rounding function, e.g. Date(Floor(Timestamp#(DateTimeField, 'YYYYMMDD hh:mm:ss')), 'M/D/YY').

  5. Use the numeric value in variables
    If you want to use the variable for comparisons, it is simpler to use the date serial number rather than the textual representation, e.g. Let vToday = Num( Today() ).

  6. Use combination fields, e.g. Year and Month as one field
    It is often practical to display both year and month in one field, e.g. Date(MonthStart(DateField),'YYYY-MMM')

  7. Use the Dual function
    If you want more complicated combinations of a string with an associated numeric value, you can do almost anything using the Dual() function.

  8. Use the Alt function for fields with mixed date formats:
    If you have a field with mixed date formats, you can resolve them using the Alt() function.


For a more elaborate description of these tips, see the technical brief on QlikView dates.



Champion III
Champion III

nice ...simple

Contributor II
Contributor II

While this is a bit old now, and I'm using Qlik Sense, this is useful.

I am troubled by "tries to" and "in most cases".  The thing about Qlik is it usually fails gracefully.  Meaning, I don't always know if there is an error in my logic until further down the line.

It seems, when working with dates at least, always use one of the above casting or date methods to put your value into a known (and thus documented) state before trying to use it.  Never assume.