Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Field tagging for source data with unrecognized formatting has changed in February 2019

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Andreas_Giesbrecht

Field tagging for source data with unrecognized formatting has changed in February 2019

Last Update:

May 3, 2021 8:45:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jun 19, 2019 9:48:16 AM

Field tags allow for adding metadata to the fields in your data model. Automatic field tagging in Qlik Sense has changed in February 2019 as a symptom of how unrecognized data format is treated by Qlik Sense.

Environment:

 

Resolution

There is an automatic field tagging based on the content of the data field, but if you want to control the field types you can use num() and text() function in your load statement to cast each field to the type you want to.

When needing to influence the actual metadata tagging for a field the tag() and untag() functions may be used.

For more information see: Field Tags

 

Cause

Most unrecognized formatting from a data source are treated as a text representation in February 2019 and later. Previously, these formats where interpreted numerically, often with incorrect results. For example in Qlik Sense November 2018 version, data fields (defined as text fields in the data source) containing yearmonth data (yyyymm) are read as a number/integer. In February 2019 and later versions, those data fields are read as ascii/text. See related documentation under Qlik Sense: Date picker field shows invalid dimension error

Labels (2)
Contributors
Version history
Last update:
‎2021-05-03 08:45 AM
Updated by: