Saroj PandaJanuary 20, 2017 at 2:01 am #3518
Seems we have broken some existing working feature of Date Picker control while fixing other issues in 4.4.7.
We were using the date control to set the field to “yyyy” format with Start view = “Year” and Minimum view mode = “Years”. This used to work before but now we are getting error on selecting or entering the year value. I have attached the screenshots for reference.
Sadly we had to revert back to 4.4.6 version inspite of having other fixes and improvements in the latest version.
SarojSaroj PandaJanuary 20, 2017 at 8:43 am #3527
We have found the work around to make this work which is bit stupid but can let us live with 4.4.7 🙂
Adding extra space to the format text is letting the year value remain in the control. So instead of “yyyy” we are now having “yyyy ” as format text. You can refer the attachment for the result.
This may help your team to point out the issue in the control and fix it.
SarojSPARK SupportJanuary 20, 2017 at 12:30 pm #3531
Thank you for bringing this to our attention and providing the work-around. We are currently investigating this issue and will provide more information in a timely fashion.
Stephen P.SPARK SupportJanuary 23, 2017 at 3:28 pm #3539
During the latest development cycle, it came to our attention that the Date Picker control was not consistently enforcing date formats. We are now enforcing date formats as originally designed to use two digit months and days when no separator is used. (yyyymmdd, mmddyyyy,
In some cases, this impacts customers who used certain less than 8 character formats without delimiters. SPARK is still able to handle these scenarios so long as customers add a delimiter to the end of their format (as you discovered with ‘yyyy ‘).
We understand this might be a less than desirable solution for some customers, but based upon the full set of customer feedback and our intended design, this approach was the most suitable way forward.
Stephen P.Saroj PandaJanuary 24, 2017 at 3:56 am #3556
I understand this might be the most suitable way considering the current design. But I don’t think most of the customers will agree to have some kind of dilimiters to short formats. Even BPM default Data Time Picker support these short formats without any issues of appending dilimiters.
This is more like the work around instead of expected behavior and I’m sure there are solutions to fix this issue. Hope your team understand this as an issue and can fix this in upcoming version.
SarojSPARK SupportJanuary 25, 2017 at 12:39 pm #3567
Thank you for your feedback, we’ll take it into consideration when planning future releases.
Stephen P.Saroj PandaJanuary 27, 2017 at 4:43 am #3596
I have created the bug report for you to track the issue and it’s resolution.
You must be logged in to reply to this topic.