Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Lena4
Contributor III
Contributor III

Set Analysis is Not working

I'm building a chart and have used the following code to isolate values for a particular timeframe. The problem is that the 'VALUE={">100"}' part of the set expression is not being recognized.  It only happens when I use the Timestamp syntax. Does anyone know of a workaround? 

 

Lena4_0-1736458801408.png

 

Labels (3)
4 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

There are 2 potential issues here:

1. you are using Value >100 and in other place you have Value = 'Open'. That indicates to me tha field has mixed datatypes which I assume can cause issues when trying to do numerical comparisons. In my preactice I never allow for such scenario as it creates confusion and mess. Id rather load 2 separate fields (one for numbers and one for text), or create flags for thos conditions.

2. your syntax is wrong here:

you have [Value= ........so you are missing closing bracket for field Value. You can do either: [Value]=, or just Value= as that field does not require brackets as it has no special characters or space in its name.

Lech_Miszkiewicz_0-1736460875450.png

cheers

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Bhushan_Mahajan
Creator II
Creator II

@Lena4 Please provide expression, since the screenshot expression is not visible properly.

@Lech_Miszkiewicz I think second issue is there in the expression due to which it is not working 

Lena4
Contributor III
Contributor III
Author

Hi @Bhushan_Mahajan & @Lech_Miszkiewicz 

Here's the corrected expression. The field does have mixed data types, but I'm able to distinguish between the different types by using the location field.  

(Count(distinct{< Location={'A'},VALUE={">100"},TIMESTAMP={"=concat(DISTINCT IF(VALUE='Open' AND Location='P.1' , TIMESTAMP),',')"}> *<TIMESTAMP=                                                       {"=concat(distinct IF(VALUE='Open' AND Location='P.11. ', TIMESTAMP), ',') "}>
             +<TIMESTAMP={"=concat(DISTINCT IF(VALUE='Open' AND Location='P.2 ' , TIMESTAMP),',')"}> *<TIMESTAMP=                                                                                                                        {"=concat(distinct IF(VALUE='Open' AND Location ='P.12 ', TIMESTAMP), ',') "}>
              +<TIMESTAMP={"=concat(DISTINCT IF(VALUE='Open' AND Location='P.3', TIMESTAMP),',')"}> *<TIMESTAMP=                                                                                                                          {"=concat(distinct IF(VALUE='Open' AND Location='P.13 ', TIMESTAMP), ',') "}>}TIMESTAMP))

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Well. You do you. That field is a single field so you cant expect it to work differently on different rows. 
For testing you can just put Value field in filter pane in UI and search >100

see if you get correct results!

I say numerical searches based on operators may not work properly in this case. 

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.