topic Re: Alternate state evaluating expression different than default in QlikView

Alternate state evaluating expression different than default

evan_kurowski — Fri, 15 Aug 2014 17:16:50 GMT

Hello All,

I'm trying to get a system working where the selections for an end-users ID are moved out to an alternate state, so that selections can be applied in the alternate state without reducing the default data set, and I have created a state called Selections.

Except when I move a copy of my user Ids to an island table and then assign that table to the separate state, the syntax that checked for evaluating matches stops working. I've marked the expressions that seem ok in green and the ones that are functioning differently in the alternate state in red. Any thoughts?

Re: Alternate state evaluating expression different than default

Anonymous — Fri, 15 Aug 2014 17:26:23 GMT

not sure what exactly the issue is but in the second text box where you check for the UISelector in Selections state, i removed the single quotes for the value in the if condition and it checks fine.

Re: Alternate state evaluating expression different than default

Fri, 15 Aug 2014 17:30:11 GMT

I created a new state State1 and it seems to work as expected.

Edit: As suggested by Jsaradhi, removing quotes around the number works

Re: Alternate state evaluating expression different than default

evan_kurowski — Fri, 15 Aug 2014 17:48:51 GMT

Hello jsaradhi, Ajay,

I'm confused then, why does the expression against UsrID using single quotes evaluate properly in all states?

=IF(UsrID='0.015625','TRUE','FALSE')

What would be the indicator for when and where you can or cannot use quotes?

Re: Alternate state evaluating expression different than default

Fri, 15 Aug 2014 18:51:39 GMT

My theory:

Usually number fields dont need quotes, its required only for text values. But people use even for numbers, forcing QV to read it as a text. Maybe something to do with that.

Re: Alternate state evaluating expression different than default

Anonymous — Fri, 15 Aug 2014 19:10:36 GMT

I agree with Ajay about the use of single quotes for numbers. I am guilty of it too sometimes.

Re: Alternate state evaluating expression different than default

evan_kurowski — Fri, 15 Aug 2014 19:26:25 GMT

Well, I appreciate you taking the time to look.

But here's something weird.. I thought maybe having ID values using a decimal it might be something making the evaluation inconsistent, so I tried to push them to integers.

Except when I multiply the same value from the ID fields, I get two different evaluations of the Floor() function. Why aren't these matching?

Re: Alternate state evaluating expression different than default

Mon, 18 Aug 2014 18:29:22 GMT

I have come across this and the solution I found was using this:

=Floor(Num#(UISelector) * 100000000)

I used to compare numbers like If (Value=Cost,1,0) and for 1.2342 = 1.2342 it would return false. I searched the forum and found the solution as to use Num#(). I will paste the link if i come across it again.

Re: Alternate state evaluating expression different than default

Mon, 18 Aug 2014 18:55:47 GMT

This might help:

http://community.qlik.com/blogs/qlikviewdesignblog/2013/12/17/rounding-errors

Also when I tried converting the two numbers to binary they were giving me two different results:

=Num(UsrID,'(bin)') or =Num(UsrID,'(hex)')

The above link might throw some light on that.