Qlik Community

Qlik Sense App Development

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

Announcements
QlikWorld 2020: Join us May 11 - 14, 2020 in Phoenix, AZ. Register early and save $400. Learn More
Highlighted
vkish16161
Contributor III

Bug ?? in Set Expressions Builder in QS Nov 2018?

All,

There was an update to the Set Analysis syntax Quotes in Set Analysis‌ (Sep 2017)

Today, in QS Cloud (Nov 2018) there is a SET expression builder that got released.

I believe there is a minor flaw in it :

1.JPG

Above expression was built using the Set Analysis Builder and it wrapped the year value 2013 in single quotes. As far as I'm aware, the wrapping in quotes should be done if the value is a string literal. So it should be Year={2013}.

Or am I wrong?

mto hic

1 Solution

Accepted Solutions

Re: Bug ?? in Set Expressions Builder in QS Nov 2018?

No, it works properly. Whether you should use

   {<Year={2014}>} ,

   {<Year={'2014'}>} or

   {<Year={"2014"}>}

is a matter of taste. All three will work for this field value. Single quotes denote explicit field values, just as Dilip points out.

No quotes will cause problems if the field value contains spaces. Double quotes will cause problems if there are two field values that only differ in the upper/lower case. So, we chose to wrap all field values in single quotes, because then it always works.

HIC

View solution in original post

2 Replies
Partner
Partner

Re: Bug ?? in Set Expressions Builder in QS Nov 2018?

Single quotes should denote literals, i.e. explicit field values.

Re: Bug ?? in Set Expressions Builder in QS Nov 2018?

No, it works properly. Whether you should use

   {<Year={2014}>} ,

   {<Year={'2014'}>} or

   {<Year={"2014"}>}

is a matter of taste. All three will work for this field value. Single quotes denote explicit field values, just as Dilip points out.

No quotes will cause problems if the field value contains spaces. Double quotes will cause problems if there are two field values that only differ in the upper/lower case. So, we chose to wrap all field values in single quotes, because then it always works.

HIC

View solution in original post