topic Re: Set Analyisis Boundary for integer diemension in App Development

Set Analyisis Boundary for integer diemension

fabdulazeez — Wed, 22 Dec 2021 20:29:53 GMT

Sum({<EmployeeID={">3 <2"}>}[Sales Amount]) is giving me results for 0 and 1

(Like invalid range)

and Sum({<EmployeeID={">1 <3"}>}[Sales Amount]) gives result properly for 2.

Is this a expected behavior as I was expecting a between

I am using February 2019 ReleaseEnterprise edition.

So i am using like Sum({<EmployeeID={">3"}*{"<2"}>}[Sales Amount])

Re: Set Analyisis Boundary for integer diemension

tresB — Tue, 14 Jan 2020 07:18:09 GMT

It seems that range itself is not right for integers. There is no integer between 3 and 2 (">3 <2"), right?

Re: Set Analyisis Boundary for integer diemension

fabdulazeez — Tue, 14 Jan 2020 07:19:40 GMT

Yeah Invalid range. But i was expecting it return no values

Re: Set Analyisis Boundary for integer diemension

tresB — Tue, 14 Jan 2020 07:23:39 GMT

Sum() always returns a numeric value, i.e. - sum of nothing is also zero.

Re: Set Analyisis Boundary for integer diemension

fabdulazeez — Tue, 14 Jan 2020 07:24:49 GMT

I meant its returning value for employee 0 and 1.

Re: Set Analyisis Boundary for integer diemension

tresB — Tue, 14 Jan 2020 07:27:35 GMT

That should not happen. Could you share a sample app where you see this?

Re: Set Analyisis Boundary for integer diemension

fabdulazeez — Tue, 14 Jan 2020 07:27:39 GMT

if you want to check

SalesTable:
Load
MakeDate(2016+Floor(Rand()*2), 1+Floor(Rand()*12, 1)) as TimeStamp,
Round(Rand()*10000) as 'Sales Amount',
Floor(Rand()*4) as EmployeeID
autogenerate 100;

than create a tabl with Employee id and Sum set analysis

Re: Set Analyisis Boundary for integer diemension

jonathandienst — Tue, 14 Jan 2020 08:03:55 GMT

You may have noticed when interacting with Qlik, that making an selection that conflicts with existing selections clears the existing selections. Something similar may be happening here. The impossible range does not result in no values, but rather that the filter is not applied.

Re: Set Analyisis Boundary for integer diemension

fabdulazeez — Tue, 14 Jan 2020 08:13:21 GMT

True . I was thinking the same, because it was giving output for second condition. In few Docs online i saw it as between.

Just wanted to make sure

Re: Set Analyisis Boundary for integer diemension

tresB — Tue, 14 Jan 2020 09:17:33 GMT

The impossible range does not result in no values, but rather that the filter is not applied

If you notice, the values 2 and 3 (end points) are excluded from result, so it's not exactly 'filter not applied'. However, your selection logic (clearing) something looks to me as a possibility.

Re: Set Analyisis Boundary for integer diemension

fabdulazeez — Tue, 14 Jan 2020 09:23:23 GMT

Yeah that's what i thought as it was giving output for second condition.

Basically like second selection is excluded from first selection, first selection is removed and second selection is applied.

If it's like that than i need to be more vigilant while writing set Analysis.

Re: Set Analyisis Boundary for integer diemension

tresB — Tue, 14 Jan 2020 10:23:15 GMT

As if it's working as OR condition instead of AND. That is, when the range looks to be a improper/impossible one, it uses OR in place of AND, the technicality of this evaluation I am not aware of. I don't remember if the case was so in old version of qlik engine, however in some cases new qlik engine is designed in such a manner that it applies it's intelligence to handle ambiguous scenarios ( I read @hic post, don't just recollect it now where), the same might be happening here; qlik engine is being intelligent here - since AND logic is not valid, therefore it is using OR logic.

Re: Set Analyisis Boundary for integer diemension

jonathandienst — Tue, 14 Jan 2020 11:54:53 GMT

I created simple app;

LOAD * Inline
[
Cat, Val
1, 10
2, 20
3, 30
4, 40
5, 50
6, 60
];

And now I can see the OR behaviour. in a text box:

=Concat({<Cat = {"<=2 >=5"}>} Cat, ',')

give 1, 2, 5, 6

And this the same as an explicit OR:

=Concat({<Cat = {"<=2"}+{">=5"}>} Cat, ',')

You learn something every day...

Re: Set Analyisis Boundary for integer diemension

hic — Tue, 14 Jan 2020 12:57:21 GMT

The format of the search string decides how the search is made.

>900<1000	will find all values greater than 900 and less than 1000
<900>1000	will find all values less than 900 or greater than 1000

This is described on https://help.qlik.com/en-US/qlikview/April2019/Subsystems/Client/Content/QV_QlikView/Text_search_and_numeric_search.htm

If you want a strict behaviour, you need to split it up into two different conditions, you like you already have done.

HIC