Qlik Community

Ask a Question

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
Welcome to our newly redesigned Qlik Community! Read our blog to learn about all the new updates: READ BLOG and REPORTED ISSUES
cancel
Showing results for 
Search instead for 
Did you mean: 
Contributor III
Contributor III

sql server GUID (uniqueidentifier) type loading in lowercase - April 2019

Situation: After upgrade to April 2019 from November 2018, we are experiencing difference in loading and handling of guids (uniqueidentifier) sql server columns. columns values are now loaded in lowercase. 

Simple loading of a sql server table containing columns of type - uniqueidentifier ( containing guid in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) is now loading in lowercase. 

e.g. Column A is loaded  with a row value of '6F9619FF-8B86-D011-B42D-00C04FC964FF' as '6f9619ff-8b86-d011-b42d-00c04fc964ff'. 

This creates a problem in Qlik when you are trying to retrieve a particular row in an in-memory dataset by using a where clause like 'where A = '6F9619FF-8B86-D011-B42D-00C04FC964FF' , say you are looking for a particular client data. This now results in no data being returned because April 2019 version now make the where clause look like 'where A = '6f9619ff-8b86-d011-b42d-00c04fc964ff'

I know I can do a workaround using upper or lower but it is not compatible with the older code written against November 2018. Has anyone experience this? Is this related to any odbc driver load change to the data manager? Any input will be appreciated. Thank you.

Labels (1)
0 Replies