Timepicker sets year to 2000 if min and max time value is defined

If you think that something doesn't work in Aware IM post your message here
Post Reply
joben
Posts: 221
Joined: Wed Nov 06, 2019 9:49 pm
Location: Sweden
Contact:

Timepicker sets year to 2000 if min and max time value is defined

Post by joben »

timetest1.png
timetest1.png (8.1 KiB) Viewed 11974 times
timetest2.png
timetest2.png (11.03 KiB) Viewed 11974 times
timetest3.png
timetest3.png (8.03 KiB) Viewed 11974 times
Expected behaviour would be the have the current date displayed.

The cause seems to be the min and max values that I have defined for the StartTime attribute inside the form.

I have attached a bsv in the reply.

Steps to reproduce:
Create a new "Appointment" object.
Click the time picker on the StartTime field and pick any time, 09:00 for instance.
The date part will now think it is year 2000.

Currently running 8.7 (build 3025)
This worked as intended when running AwareIM 8.4
Regards, Joakim

Image
joben
Posts: 221
Joined: Wed Nov 06, 2019 9:49 pm
Location: Sweden
Contact:

Re: Timepicker sets year to 2000 if min and max time value is defined

Post by joben »

Bsv for testing attached.
timetest.zip
(48.31 KiB) Downloaded 616 times
Regards, Joakim

Image
joben
Posts: 221
Joined: Wed Nov 06, 2019 9:49 pm
Location: Sweden
Contact:

Re: Timepicker sets year to 2000 if min and max time value is defined

Post by joben »

Workaround via update rules:

Code: Select all

If Appointment IS NEW AND Appointment.StartTime IS UNDEFINED Then 
Appointment.StartTime=CURRENT_DATE
Regards, Joakim

Image
Post Reply