Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 2.1
-
Fix Version/s: 3.0
-
Component/s: Core CiviCRM
-
Labels:None
Description
Problem:
When importing contacts that fail for a system reason, that is to say the data is formatted correctly but there was a problem in the system which caused a civicrm error, that error information does not get transmitted to the user interface because Dojo masks it. If there is a critical error that causes civicrm to not import anything, dojo still reports 100% success importing.
Expected result:
The proper number of imported contacts should be displayed (most likely zero) and the error should be presented to the user for resolution.
Steps to recreate:
1) Remove a strict rule for a contact type--for example, I changed a strict rule for organizations to a fuzzy rule which left no other strict rules for organizations.
2) Attempt to import a CSV in to organizations. I used the following options: first row contains headers, organization, on match update.
3) Select your field mappings as needed
4) Preview should tell you n rows of x are valid and will be imported. Hopefully n = x at this stage.
5) Click import contacts and confirm the dialog.
6) You will get a status indicator that will attempt to update once.
7) Upon update, it will tell you that all of your contacts were successfully imported (that didn't have data errors)
--alternate ending--
if you break dojo but not all javascript (change the civicrm resource URL to something invalid)...
5) Click import contacts and confirm the dialog.
6) Your page will wait while loading. This may take awhile depending on the size of your dataset.
7) You should receive the civicrm error indicating no strict rule for contact matching in organizations was found.
When importing contacts that fail for a system reason, that is to say the data is formatted correctly but there was a problem in the system which caused a civicrm error, that error information does not get transmitted to the user interface because Dojo masks it. If there is a critical error that causes civicrm to not import anything, dojo still reports 100% success importing.
Expected result:
The proper number of imported contacts should be displayed (most likely zero) and the error should be presented to the user for resolution.
Steps to recreate:
1) Remove a strict rule for a contact type--for example, I changed a strict rule for organizations to a fuzzy rule which left no other strict rules for organizations.
2) Attempt to import a CSV in to organizations. I used the following options: first row contains headers, organization, on match update.
3) Select your field mappings as needed
4) Preview should tell you n rows of x are valid and will be imported. Hopefully n = x at this stage.
5) Click import contacts and confirm the dialog.
6) You will get a status indicator that will attempt to update once.
7) Upon update, it will tell you that all of your contacts were successfully imported (that didn't have data errors)
--alternate ending--
if you break dojo but not all javascript (change the civicrm resource URL to something invalid)...
5) Click import contacts and confirm the dialog.
6) Your page will wait while loading. This may take awhile depending on the size of your dataset.
7) You should receive the civicrm error indicating no strict rule for contact matching in organizations was found.
Most likely we'll fix this when we transition to jQuery