CiviCRM Community Forums (archive)

are you trying to create relationships during the import?

Do any of your rows have NULL data in the Org Name column?

If so maybe split your import to a table that all rows have Org Name, and another that does not?

let me know if that helps

Peter was correct, the records with the 'Mismatched Contact ID' were the records with NULL as the Organization Name. Importing the sheet in two batches (contacts with an organization and contacts without) corrected everything.

This has never been an issue before I upgraded to 3.2.2

I don't know if this is strictly speaking a bug, but it definitely doesn't seem the ideal way to run imports. When importing thousands of records you are always going to have records without a company/organization name.

Running into identical issues, I agree that this is highly unintuitive. It beats creating blank records, but I really don't want to need to present my end users with a small "How to do imports" book describing the numerous conditions under which they need to break lists down into smaller lists and the numerous intimidating error messages which they should be prepared to encounter on a regular basis during seemingly ordinary imports.

This probably wouldn't be a problem if the message displayed was clearer. If it's leaving developers and experienced CiviCRM implementers baffled, to an ordinary user it must sound impossibly technical, when actually what's happening should be really easy for anyone to understand and fix.

Where a contact reference field is blank rather than mismatched, I can't see any problems with a more helpful plain-English message like,

"There were rows where [Employee of - Organisation Name] was missing. In case this is a mistake, these rows were not imported.
If you would like to import these rows anyway, please download and re-import the following file, which contains only these rows, and leave [Employee of] out of the import".

Agreed, really weird way of handling the issue. Especially confusing as it only seems to have happened after an upgrade.

Hey ken:

any chance u can take a look at the code and see if you can make the message friendlier and more informative

Will help your client AND all the other folks who download and use civi

lobo

Are you importing rows of contacts, and only some of them have an 'employee of' organisation?
hence the 'errors' are the import reporting back to you that you had included the column to create the relationship, but that for some of those rows it was empty.

if so getting an error seems correct since the import mapping is saying 'look at column x and create a relationship between Individual A and Organisation B' but then no data is provided for Org B.