Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 3.3.3, 3.3.5
-
Fix Version/s: 3.4.alpha
-
Component/s: Core CiviCRM
-
Labels:None
Description
To reproduce.
Create a custom data field with a "integer" data type and associate with individual contacts.
Create an import file with firstname and lastname of contact, with data to be mapped to the custom field...put non integer data in the field, e.g. "10 01"
Upload, CivCRM Import will report 1 contact to import, but when it tries to import on the next stage it will break.
Developer who is fixing this issue, may want to investigate if there are any other data type mismatch scenarios which could break the import process.
Could you please integrate the patch from : https://fisheye2.atlassian.com/changelog/CiviCRM?cs=32686
( should be available in few minutes )
with your installation and let us know if it works for you.
From code base, it looks like we have handled most of the data validation cases.
It would be great if you take a close look for different scenarios and let us know in case anything is missing/broken.
Thanks
Kiran