topic Re: Unexpected behaviour with date range in set analysis in QlikView

Unexpected behaviour with date range in set analysis

Wed, 05 Aug 2015 09:59:36 GMT

Hi I'm using QlikView 11.20 SR 12 and have a strange behaviour with date ranges in set analysis

i have the following set expression:

{$<date={'>=$(=MonthStart(vEndDate))<=$(vEndDate)'}>}

It seems that QlikView is ignoring the <= and behave like it is only a < . Does anybody know, why?

My workaround for this behaviour is $<date={'>=$(=MonthStart(vEndDate))<=$(=Date(vEndDate+1))'}>} , so the correct date range is shown.

Thank you for your help!

Re: Unexpected behaviour with date range in set analysis

Gysbert_Wassenaar — Thu, 06 Aug 2015 08:44:04 GMT

It seems that QlikView is ignoring the <= and behave like it is only a < . Does anybody know, why?

I doubt that. What does your variable vEndDate contain? How is that value created?

Re: Unexpected behaviour with date range in set analysis

Fri, 07 Aug 2015 09:56:56 GMT

vEndDate is created and filled with a Slider/Calendar Object. Min Value is undefined, Max Value is = Max({1} date).

Date is generated with the Master Calendar Script.

When i print the expression in a Text Object it looks like >=2015-07-01<=2015-07-31.

When i use it in a straigth table with date as dimension i get dates from 2015-07-01 till 2015-07-30 and not till 2015-07-31.

Re: Unexpected behaviour with date range in set analysis

Gysbert_Wassenaar — Fri, 07 Aug 2015 10:09:00 GMT

I'm guessing that your variable vEndDate is a pure date without a time fraction, i.e. 2015-07-31 00:00:00, and the 'dates' you want to see do have time fractions. Those 'dates' will be larger than the start of the day 2015-07-31.

Re: Unexpected behaviour with date range in set analysis

Fri, 07 Aug 2015 10:40:26 GMT

That was the solution for the problem. Some of the data which i thougt, that where pure dates, had a timestamp. Thank you for your help.