Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Adobe Reader-Today's update will not allow 01/01/2017 as a date in a form.

Avatar

Level 1

Today's update will not allow 01/01/2017  to be used as a date in a form. Tried on several computers on my network. Users were able to use 01/01/2017 on forms yesterday before the update.

12 Replies

Avatar

Employee

Hi pendarus,

Try to reboot the computer, relaunch Reader, and then check if the issue still persists.

Could you please confirm the following details:

Version of Reader installed- to check the version, launch Reader>click Help menu>select About Adobe Acrobat Reader

Operating System installed on the machine?

Avatar

Level 1

We are experiencing this issue as well at the Commonwealth of Kentucky.  Users are reporting the inability to enter 01/01/2017 as a date on any form.  We use the Adobe Interactive Forms to allow our Human Resource Specialists to enter Personnel Actions for Employees.  We are an SAP HR Bench.  This is now a production issue for us for anyone who has updated the Adobe Acrobat product on their workstations state wide.  Please advise.

Adobe Acrobat Reader DC: Version 2015.023.20053 Installed 01/11/2017

Adobe LiveCycle Designer: Installed 04/02/2013

Avatar

Level 1

The date changes from 01/01/2017 to 01/01/2016 on any date field, on any form.  This strange behavior occurs when the user enters the date by typing the date into the date field OR if they select 01/01/2017 using the date picker.  The issue is occurring irregardless of how the user enters 01/01/2017, the date is Automatically flipped to 01/01/2016 when the user exits the date field.

Avatar

Level 3

Can you change 2016 to 2017 with the keyboard?

Avatar

Level 1

You can, however once the focus leaves the Date Field, it flips back to 01/01/2016.  This is only an issue with January 1st, no other date is presenting this issue.  It behaves as if 01/01/2017 is an invalid date to the Adobe Date Field.  This behavior occurs on a bran new form, with no FormCalc or JavaScript, therefore presents itself as an issue with the Control itself.  I am curious, have more people not reported this issue?  This issue presented itself two days ago when our IT Staff rolled out the latest Adobe Reader update.

Avatar

Level 3

Looks like a bug of the last update of Acrobat Reader DC and Adobe Acrobat DC.

Avatar

Employee

Hi COMK_BrandonShort,

Would it be possible for you to share one of the form with us, i have sent you a private message, please check the inbox.

Thank You,

Shivam

Avatar

Level 1

Problem still persists after a reboot.

Adobe Reader version 2015.023.20053 Windows 7 Professional 64 bit.

I saw the problem happen on my system. I opened the form and was able to input 01/01/2017 in a date field. I then closed Reader and it updated to version 2015.023.20053. Opened the form again and could not enter 01/01/2017. It reverted to 01/01/2016. I used both the keyboard and the date picker.

Avatar

Level 1

I'm not sure how to save an Adobe Interactive Form, I can give you a print form version of the form, but that will not let you use the date field.  The issue resides with any date field on any form that is being used by a user who has Adobe Acrobat Reader DC v. 15.023.20053 installed.  All you have to do, to replicate this issue is to simply enter or choose 01/01/2017, when the focus of that date box is changed, eg., if you move to the next field, click out side of the date box, etc., the date is automatically flipped to 01/01/2016.

Avatar

Level 1

I would like to add that the date field presents the issue when a Display Pattern and Edit Pattern are set on the Date fields.  If you do not have any display/edit date validations configured, the field will accept any text, and therefore will not present the issue.  I have attached a screen shot of how we have our Date Field(s) Configured.

Adobe_Issue.JPG

Thank You,

Brandon.

Avatar

Level 1

It appears that the issue is occurring for us for multiple date fields, using the date of January 1st in other years.  The only way that I can allow our users to enter a January 1st date is to switch the Date/Time field to a standard Text field... which being bound to date fields in our SAP System, requires the data to leave the form in a YYYYMMDD format, eg., 20170101.  This is highly unacceptable for us, and our business is very disappointed.  We are unsure of how to move forward, however without the ability to enter a January 1st date, we are limited on being able to process personnel actions, and therefore may potentially impact employees payroll.  I am not seeing a lot of information about this issue, however we cannot be the only location having this trouble, as I have been able to duplicate the issue using a "blank" unbound form.  Please advise.