Qlik Community

Ask a Question

Integration, Extension & APIs

Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.

Announcements
QlikWorld Online 2021, May 10-12: Our Free, Virtual, Global Event REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
martyginqo
Partner
Partner

Christmas comes early (bug) in Date Picker - Qlik Dashboard Bundle: Predefined Ranges off by +1

I believe an old bug in the Date Picker has resurfaced.

In a number of recent Sense releases (November 2019, September 2019) the Date Picker extension in the dashboard bundle returns dates that are off by a day (offset +1). Versions 2.8, 2.9 of the extension don't seem to work.

Sense June 2019 and associated extension version (2.5) seems to be one of the last combinations to work.

Interestingly, when hovering over "Today", the dates update correctly...but upon selecting, the next date is actually loaded. Christmas comes early...but not in a good way.

Merry Christmas and Happy Holidays nevertheless. 

Martin.

DatePicker.png

 

 
11 Replies
andoryuu
Creator III
Creator III

After much experimentation in experiencing something similar the only way I found around this was adding a field to my data load that handled my date field thusly:
timestamp(floor(timestamp#([yourdatefield]))) as SessionDateFilter
then force the system to see it as a date in your data load:
Tag [YourDateField] with '$date'; //tell the system you want it to be recognized as a date so that you can use it.
and then set the format in the language and labels to be:
='M/D/YYYY'
this brings all the dates down to a base timestamp to make date selection singular in nature per day and cuts out the timestamp. Obviously, you'll set your format to be for whatever your local settings are, but the main point is to use a timestamp, but force the system to use it as a date.
alantam12
Partner
Partner

I'm also seeing the same issue.  Has someone been able to solve this issue?

dialupdave
Contributor
Contributor

Issue same here. November 2019 server.

jbouslimi
Contributor III
Contributor III

I confirm we have the same issue here - November 2019 patch 3. Was OK in June 2019.

jbouslimi
Contributor III
Contributor III

Does anyone know when the bug will be fixed?

jphillips
Contributor
Contributor

This issue still seems to exist, although it is not isolated to just predefined ranges.  When I select a single date from the calendar such as Feb 11, the filter will actually select Feb 12th.

 

hhe
Employee
Employee

The bug is fixed and will be part of Sense April 2020.

Qlik_Greg
Contributor
Contributor

Appreciate the feedback confirming the bug and the fix date, but this is a pretty significant bug.  Isn't it possible to have it  fixed in a November 2019 or February patch?  We purposefully stay 1 release behind to avoid as many issues/bugs as possible.  That means we won't be deploying the April 2020 update until the middle of the year.  That is a long time for such a silly bug to be in the system.  Please add it to a November or February Patch.

lynn_mcclurg
Contributor II
Contributor II

I know this is a little late for some.  We can't jump to April 2020 yet.  I put in a ticket with Qlik support and they were able to post the corrected extension to the ticket.  I loaded it into our QA Environment with Nov 2019 installed and the issue is corrected.

In the ticket I reference this post as it perfectly describes the issue.