Qlik Community

Ask a Question

Support Updates Blog

Important and useful support information about end-of-product support, new service releases, and general support topics.

Join us March 10th, 7 Ways Modern Analytics Can Help You Take Smarter Action. REGISTER NOW
Digital Support
Digital Support

Hello Qlik Users!

In QlikView 12.10, there were two specific scenarios that would change the data type or formatting when running a reload with a WHERE clause:

  • The field is a date (format mm/dd/yyyy) is changed to numeric representation instead (#####)
  • The field is a float value and is changed to numeric, dropping the decimals when the number is integer. e.g. 10.00 turns into 10

An intentional change in behavior was made in QlikView 12.20 and higher that keeps the original data type/formatting from the source. If the data conversion is necessary, the script will need to be adjusted to force the conversion.

For more information on the intentional change and the reason behind it, please take a look at this article:

QlikView 12.50 reload returns different data types than 12.10(Intentional change in behavior 12.20 v...

Please let us know if you have any questions using the comments below and don’t forget to give this blog (and the article) a Like if you found it helpful!

Thank you for choosing Qlik!

Kind regards,

Qlik Digital Support



Good to know.

Is there a complete overview of all intentional changes?


For example I have 

- "Collapse All" with dynamic dimensions  in pivot tables no longer works after QV12.20 . R&D says this is a WAD. https://community.qlik.com/t5/Ideas/Pivot-table-with-dynamic-Dimension-Collapse-does-not-work-as/idi...


- Thousand Seperator is no longer taken from Windows Server Settings. Worked in QV11.20.  R&D says this is a WAD.  https://community.qlik.com/t5/Support-Knowledge-Base/QlikView-ThousandSEP-SET-variable-doesn-t-match...





Digital Support
Digital Support

@rva_heldendaten Hi Roland! We do not have a list but I will take it back to the team as it's a great idea!