Qlik Community

Qlik Sense Advanced Authoring

Discussion board where members can learn more about Qlik Sense Advanced Authoring.

Announcements
BARC’s The BI Survey 19 makes it official. BI users love Qlik. GET REPORT
Highlighted
Partner
Partner

Using Spaces in Set Analysis Values

I'm using the attached set analysis expression and it is giving me an Error.

I noticed that when I remove the space between "A 1" and "I 2" that the expression is then OK.  

Why wouldn't I be able to use a space if that is what my values are?

How do I fix this?

1 Solution

Accepted Solutions
MVP
MVP

Re: Using Spaces in Set Analysis Values

It looks like you built the expression in Excel (or some other auto-correcting editor) -- the quotes are not the correct characters. Replace them with normal quote characters in the Qlik script editor.

One, Two should be "One, Two"

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein

View solution in original post

5 Replies
Partner
Partner

Re: Using Spaces in Set Analysis Values

try using single quote as below:
[Program Type] = {'A 1', 'I 2'}

Re: Using Spaces in Set Analysis Values

Did you try to press okay and see if the expression worked or not? Also, can you try this

{<[Program Type] = {"A?1", "I?2"}>}

or

{<[Program Type] = {"A*1", "I*2"}>}
MVP
MVP

Re: Using Spaces in Set Analysis Values

It looks like you built the expression in Excel (or some other auto-correcting editor) -- the quotes are not the correct characters. Replace them with normal quote characters in the Qlik script editor.

One, Two should be "One, Two"

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein

View solution in original post

Partner
Partner

Re: Using Spaces in Set Analysis Values

You're right!  I was copying & pasting the expression from Word.  Word was using "Smart Quotes" which I had to disable.  Qlik doesn't recognize these Smart Quotes.

Partner
Partner

Re: Using Spaces in Set Analysis Values

Yes, single quotes would have worked, but I specifically wanted double quotes to account for lower-case spelling variations.