topic Re: Calculated Dimension - STRANGE BEHAVIOUR in QlikView

Calculated Dimension - STRANGE BEHAVIOUR

Wed, 26 Nov 2014 13:51:09 GMT

I'm noticing a very strange behaviour while defining a calculated dimension in a line chart. Please see the following screenshots and let me know if you have any idea of this strange behaviour.

I'm writing this in calculated dimension (numDate)

But the output display is seen as :

Here it can be seen that less than 40721.33055 is being shown. How is this possible?

I have the one more similar sample but the output display is absolutely correct in that case.

Correct output can be seen as follows:

Can anyone explain this behaviour?? Unfortunately I can't share my qlikview files and data due to privacy issues.

Re: Calculated Dimension - STRANGE BEHAVIOUR

quwok — Wed, 26 Nov 2014 14:00:38 GMT

Your value is being read as a number, you'll need to set it to the date number format.

Re: Calculated Dimension - STRANGE BEHAVIOUR

Frank_Hartmann — Wed, 26 Nov 2014 14:07:03 GMT

Try this in script

Date(Date#(numDate)) AS numDate

Re: Calculated Dimension - STRANGE BEHAVIOUR

Wed, 26 Nov 2014 14:07:41 GMT

Thanks for the reply. But if the values are being read as a number, still the comparison operator should work fine. In fact I intentionally converted my dates to Num(Dates) so that numbers are compared instead of dates

Re: Calculated Dimension - STRANGE BEHAVIOUR

Wed, 26 Nov 2014 14:10:33 GMT

Hi Frank

I would like to know what's wrong in comparing two numbers here..??

Re: Calculated Dimension - STRANGE BEHAVIOUR

quwok — Wed, 26 Nov 2014 15:11:34 GMT

Ah, the year made me think you are looking after the date. Having looked at your issue a bit closer, it seems that your decimal comma is causing an issue with the comma of the if statement.

Your expression:

=if(numDate>=40721,330555556,numDate)

is read as

if numDate>=40721 then 330555556 else numDate

hence every number that is smaller than 40721 is shown.

Re: Calculated Dimension - STRANGE BEHAVIOUR

Wed, 26 Nov 2014 15:17:58 GMT

I thinik that's the actual reason.

I resolved it by converting number to Date.

Thanks...!!!!