Set Analyisis Boundary for integer diemension

[fabdulazeez]

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])

[tresesco]

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

[fabdulazeez]

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

[tresesco]

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

[fabdulazeez]

I meant its returning value for employee 0 and 1.

[tresesco]

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

[fabdulazeez]

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

[jonathandienst]

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.

[fabdulazeez]

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

[tresesco]

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.