Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 3.1
-
Fix Version/s: 3.1
-
Component/s: Core CiviCRM
-
Labels:None
Description
In CiviCRM v3.1 beta 4 with CiviEngage install, and also tested in the CiviCRM sandbox (CiviCRM 25758), when importing a date format of mm/dd/yyyy and select this format for import, in the following import screen, when you can view the data, I see that civi shows the date format as mm/dd/yy, which then causes an error when trying to run the import. This is confusing to the user - of course if I go back a screen and change the date format to mm/dd/yy, it works. But definitely a usability issue, since a user expects their data to be in mm/dd/yyyy.
I also noticed that in the Global SEttings -> Date Settings, the option for complete date is "mm/dd/yy (12/31/2009)" which is also confusing to the user. I think in previous versions, we actually have mm/dd/yyyy when selecting a date format in the import and it works wonderfully.
Is this an intended change for v3.1?
Attachments
Activity
Kiran - seems to be working now. And I did another test. It no longer tries to convert the date to mm/dd/yy from mm/dd/yyyy and cause the error. I'll attach my sample anyways. thanks!
alice
Here's the sample I've been using. Again, it seems to be working. I tested in the Sandbox.
thanks!
We have fixed the date examples from Global Settings -> Date Formats -> Complete Date.
Regarding import date with mm/dd/yyyy format -
It seems to be working fine for my local install as well as on sandbox.
sample .csv data file that I have tested :
"first name","last name","Birth Date"
"abc","xyz","12/13/1983"
It would be great if you give some sample .csv data file to replicate issue.
thanks