Qlik Community

App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
WE ARE LISTENING! New Navigation for Qlik Community, Sept. 26: TELL ME MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
alexis
Partner - Creator III
Partner - Creator III

Date Picker unusual behaviour

We select a range of dates on the Date Picker (say 4/7/22 - 6/7/22) (European format so it's July 4 until 6th) that displays InvoiceDate  and for some bizarre reason the picker shows 5/7/22 - 7/7/22 as the dates picked. This has nothing to do with data/transaction availability.

I have a separate filter pane with Year, Month, Week and Day of the InvoiceDate and it behaves exactly as expected sp it's not data related. We need the picker to manually select across month boundaries (e.g. 20/6/22 - 5/7/22 for example). Anyone come across this?

We are using version 2.14.0 of the Date Picker which is part of the Qlik Dashboard Bundle of the June 2020 version of Qlik Sense.

Labels (1)
2 Replies
NadiaB
Support
Support

Hi @alexis

 

Unfortunately June 2020 is out of Support, it is suggested to upgrade Qlik Sense and verify if the issue persist in the new version:

 

https://community.qlik.com/t5/Product-Support-Lifecycle/Qlik-Sense-Enterprise-on-Windows-Product-Lif...

 

I was not able to find Product Defects confirmed by R&D with that issue. 

 

Kind Regards!

Note: if this suggestion helps to resolve the issue or answers your question, it will be appreciated if you select the "Accept as Solution" option.
Visit our Knowledge Base https://community.qlik.com/t5/Knowledge/tkb-p/qlik-support-knowledge-base and our Qlik Help portal https://help.qlik.com/
Or
Champion
Champion

One thing that might be worth checking - are your dates correct insofar as the dual() aspect? Which is to say, does the number portion of the date field match the text (formatted) version of the date? Being off by exactly one day is a bit suspicious, so I'm wondering if this isn't a case of the values being created from Excel values where there's the infamous 1900 leap year bug ( https://docs.microsoft.com/en-us/office/troubleshoot/excel/wrongly-assumes-1900-is-leap-year ) or something of that nature.